On 10-12-06 10:46 PM, Dmitriy Sintsov wrote:
- Daniel Friesenlists@nadir-seen-fire.com [Mon, 06 Dec 2010 03:18:44
-0800]:
I've been chipping away at our skins system lately, there's a lot we
can
improve to improve the skins system. Right now there's a lot of it that doesn't work so nicely for an ecosystem promoting the creation of a wide variety of skins.
Nice work and good looking skin! By the way, I've always wondered why QuickTemplate::execute() itself could not be divided into separate smaller methods for different parts of layout. Such way one might inherit base Skin then alter only few lines, instead of patching or re-implementing the whole execute(). Currently, the base class QuickTemplate is too much limited. Dmitriy
Well, from what I see QuickTemplate was mostly built as an actual template, ie: it's purpose was the setting and use of variables of data stored in the template, some sort of holdover from the PHPtal days.
With my latest commit I did create a BaseTemplate extended from QuickTemplate, that will act as the new class to extend instead of QuickTemplate and will have a bunch of helpers to handle common ways we interact with the data that SkinTemplate sets on QuickTemplate based templates.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]