On Wednesday 10 January 2001 00:39, you wrote:
> On Tue, 09 Jan 2001, you wrote:
> > I like the idea as well as an option, however, I would rather just have
> > the tools made available for the designer without the designer having to
> > copy/paste that line of code into each and every page.
> >
> > In other words, you are embedding a sense of "logic" into the page by
> > requiring someone to code something in there in order to get a certain
> > amount of functionality.
>
> So then, each tool is uniquely identified and stuffed into the context by
> the loader. The page author then has a list of tools to pick from.
>
> So instead of : #set $aTool =
> $toolLoader.getTool("org.apache.velocity.contexttool.SomeTool") I use :
> $sometool
The reason behind the idea is that it may be a lot of tools and many of them
should be part of velocity/turbine. (or at least availaible from velocity for
inclusion in your procject).
But its not sure that so many of them are being used in a project and I have
no clue what the designers may need. So its either a lot of unused tools in
memory or work adding the right tools for every project.
So it would be really nice if it could be an option or at least that the
context stuff is designed in a way that it's possible to add such
functionallity without changing the commited codebase.
regards
killi
--
Penguins are nice animals -
if you get to know them!
- Re: ContextTool stuff - Recycling an Idea Roall Lein-Killi
- Re: ContextTool stuff - Recycling an Idea Geir Magnusson Jr.
- Re: ContextTool stuff - Recycling an Idea Dave
- Re: ContextTool stuff - Recycling an Idea Jon Stevens
- Re: ContextTool stuff - Recycling an Idea Dave Bryson
- Re: ContextTool stuff - Recycling an Idea Jon Stevens
- Re: ContextTool stuff - Recycling an Idea Geir Magnusson Jr.
- Roall Lein-Killi
