John McNally wrote:
> > Again, maybe we could have JavaLoader, JPythonLoader, RhinoLoader that would
> > were responsible for loading and launching assemblers, and they could
> > be installed/removed at administarators discretion?
> I think something like the above is a good way to go, rather than
> hacking ScreenLoader for every new addition.
Some of the stuff is already in place. All Loaders extend GenericLoader, and
Action, Screen, Navigation all extend Assembler.
We could define a service that would make a centralized point of access to
all Loaders, and delegate functionality to specific Loader classes (Java, JPython,
Rhino etc.).
Does this make sense?
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
