[TYPO3-ect] lib/div 1.0 - it's time to say thank you

[Elmar HInz]

Hi Steffen,

>>
> How should this be done ? I have an access but not sure if its possible to 
> access div/lib. Where should there be uploaded, and how do you coordinate 
> this ?
> 
> I will make the smarty connection for the beginning ;-)
> 

Promise? 

First, it would be usefull to get the extension "Smarty Template Engine"
with the key *smarty* updated. Last update was 2005. Maybe you can reach
Peter Knöll <pknoell at gmx.de>. If not you can try to contact the
responsible persons and ask if they could assign the key to you. Last
option, take a new extension key.

I think the smarty classes should stay within their own extension,
because they will throw a lot of XCLASS warnings and should be seperated
for this reason from "clean" TYPO3 code.

Second, we need to create a common view class tx_lib_view like Ernesto
proposed today. That should be trivial. That's my part.

Third, from tx_lib_view you would inherit the smarty connector. I think
smarty is relevant enough that the connector can be integrated into the
extension lib itself. The classname would be tx_lib_smartyView. 

As far as I know there are no write access restrictions within the team of
typo3xdev developers. So you can simply start. I hope that no big
organization is needed then. You are responsible for the class
tx_lib_smartyView. I will review it and include it into the TER realease
as soon as it looks stable enough for that.

So for the next steps. I will make tx_lib_view, to work out the common
view interface, you organize the smarty stuff. Right? 

Thank you for joining in

Elmar