Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-04-18 Thread Sunburned Surveyor
Benjamin, That is a fine looking GUI. Might also be the only time my code was every useful to anyone for anything. :] Any chance you'd consider releasing the code to us? I don't know any Groovy, but I'd like to see what you've done. I'm intereseted in learning how the same porting of OJ function

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-18 Thread Benjamin Gudehus
Hi Michaël! > Do you mean you use groovy as a compiled language and not as a scripting > language ? Have you got a small sample of a grrovy extension for OpenJUMP ? > Yes, indeed, I use Groovy as a compiled language. Here is a simple example for a UnionByAttributePlugIn. http://pastebin.com/ab

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-18 Thread Michaël Michaud
Hi Benjamin, One idea I had which may be related to the plugin management is that OpenJUMP should be able to record plugin actions in macros. Here's my basic idea. void execute(Map macroOptions) { Map optionsForExecute = null; if (macroOptions) { option

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-18 Thread edgar . soldin
On 18.03.2011 03:26, Martin Davis wrote: > > * Without knowing more about the impacts on the development process, I'd say > I'm not really in favour of introducing Groovy into the core JUMP codebase. > It seems like it might complicate coding (especially for people who don't > grok Groovy). I

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-17 Thread Martin Davis
Here's my thoughts on a couple of these topics... * I agree with keeping dependencies as small as possible. This especially applies to "the core". The core could actually be thought of as a few concentric rings of things: the Feature API, the I/O framework (and drivers, including DB drivers)

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-17 Thread Benjamin Gudehus
Hi Michaël, Thanks for your comments and links to docking and plugin libraries/frameworks. > is infonode totally free and opensource ? InfoNode Docking Windows is under GPL. It looks quite good (as one can see in my screenshots) and has a nice API. One idea I had which may be related to the

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-15 Thread Michaël Michaud
Hi Benjamin, Matthias, developpers, Nice to know there are great ideas to enhance OpenJUMP user interface. Here are some comments about Benjamin's main points : - windows docking : totally agree that it would be a nice addition is infonode totally free and opensource ? anyway, there are also :

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-14 Thread Benjamin Gudehus
btw: this is how the gui looks when I deactivate all plugins: http://www.abload.de/img/nicejump_wo_pluginsq71j.png I think this is a nice showcase of how to customize a scalable user interface. here is the corresponding source code for this: static void main(args) { Translation.rese

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-14 Thread Benjamin Gudehus
hallo Matthias! it would be nice to incubate a new GUI in parallel work. Maybe we could split the source code in two modules as I already did: * a workbench with a new gui built from scratch * a core with current OJ code base then substract the old workbench code (successively) from core and

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-14 Thread Matthias Scholz
Nice Work! What do you think about a GUI revision for OJ in 2.0? This can be a longer project of parallel work. Should be no problem with SVN. A more modern and customizable GUI would be a great enhancement for OJ in the future. I know that this is not a small task. Matthias > Hi Michaël! > > The

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-13 Thread Benjamin Gudehus
Hi Michaël! The RCP has a new plugin system which (basically) consists of * a PlugIn class with initialize(PlugInContext) and an execute method without parameters. * a PlugInContext class with getProgramModel(), getProgramFrame() and getPlugInManager(). * a PlugInManager class which stores initia

Re: [JPP-Devel] Some thoughts for future work on the user interface

2011-03-13 Thread Michaël Michaud
Hi, Nice work ! There is surely a lot of work to transfer all the improvements to the last version of OpenJUMP. What do you mean by running PlugIns from OpenJUMP with the new plugin system ? Michaël Le 13/03/2011 21:05, Benjamin Gudehus a écrit : Hi OpenJUMPers, I want to come up with