Re: Package Proposal: HTML_Template_Dummy

I like you rimplementation, it is quite nice I might add and simple. The only thing stoping me from givinig it a +1 is it's length of usefull code as far as I can see there are three methods, which actually contribute the logic and functionality of the class, and two of them are mutially excusive (in term of flow of data fetch and display are the same, just one would print the results and the other return them, unfortunatelly you have to do ob capturing and I guess there is no better way of handling it, you could skip the first file check in fetch thow, you are checking for file existance in fetch) Anyhow I don't see the use of this class, it is too short to be usefull, anyone needing such functionality could come up with it in a matter of minutes. On a more positive side, for this to become usefull i would expect to see some smarty like features, a bunch of plugins, modifiers and functions. basically i would like to see a smarty (or at least a framework twards it maybe not all the functianality but at least some frameword twards it, sublassing your class to add the extra functionality is really not the way for me) Now why would you do this for a mere +1 i could not bigin to imagine, espesially knowing what the general attitude twards templates in PEAR. I do like the php only aproach for templates but I really see no need for a 15 line class to encapsulate that logic, which involves checking for file existance and including it plus copying variables around a class, i think the point am trying to make (i just realize what it is my self), is if you will be using php as a template system just use it as it is insead of going and imitating a solution which you are trying to avoid Yavor