Re: [First post][Templates]

Théo wrote: > > I'm hearing something about templates engine in PEAR, and i want to have got > more elements on working advancement about this... here is an archive about > it ? Read the discussion on this topic at: http://marc.theaimsgroup.com/?l=pear-dev&w=2&r=1&s=template+proposal&q=b > I explain me a little bit more ... > I'm writing a template engine for a few time before, his name is ModeliXe, > unfortunately due to my poor english mastering, the documentation is only in > french. > Nevertheless i'm very interesting by PEAR ... and i know that there is > others template engine solutions that are ready to be incorporate in it... > so i'm asking me how i can contribute, and how can ModeliXe be introducing > in PEAR. > Perhaps, in first, i must speak about my template solution ? > In first step, you can find documentations, source and samples, here > http://modelixe.phpedit.com/ ,but only in french for the moment > :-( Pear has now a template engine called IsoTemplates, that can be found under pear/HTML/[IT.php|ITX.php|IT_Error.php]. The final decision was to leave IT as the "low weight" Pear template solution and ocassionaly adapt Smarty as the more powerful solution (if author agrees, etc). So if you want to contribute, IMHO you should contribute to IT. But we (at least me) want to leave IT as simple and small as posible, so IMHO the main work it would need, is improving speed and usability, write doc, fix bugs, etc. Anyway, you can always can follow the Pear Standars, integrate by your self into Pear (errors, use of other pear classes like cache, etc) and benefit of the pear package distribution system. As I'm talking about IT, here I put some minor recomendations to include: - Ability to detect and parse global vars automaticaly. For ex: <form action="{_PHP_SELF_}?id={ID}"> or <input value="{_HTTP_GET_VARS[id]_}"> - Rename (or alias) some methods (do you really like to type so much? :). For ex: setVariable -> assign (or set) setCurrentBlock -> setBlock (or block) parseCurrentBlock | parse |-> parse (no args the current) - Remove IT_Error and trigger errors with raiseError() Please don't get very angry with me, as I haven't look at IT in deep and perhaps I've missed something :) Regards, Tomas V.V.Cox