Aw: Re: Remembering imports between script invocations

to let it set the additional imports.   bye Jochen   Gesendet: Donnerstag, 01. November 2018 um 16:19 Uhr Von: "Keith Suderman" An: dev@groovy.apache.org Betreff: Re: Remembering imports between script invocations Hi David,   I am not a Groovy committer and I am not that familiar

Re: Remembering imports between script invocations

n between >>> script invocations, it makes it hard to use Groovy to interactively create, >>> say a Swing or JavaFX UI one line at a time. With BeanShell, the user can >>> add the needed imports, execute that "script" and then continue to refer to >>>

Re: Remembering imports between script invocations

>> the imported classes in the following script invocations. Making Groovy >> remember imports would make it behave in as nice fashion as the new JShell >> tool in Java 9. JShell unfortunately cannot run embedded via the >> javax.script API :-( >> >>

Re: Remembering imports between script invocations

invocations. Making Groovy >> remember imports would make it behave in as nice fashion as the new JShell >> tool in Java 9. JShell unfortunately cannot run embedded via the >> javax.script API :-( >> >> Regards >> /David >> >>> On 8 Feb 2018, at 2

Re: Remembering imports between script invocations

.script API :-( > > Regards > /David > >> On 8 Feb 2018, at 21:34, eric.mil...@thomsonreuters.com >> <mailto:eric.mil...@thomsonreuters.com> wrote: >> >> You can add all the imports you want to your compiler configuration and they >> will be con

Re: Remembering imports between script invocations

too sure myself how the javax.script stuff is tied in. *From:* David Ekholm [mailto:da...@jalbum.net ] *Sent:* Thursday, February 08, 2018 2:47 PM *To:* dev@groovy.apache.org *Subject:* Re: Remembering imports between script invocations How do I do that via the javax.script API? Even if this

Re: Remembering imports between script invocations

.net>] > Sent: Thursday, February 08, 2018 2:47 PM > To: dev@groovy.apache.org <mailto:dev@groovy.apache.org> > Subject: Re: Remembering imports between script invocations > > How do I do that via the javax.script API? > > Even if this is possible via the javax.scrip

RE: Remembering imports between script invocations

Sounds more like the Groovy Shell or Groovy Console. Not too sure myself how the javax.script stuff is tied in. From: David Ekholm [mailto:da...@jalbum.net] Sent: Thursday, February 08, 2018 2:47 PM To: dev@groovy.apache.org Subject: Re: Remembering imports between script invocations How do I

Re: Remembering imports between script invocations

t; > From: David Ekholm [mailto:da...@jalbum.net <mailto:da...@jalbum.net>] > Sent: Thursday, February 08, 2018 2:12 PM > To: dev@groovy.apache.org <mailto:dev@groovy.apache.org> > Subject: Remembering imports between script invocations > > We're considering sup

RE: Remembering imports between script invocations

You can add all the imports you want to your compiler configuration and they will be consistently available for all scripts. From: David Ekholm [mailto:da...@jalbum.net] Sent: Thursday, February 08, 2018 2:12 PM To: dev@groovy.apache.org Subject: Remembering imports between script invocations

Remembering imports between script invocations

We're considering supporting Groovy as an additional scripting language to our web gallery software jAlbum (http://jalbum.net ), but one aspect bugs me: It doesn't seem like import statements are remembered between script invocations. This makes it far harder to use Groovy to