[TYPO3-ect] lib/div & compatibility
philip.almeida at ippimail.com
philip.almeida at ippimail.com
Mon Apr 28 15:00:14 CEST 2008
> Hello Franz,
>
>>> An additional function
_is_ an API-change :-)
>>> Example: If lib02 and div03 are
the current extensionkeys and they are
>>> in use for some
extensions any new functions should go into a new
>>>
branch
>>> lib03 and div03. Just bugfixes for already
existing functions go in
>>> lib02 and div02.
>
> If you're the main-maintainer of div & lib it's easy
for you to put
> everything in the newest version of div &
lib. You can always use the
> current one in extensions like
tt_products .
>
> For others who want to use how it is
(e.g. I'm one of this group) it's
> good to have a defined
version with a non-changing API. For example
> "lib02"
and "div02".
>
> The alias: Please see the
extension "ect". That is an
>
"extension-package". In our case we just have ONE extension in
the
> package.
>
> Clear now what I mean?
>
> Cheers!
>
Daniel
Hi,
Don't forget the KickStarter, the
grow of several div's can make the kickstarter development more
complicated.
This kind of evolution of the API (separated by Year)
is a new thing that you do not see elsewhere (as I Know).
I think
the step now should be the following:
1. See what must be done to
get to beta and close it.
2. After Beta consolidate documentation
and examples (which are already good) .
I would like to developed a
satellite like div__extjswidget but me and others need the confidence that
the API stays solid.
I am not going to develop
div2008__extjswidgets and etc, as well as different tutorials, it is hard
as is already.
Well this is my vision but I may be wrong.
Best
Regards,
Philip Almeida
Einstein "Make things easy but
not easier, make things simple but not simplier"
>
>> This is bad. Imagine you are developing for div02 and then
you want to
>> add a new function. Then this is so restrictive
that you cannot continue
>> and must move to div03 which will
take many months to get ready.
>> Or you must copy this code
into all of your extensions. This is also
>> bad.
>>
This is only managable if div02 is already in RC phase. But it is too
>> restrictive during alpha and beta phase.
>> -
Franz
> _______________________________________________
>
TYPO3-team-extension-coordination mailing list
>
TYPO3-team-extension-coordination at lists.netfielders.de
>
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
>
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com/
More information about the TYPO3-team-extension-coordination
mailing list