Re: Re: an HTML_Template_IT[X] fork is available

11 Февраль 2003 19:32, Christian Dickmann написал: > > prepared one is loaded instead, with a cheap unserialize() instead > > of very expensive RegExp matching logic. > > Why not use PEAR::CacheLite and cache the Template class within > ones program? Why do we need a caching inside IT? IT is simple, if I > want a more advanced and blown template engine I use Smarty. It does not cache the whole object, it just caches individual template files. And the cached version is regenerated when the original one changes. The hooks are all there, there is a possibility to use PEAR::CacheLite from inside the IT. Only it would add more overhead, rather then less. Besides, now the caching is completely transparent, unlike your proposed solution. > > d) Using <!-- INCLUDE something --> in template is no more possible. If > > one > > > needs unconditional include, he should consider joining the > > templates into single file, if one needs something more useful, he should > > use > > ITX > > > with its addBlockfile() method. > > I _really_ _need_ this feature (I added it). Its really important to me, > without it, I couldn't use IT anymore, so a clear > -1 on this. Ugh, was this feature added when addBlockfile() was not working? Besides, what's the advantage of unconditional include instead of keeping it all inside one file?