Hi Benjamin, yup - what Ede describes is what I do too in Eclipse. I have a OpenJUMP project that I setup and run without any addons (but using the default-plugins option) Then I have setup another Project that will contain my own code. As you describe the PlugIn or is Extension class is where I can hook into OJ. Hence, my plugin classes are called using the workbench-properties.xml file that I place in my project - and that is called with the command line option: http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=How_to_use_a_plugin_with_a_properties_file_in_ECLIPSE
It works like default-plugins. Its not truly dynamical and does not work for GUI changes, but for algorithms (and when class variables inside the plugIn class don't change) I can modify code live in Eclipse Debug Mode. stefan PS: sorry, seems like we really should expose the developer primers better - or write a downloadable manual. Am 03.01.12 00:03, schrieb edgar.sol...@web.de: > On 02.01.2012 23:49, Michaël Michaud wrote: >> Hi Benjain and happy new year >> >>> Let's start with the first point, since I really like to know how you guys >>> development cycle is. >>> >>> When I started with OpenJUMP back in April 2009 I typically started Eclipse >>> and opened my Project with an Extension class and some PlugIns. To test >>> changes I had to run an ant task to compile the classes and deploy the jar >>> to the /lib/ext/-directory. Then I started OpenJUMP to execute the PlugIns >>> via the menubar. >>> >>> That was tedious. >> Not that tedious, but it depends on what you are testing. >> For the UI part (which is quite important in my plugins) this kind of cycle >> is difficult to avoid. >> For algorithm part, of course, this is no very efficient, and we miss >> something like a unit test framework. > > uhm, don't want to spoil anything, but you don't have to package a jar for > development. the intended way to develop extensions with plugins is afaik > like this: > > - set up oj core as an eclipse project, add the libs, see that you can run > the workbench class with appropriate arguments > - set up a project for your extension > - add your extension project to the workbench run configuration classpath > - specify a path to a workbench-properties.xml in the run configuration > program arguments and add your extension/plugin in the xml file > - when you (debug)run this you run oj with the ext/plugin loaded > >>> The third step was to make the development cycle even shorter, by run >>> PlugIns dynamically within OpenJUMP. I intent to modify the PlugIns so that >>> you can edit them within Eclipse (or your favorite editor/IDE) and run them >>> within an already started OpenJUMP instance. Or to edit them within >>> Michaëls script editor directly within OpenJUMP and them directly. It is >>> also possible to run JUnit-Tests within OpenJUMP to load Shapefile-Fixtures >>> for the tests. >> I often start my plugins with small beanshell scripts (to understand how jts >> functions work before starting a plugin for example) >> I also heard about tools to reload class dynamically without restarting >> OpenJUMP (Eric, a co-worker, used it for his OpenJUMP plugin, I will ask him) >>> > > when you run the configuration described above in debug mode you can even do > limited hacking and the jre reloads the classes during runtime. > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
