[TYPO3-ect] Your feedback for lib/div forms / cherries

Fabien Udriot fudriot at omic.ch
Thu Jun 7 18:15:26 CEST 2007


First of all I would like to say, I like the lib/div approach. The main 
advantage in my opinion, is that it gives a clear coding guide line to 
the developers. The consequence is a cleaner and more maintanable code 
for all !

Here are a few things that I would like to point out :

1) Add some static (?) methods to manipulate *external* *flexform*. I 
have to add manually thoses functions in my classes (pi_getFFvalue - 
pi_getFFvalueFromSheetArray). tx_lib_switch could use thoses static 
methods as well (suggestion).

2) Provide some useful method to convert SPL object from model > 
controller > view. It is a bit anoying to do all theses loops again and 
again. Furthermore, I am wondering about the performance's cost.

3) a question : how SPL objects are handle with PHP 5. I am wondering if 
PHP 5 could be detected and if the default compiled library could be 
used, instead of tx_lib_spl_ArrayIterator and tx_lib_spl_ArrayIterator.

4) About the template engine... long issue... It would be a good thing 
to have an official template engine. Personnaly I don't like very much 
the TYPO3 template engine. I would rather use a "Smarty like" template 
engine. But as Smarty is not included and used in the Core, it's maybe 
too big to add X thousand of lines for just one an extension. What about 
Typo3 5.0 ? Do they have already discussed to reconsider the default 
template engine ? It can make the difference !

5) Show in your demo extension / documentation how to include templates 
in other templates. <?php require('htmlTemplate.php'); ?>

6) Have you ever tried lib/div with ajax calls ? It could be a cool 
example as well. (I need it ;)

7) Do you know somthing about the MVC model in TYPO3 5.0 ? My 
preoccupation is to make the 2 MVC implementations as compatible as 
possible !! According to the last T3N, the TYPO3 5.0 team have made 
progresses. It could be a question to them.

Thank's for sharing your work !


More information about the TYPO3-team-extension-coordination mailing list