[TYPO3-ect] lib/div & compatibility
philip.almeida at ippimail.com
philip.almeida at ippimail.com
Sun Apr 27 23:57:51 CEST 2008
Hello ECT,
Lib div is now alpha for to long, lib div is more then
a "duplication" of the core T3 API, it stands as a new
development paradigm for T3 developers opening the door and integrating
standard patterns like MVC, SPL, Registry.
I have developed 2 small
extensions based on it and I must say that the big outcome for me as a
developer was to have a well separate MVC model.
I did not master
the multi-controller feature of Lib/div or understand yet the full
benefict of switching controllers I admit I am still very
"green" on lib/div.
Either way I would like to point the
following:
1 - Regarding duplicating functions:
I see no
problem on it because lib/div is afterall a new api for TYPO3 framework
and stands as a independent API.
2 - New name div2008 etc...
I
do not like the concept of having div2007, div2008 and so on, it goes
against the unification of code it will be a mess on the long term. I
remember Elmar pointing that div2007 was a exception... (I subscribe
Daniel on this)
3 - Personaly I think Div should go beta even
against Elmar plan, the schedual is already broken and I see no one
following the original plan,
to long as alpha is bad and it have
given proof on field. Many people have already developed some nice
extencions on it. Lib/div is nothing new is just a new way of putting
things but it is a step foward for new developers entering the Typo3
world.
Well I would like to help in the development of
Div as I putted to Elmar, I would like to work on the integration of
EXTJS, but I think we need a unified Div.
Best
regards,
Philip Almeida
> Hello Franz,
>
> if we provide an upgrade-guide from one version to the
next the problem
> is solvable.
>
> So it's
no problem that just one version of lib and div can be on the
>
server. In the PEAR world it's easy to check WHAT version an
installed
> class has, but just ONE version of a package can be on
the server. In
> the Java world it's the same. A jar has a
versionnumber, but when it's
> in the classpath just one can
be active.
>
> =>
> 1. We need an
upgrade-guide and so a fork "2007" and so on is not in need
> 2. The version-number of lib and div should be better:
>
<major>.<minor>.<bugfixes>
>
> Until
now just the bugfix-number was increased, but in reality the API
>
was changed all the time.
>
> Wouldn't that solve the
problems?
>
> Cheers!
> Daniel
>
>>> Forth: Is it finished? doesn't seem to be a lot of work
going on there
>>> anymore.
>> @ECT: Tell me when
you think I should commit the div2007 functions also
>> to the
div extension. It will be added to div in a few months, just
>>
before the div2008 will come out.
>> - 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