Re: [PHPiCalendar-DEV] update

[<da...@d2...>]

> David Fallon wrote:
>> Ugh, the switch to not using forms openevent stuff was a can o' worms.
>> This would be vastly easier if we used a real template system - is there
>> a reason we're not using one of the template classes from PEAR?
>> (http://pear.php.net/manual/en/package.html.php) I've used
>> HTML_TEMPLATE_IT, and it works well and the syntax is almost identical
>> (in the template) to what's already there. The code syntax is
>> significantly different, of course, since all the "hard work" (the
>> various regexes all over the place) is abstracted out for you. :) While
>> I should learn my lesson after diving into this rewrite, I volunteer
>> myself to do the switchover if I get approval. This, of course, is a
>> fairly serious rewrite, but continues my "less code" mantra.
>
> Have you had a look at smarty.php.net? We used to use HTML_TEMPLATE_IT
> but smarty has some neat features such as caching that make things
> faster and other nifty features that make templating easier

I haven't looked at it much, but I will take a closer look. In my brief 5
sec. glance after your email, two concerns jumped out - the syntax is
decently different than the existing template stuff in phpicalendar (while
html_template_it is almost identical), and it's not integrated into
php/pear, meaning we'd have to have an additional install requirement. The
second one being the bigger of the two, since I'd definitely recommend
staying away from any additional install requirements.