On 10/31/07, David Nuescheler <[EMAIL PROTECTED]> wrote: > ....(3) how about using the workspace itself as an extension mechanism... > > something like: > > /.microsling/script-engines/esp > /.microsling/script-engines/fm > /.microsling/script-engines/rb > > ... which would host all the mapping information also allow for > dynamic extension and distribution/installation as a content package....
That might be good once people grasp the JCR way of doing things, but if we want people to be able to test the Velocity ScriptEngine in 20 minutes, the standard 15 minutes for microsling leave only 5 minutes to install and test the VelocityScriptEngine. I think microsling beginners will find it easier to drop a jar file somewhere. -Bertrand
