On Thu, 01 Jun 2000, you wrote:
> How about lines in TurbineResources.properties like:
>
> webmacro.context.page = org.apache.turbine.util.webmacro.WebMacroPageAttributes
> webmacro.context.formatter = org.apache.turbine.util.webmacro.WebMacroFormatter
I think this could run into a problem if the number of tools grow ( an
entry for each ). What about taking an approach similiar to the way
WebMacro loads all of it's ContextTools ( see the WM properties ).
Hey, maybe even _use_ the WebMacro.properties file for this stuff?
> Where the class can implement TurbineWebMacroTool
>
> interface TurbineWebMacroTool
> {
> public void setRunData(RunData data)
> }
>
> and get hold of the RunData when constructed?
>
I think this is a good idea. We should then convert all our current
utils/tools to implment this interface.
> (I'm not sure about TurbineWebMacroTool as a name for
the interface - it seems like the interface might have more general uses? Any ideas?)
How about TurbineWebMacroContextTool ?
And also, good work on the $page.... stuff!
--
dave
[EMAIL PROTECTED]
----------------------
Just your average Joe armed with an Emacs editor.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
