[TYPO3-ect] New roadmap lib/div/cool
Elmar Hinz
elmar07 at googlemail.com
Thu Nov 29 14:22:35 CET 2007
Hello Michael,
that is good news. Having a proof of concept and this nice article is
already half the way. With this knowledge people can already start to
develop extensions with propel.
Are this relations right?
generator way <-> generic way
normal ORM <-> active records
torque <-> hibernate
propel <-> ???
symfony <-> cakePHP
> 1) Transform TCA structure into XML
> 2) Adapt ORMs to use TCA
> So my proposal would be the following: We could use Propel and first of
> all Propels interfaces for implementing extensions with lib/div. After
> some testing, we'll see, whether Propel does the job well and could
> implement our own ORM with the Propel interfaces, so that no change in
> the extensions is required - or at least only a little change. Thereby
> we could implement the ORM piece by piece and could replace Propel bit
> by bit.
My proposals:
1.) Pimp your current doc and put it into a documentation extension:
http://typo3.org/documentation/document-library/extension-manuals/http://typo3.org/documentation/document-library/extension-manuals/
We should also think about something like: http://ect.typo3.org, to
communicate ECT results and extensions.
2.) Making a tca2xml converter for propel configuration.
3.) Making lib/div interface.
I think we shoul use Propel unaltered, without a piece by piece replacemet.
All modifications of external tools are quickly outdated upon updates.
Regards
Elmar
More information about the TYPO3-team-extension-coordination
mailing list