Folks - I am on board with Jon on this one.
Jon wrote:
> Think in terms of someone who is editing the template who has
> no idea of what a tool even is. All they know is that if they
> put '$ticker.getSymbol("RHAT")' into the template that they
> will get a number as a result.
I don't believe that a Designer should instantiate a tool in the
template. A tool would be available only if a Developer put it there.
IMHO, the optimization/lazy loading Bill presents is something that the
Developer/Framework should handle, not the Template Designer.
Think of the Designer who knows he can "instantiate" a tool called
"Ticker" by using some mojo like so:
#set ( $ticker = $FunkyToolLoader.load("CoolStockTickerVersion3",
"ticker") )
$ticker.getSymbol("RHAT")
So the Designer only loads that tool whenever she 'needs' it and that
makes the system faster?
I doubt it. ;-) I bet the Designer will say, "Why the #$@# do I write
that load thing, it's confusing? And if I want that tool on every page,
do I need to do that #SET on every $#@# page? Ugh."
--
My understanding of the Toolbox was that it was to help the Developer
config/create tool objects automagically to help with rapid prototyping.
Gabe/Geir - what say you gents? Is that correct? If not, what's the
vision/spec for the Tool Loader?
Cheers,
Tim
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
