Re: [PW-dev] Template Toolkit concept

[Jay L. <Ja...@La...>]

This is just theoretical - I am examining what Gunther was driving at....

I am not sure if I like it, tho. I really really wanna just put in my
templates
simple things like [% widget1 %] to have widget named Widget1 show up there.

This can be accomplished now with little difficulty.

I can see the merits of the widget controller now. It might be attractive to
explore passing the widget controller to Template toolkit and take your
approach of  [% wc.widget1 %] for placing widgets.

I am thinking of overhead for setting my my template variables - if I place
each widget into my $vars hash which I send to my template then that's
a lot of overhead. If I constantly have to get Template Toolkit to parse
[% wc.xxx %] that's even more overhead. A future optimization in TT
would be attractive.

J
----- Original Message -----
From: "Stephen Adkins" <ste...@of...>
To: <per...@li...>
Sent: Tuesday, June 12, 2001 7:26 AM
Subject: Re: [PW-dev] Template Toolkit concept


> At 10:25 AM 6/11/2001 -0400, you wrote:
> >> At 11:09 AM 6/6/2001 -0400, Stephen Adkins wrote:
> >> >At 09:53 AM 6/6/2001 -0400, Jay Lawrence wrote:
> ...
> >> In Java I am used to JSPs and we code widgets using taglibs. So the
> >widgets
> >> are objects, but then there is a widget taglib that can display a
widget.
> >>
> >> <widget id='fname'/>
> >>
> >> in JSP parlance for example.
> >
> >So, for example, with Template Toolkit might we have something like:
> >
> >    [% WIDGET fname %]
> >
> >Which would render the widget in place - and of course you could do
things
> >like [% WIDGET fname.value('Jay') %] if you wanted to set it in your
> >template code.
>
> Jay,
>
> Have you written any Template Toolkit specific driver yet to do this?
> Or is this example just theoretical?
>
> Stephen
>
>
>
> _______________________________________________
> Perl-widget-developer mailing list
> Per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-widget-developer
>