I'm playing around with graphical user interfaces for my gradle scripts. I originally thought about antforms (http://antforms.sourceforge.net/index.html): it works pretty fine in ANT scripts. But I feel that while antforms had to take care of ANT limitations, with gradle we have a "developer-friendlier" environment. So I tried JideBuilkder: here I used the first example from http://griffon.codehaus.org/JideBuilder.
It quite works. Now the problems: 1. I'd *need a way to leave the gradle JVM alive during all the time needed to serve the gui*. In the above example the gradle task exits immediately after the GUI is shown, then the entire jvm terminates. I guess I should make some thread synchronization machinery between the gradle execution thread and the awt one. Alternatively I could launch the gui on another jvm instance, leaving the gradle jvm terminate. In this case the problem would be: how to execute the gui task (closure) on an external jvm? 2. I'd *need a way to call some tasks execution in response of user GUI interaction*: should I recur to the tooling api in order to have a proper task dependency tree? Any idea would be appreciated :-) -- View this message in context: http://gradle.1045684.n5.nabble.com/Experimenting-ways-to-produce-GUIs-from-gradle-scripts-tp5661219p5661219.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
