> on 9/26/2000 11:19 AM, "John McNally" <[EMAIL PROTECTED]> wrote:
>
> > I think something like the above is a good way to go, rather than
> > hacking ScreenLoader for every new addition.
> >
> > John McNally
>
> I agree. The ScreenLoader changes are making me feel uncomfortable.
>
Any suggestions about loader chains? How about something like this in
TR.properties:
screen.loader=org.apache.turbine.modules.screenLoader
screen.loader=org.apache.turbine.modules.anotherLoader
screen.loader=org.apache.turbine.python.pythonLoader
screen.loader=com.somebody.myLoader
We'll need something like a "master loader" class that cycles through these
loaders until a screen is found or take appropriate error steps. Won't be to
difficult to implement. We will probably need to do the same for actions.
The administrator can then simple add/remove comments from these lines to
include/exclude a screen loader.
Other thoughts?
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
