Re: Discussion: Move Scripting Code To A Script Component

2012-07-20 Thread Erwan de FERRIERES
Adrian, this is a nice idea. so +1 2012/7/12 Adrian Crum : > Yes, anything to do with scripting would go there. > > -Adrian > > > On 7/12/2012 2:01 PM, BJ Freeman wrote: >> >> would a new scripting language be in the same component. >> >> Adrian Crum sent the following on 7/12/2012 5:57 AM: >>> >>

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread Adrian Crum
Yes, anything to do with scripting would go there. -Adrian On 7/12/2012 2:01 PM, BJ Freeman wrote: would a new scripting language be in the same component. Adrian Crum sent the following on 7/12/2012 5:57 AM: I don't understand the question, sorry. -Adrian On 7/12/2012 1:55 PM, BJ Freeman w

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread BJ Freeman
would a new scripting language be in the same component. Adrian Crum sent the following on 7/12/2012 5:57 AM: I don't understand the question, sorry. -Adrian On 7/12/2012 1:55 PM, BJ Freeman wrote: so how would this work with a new scripting , like business basic. Adrian Crum sent the follow

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread Adrian Crum
I don't understand the question, sorry. -Adrian On 7/12/2012 1:55 PM, BJ Freeman wrote: so how would this work with a new scripting , like business basic. Adrian Crum sent the following on 7/12/2012 2:56 AM: That is true for now, but I was thinking farther down the road. For now we could just

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread BJ Freeman
so how would this work with a new scripting , like business basic. Adrian Crum sent the following on 7/12/2012 2:56 AM: That is true for now, but I was thinking farther down the road. For now we could just consolidate the code in base, common, and minilang. -Adrian On 7/12/2012 10:40 AM, Jacop

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread Adrian Crum
That is true for now, but I was thinking farther down the road. For now we could just consolidate the code in base, common, and minilang. -Adrian On 7/12/2012 10:40 AM, Jacopo Cappellato wrote: Adrian, it is an interesting proposal. If I well understand your proposal then the new "scripting"

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread Jacopo Cappellato
Adrian, it is an interesting proposal. If I well understand your proposal then the new "scripting" component will depend on (mostly) all the 4 components... let me try to explain with an example. A) in theory with the current setup you could enable the service component and that will give you

Re: Discussion: Move Scripting Code To A Script Component

2012-07-12 Thread Adrian Crum
Mini-language could be moved to the script component or it could remain its own component. Some of the things that would be moved are: ScriptHelper.java, Scriptlet.java, ScriptUtil.java, GroovyUtil.java, BshUtil.java, javax.script.ScriptEngineFactory, ContextHelper.java, ScriptHelperFactoryIm

Re: Discussion: Move Scripting Code To A Script Component

2012-07-11 Thread Jacques Le Roux
It's not quite clear to me Jacques From: "Adrian Crum" The code for scripting support is scattered across several different components. I would like to move all scripting-related code to a separate component called "script" or "scripting". I believe this will help make things more modular an

Re: Discussion: Move Scripting Code To A Script Component

2012-07-11 Thread BJ Freeman
are you thinking of just mini, or js, grouvy or what ever? Adrian Crum sent the following on 7/11/2012 7:16 AM: The code for scripting support is scattered across several different components. I would like to move all scripting-related code to a separate component called "script" or "scripting".