Re^4: The history of a templating engine

I'm still waiting for the proof? I see some interesting design decisions, but I'm not seeing the "proof" that its simpler. I would appear that the writer thought a lot more about what someone could want to do someday, maybe. So, he's more generic and complicated. You are less generic and less complicated. That's about all you’ve proved to me.

Comment on Re^4: The history of a templating engine

Replies are listed 'Best First'.
Re^5: The history of a templating engine by powerman (Friar) on Sep 20, 2006 at 10:43 UTC
Hmm. Can you ask less generic question, please? :) What exactly is 'less generic' in my solution? 'Tag names' and attached 'result convertion' action can be made configurable as I show in previous post without introducing significant complexity, if any. This way I'll have things like "<% ... \|blog %>": `$t->text('<%', '\|blog %>', \&MyBlog);` [download] 'include template' feature can be developed in many different ways, from simple including header/footer templates (which will in most case doesn't have any perl code at all, or will use few local()'ized global variables) to something OO-like which surely may be very complex.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: The history of a templating engine
by powerman (Friar) on Sep 20, 2006 at 10:43 UTC

'Tag names' and attached 'result convertion' action can be made configurable as I show in previous post without introducing significant complexity, if any. This way I'll have things like "<% ... |blog %>":

$t->text('<%', '|blog %>', \&MyBlog);
[download]

'include template' feature can be developed in many different ways, from simple including header/footer templates (which will in most case doesn't have any perl code at all, or will use few local()'ized global variables) to something OO-like which surely may be very complex.

[reply]
[d/l]