Just a thought... What your doing is, to me, very interesting, because it could lead to a complete modularization of OJ. If OJ could be splitted into separate and independent parts (Data access, Catalog, Rendering, GUI, etc.) this can give the opportunity of developing independent application with OJ embedded inside, but also to develop a server version of OJ and even mobile versions. The most valuable part is the rendering. When you have a good rendering system, you can embed it into lots of applications. Data access is very important too... And GUI, also... OK, they're all very important, but now they're a little too much tangled together :-) Have a nice weekend!!!
Bye Paolo > First of all: I think its a good idea to write some more details, how to use > components of openjump in the wiki. My source code is completely written in > groovy. Its a good idea to rewrite the PlugInContextFactory (see beneath) in > Java and keep the other sources in groovy, since unit testing is a blessing > in groovy ;) > > To write functional tests for openjump it is neccessary that you can use > the > components (e.g. LayerManager, LayerViewPanel, Task) independently of the > openjump-gui. A good starting point is to mock the methods of > PlugInContext. > then you will pass the mocked PlugInContext to the initialize() and > execute() > methods of your PlugIns. > > Thus I first created a useful mind map with frequently used components > and their > methods (http://img5.imagebanana.com/view/xlrta89n/PlugInContext.png). > > Most of the components can also be used without the PlugInContext with > nearly > no need to mock something (maybe WorkbenchContext needs to be mocked). > If you > want to use PlugIns you have to mock the PlugInContext. > > I learned many stuff from the openjump-api while investigating, how to > create > the components. Also a big advantage was, that I can run my application > even without starting openjump (I do a lot of small code changes and > want to > see how it behaves immediately ;)) > > So I've created a class called PlugInContextFactory, where I can create > some parts > of a PlugInContext. Static methods deliver the objects (LayerManager, > and so on). > > class PlugInContextFactory > * createTask() > * createWorkbenchFrame() > * createOutputFrame() > > * createLayerManager() > o createFeatureCollection() > * createLayerViewPanel() > > * createWorkbenchContext() > o createBlackboard() > * createFeatureInstaller() > > It was relatively easy to create the Task or the OutputFrame. Ideas to > create a > LayerManager or LayerViewPanel were shown in the eye-opening wiki entry > [1] about > how to use the openjump-api in an external application. Some more work > was required > for a WorkbenchContext or the FeatureInstaller (for menu entries or > toolbar icons). > > Now I show, how I create a PlugInContext for my tests. > > <codeInGroovy> > // Here I prepare all those components, which I later want to call > // within a plugin over the getter methods (e.g. "getLayerManager()"). > def externalConfig = this.loadExternalProperties() > def pluginContextFixture = [ > // List of layers with paths to the shapefiles. > layerManager: PlugInContextFactory.createLayerManager([ > "layer1": this.externalConfig["shapefile.layer1"], > "layer2": this.externalConfig["shapefile.layer2"], > ]), > // The output frame, where my PlugIns sends messages to the user. > outputFrame: PlugInContextFactory.createOutputFrame(), > // The settings for the project file. > task: PlugInContextFixtures.createTask([ > "project.setting1": this.externalConfig["project.setting1"], > "project.setting2": this.externalConfig["project.setting2"], > ]), > workbenchFrame: PlugInContextFactory.createWorkbenchFrame("openjump"), > // A WorkbenchContext with an Blackboard, for instance to store > // datebase connection information. > workbenchContext: PlugInContextFactory.createWorkbenchContext([ > "getBlackboard": PlugInContextFactory.createBlackboard( > "app.userPrefs": PlugInContextFactory.createUserPrefs([ > "app.setting1": this.externalConfig["app.setting1"], > "app.setting2": this.externalConfig["app.setting2"], > ]), > ), > ]), > ] > // We need do pass a LayerManager to the LayerViewPanel. > pluginContextFixture += [ > layerViewPanel: PlugInContextFactory.createLayerViewPanel( > this.pluginContextFixture.layerManager), > ] > > // Now you can use the elements in pluginContextFixture and do something > // with them. I want to mock them as a PlugInContext(), so I can later send > // the PlugInContext to a plugin. Therefore I use GMock which is something > // like EasyMock for Groovy. mockContextFixture() will add the ability > // to create a PlugInContext within a play-closure. Also "get" is added to > // the method names. > this.gmockController = new GMockController() > mockContextFixture(pluginContextFixture, this.gmockController) > > // Now execute a PlugIn. > this.gmockController.play { > def pluginContext = new PlugInContext() > > def plugin = new ExamplePlugIn() > plugin.initialize(pluginContext) > plugin.execute(pluginContext) > > // Do something with plugin and the pluginContext... > def layer = pluginContextFixture.getLayerManager().getLayer("layer1") > assert layer.getFeatureCollectionWrapper().getFeatures().size() > 0 > } > </codeInGroovy> > > I successfully tested my swing guis for openjump with the uispec4j library. > For some components I created helper classes, to help with many tedious > tasks. For example ProjectPropertiesManager will help with Tasks, > LayerHelper with modifying FeatureSchema (which is a tricky task) and > ClosureBooleanEnableCheck to create a EnableCheck with a closure (a > syntactical > feature in Groovy). > > [1] > http://www.openjump.org/wiki/show/Using+JUMP+Libraries+in+an+External+Application > > > 2009/10/1 Sunburned Surveyor <sunburned.surve...@gmail.com > <mailto:sunburned.surve...@gmail.com>> > > Benjamin, > > I look forward to learning more about your work. One thing OpenJUMP > could use is some more testing. > > Landon > > On Thu, Oct 1, 2009 at 9:58 AM, Stefan Steiniger <sst...@geo.uzh.ch > <mailto:sst...@geo.uzh.ch>> wrote: > > Hei Benjamin, > > > > every code return is warmly welcome! > > > > if you feel that this is worth a new tree/module on our SVN code > > repository and/or you want access. Please tell me. > > > > However, SVN write access is granted after some sample code has been > > approved by 1-2 core people or somebody of the core team knows your > > skills. However, if you have that much skills to change OJ > components I > > have no doubts that I can grant you access a.s.a.p. if you wish. > > > > Well.. and just in general, everyone who is willing to help coding, > > writing docs, keeping the wiki(s) uptodate or even wants to do > marketing > > is welcome :) > > > > cheers from sunny Calgary > > stefan > > > > Benjamin Gudehus wrote: > >> Hi. > >> > >> I wrote a bunch of methods to mock some components of openjump to do > >> unit tests and functional tests. I'm planning to use this > knowledge to > >> write an external application using the openjump-api. > >> > >> I spend several hours to figure out, how to mock them and hope to > >> contribute some of my code. As soon as I am back at work > (monday) I'll > >> try to post some source code. > >> > >> 2009/9/30 Jayaram Reddi <jre...@gmail.com > <mailto:jre...@gmail.com> <mailto:jre...@gmail.com > <mailto:jre...@gmail.com>>> > >> > >> Thanks for the feedback! I have been looking at the source > code and > >> piecing together bits, but its a formidable task. I asked for an > >> object model diagram because i used them quite extensively > when i > >> developed some simple applications with ArcGIS, the OMD > helped quite > >> a bit in understanding which object made up which component, > e.g. so > >> and so objects are needed to construct the table of contents. > >> > >> Help is much appreciated, hopefully in the future i'll have > >> something to contribute. > >> > >> Jayaram > >> > >> > >> On Wed, Sep 30, 2009 at 2:24 AM, Sunburned Surveyor > >> <sunburned.surve...@gmail.com > <mailto:sunburned.surve...@gmail.com> > <mailto:sunburned.surve...@gmail.com > <mailto:sunburned.surve...@gmail.com>>> > >> wrote: > >> > >> Also, don't underestimate this mailing list as a > resource. If > >> you ask > >> intelligent and well thought-out questions (after you've > looked > >> at the > >> Javadoc and peeked at the source code) you will get > intelligent, > >> well > >> thought-out answers from some of our best programmers. > >> > >> The Sunburned Surveyor > >> > >> On Tue, Sep 29, 2009 at 1:53 PM, Sunburned Surveyor > >> <sunburned.surve...@gmail.com > <mailto:sunburned.surve...@gmail.com> > >> <mailto:sunburned.surve...@gmail.com > <mailto:sunburned.surve...@gmail.com>>> wrote: > >> > Another way to study OpenJUMP is as a set of systems that > >> focus on a > >> > set of tasks. > >> > > >> > For example: > >> > > >> > - The rendering system, which controls the display and > >> appearance of > >> > spatial data in OpenJUMP. > >> > - The I/O system, which controls the input and output of > >> spatial data. > >> > - The cursor tool system, which controls user interaction > >> with the map > >> > (LayerViewPanel). > >> > - The plug-in management system, which allows > functionality to be > >> > loaded modularly. > >> > > >> > As Larry mentioned, by checking out just a few key > classes in > >> Eclipse > >> > you can weave your way through the most important > parts of > >> the code. I > >> > use the "open call heirarchy" function in Eclipse to > do this > >> quite > >> > frequently when I am lurking around in OpenJUMP's > core. Some > >> of these > >> > key classes you can start investigating are: > >> > > >> > JUMPWorkbech > >> > WorkbenchContext > >> > PlugInManager > >> > PlugInContect > >> > LayerViewPanel > >> > RenderingManager > >> > DataSource > >> > Layer > >> > LayerManager > >> > > >> > The Sunburned Surveyor > >> > > >> > On Tue, Sep 29, 2009 at 1:31 PM, Larry Becker > >> <becker.la...@gmail.com <mailto:becker.la...@gmail.com> > <mailto:becker.la...@gmail.com <mailto:becker.la...@gmail.com>>> wrote: > >> >> We seem to be getting a lot of requests for object > models > >> lately. IMHO, > >> >> object models do not help much in understanding how JUMP > >> works. Eclipse > >> >> constructs these on-the-fly, after all. You would > be better > >> off studying > >> >> the event handling and threading. JUMP is best > thought of > >> as a loose > >> >> association of plug-ins that cooperate though a > hierarchy of > >> event handlers > >> >> managed by the Workbench. > >> >> > >> >> Larry > >> >> > >> >> On Tue, Sep 29, 2009 at 2:54 PM, Stefan Steiniger > >> <sst...@geo.uzh.ch <mailto:sst...@geo.uzh.ch> > <mailto:sst...@geo.uzh.ch <mailto:sst...@geo.uzh.ch>>> wrote: > >> >>> > >> >>> however, if you want to stick to java then there is > only > >> geotools (as a > >> >>> library package), gvSIG and uDig .. the later maybe as > >> difficult to > >> >>> customize but may have better documentation: > >> >>> see: > >> >>> > >> >>> http://www.spatialserver.net/osgis/ > >> >>> > >> >>> > >> >>> Sunburned Surveyor wrote: > >> >>> > I agree with Larry's comments. What you are > talking about > >> can be done, > >> >>> > but I think it would be a challenge even for some > of our more > >> >>> > experienced OpenJUMP programmers. OpenJUMP is > quite a beast. > >> >>> > > >> >>> > Check the developer's guide, and then ask on this > mailing > >> list if you > >> >>> > have specific questions about OpenJUMP's > architecture. > >> >>> > > >> >>> > The Sunburned Surveyor > >> >>> > > >> >>> > On Tue, Sep 29, 2009 at 10:46 AM, Larry Becker > >> <becker.la...@gmail.com <mailto:becker.la...@gmail.com> > <mailto:becker.la...@gmail.com <mailto:becker.la...@gmail.com>>> > >> >>> > wrote: > >> >>> >> The JUMP Developer Guide is the best source of > design > >> information. > >> >>> >> What you > >> >>> >> are trying to do is very difficult. It has been > done, > >> but since they > >> >>> >> were > >> >>> >> external projects, no information or source code was > >> ever returned to > >> >>> >> the > >> >>> >> project. You might want to investigate a more > >> appropriate toolkit like > >> >>> >> GeoTools. > >> >>> >> > >> >>> >> regards, > >> >>> >> Larry Becker > >> >>> >> > >> >>> >> On Tue, Sep 29, 2009 at 12:11 PM, Jayaram Reddi > >> <jre...@gmail.com <mailto:jre...@gmail.com> > <mailto:jre...@gmail.com <mailto:jre...@gmail.com>>> > >> >>> >> wrote: > >> >>> >>> Hello all, > >> >>> >>> > >> >>> >>> I am new to OpenJump and I would like to > request some > >> help with > >> >>> >>> developing external applications using > OpenJump's API. > >> I would like to > >> >>> >>> use > >> >>> >>> the visualization and processing capabilities > of OJ in > >> my own java > >> >>> >>> application. I have spent a few hours looking > through the > >> >>> >>> documentation and > >> >>> >>> wading through the mailing list archives hoping > to find > >> some leads > >> >>> >>> into > >> >>> >>> developing applications with OJ. I cam across > the one > >> sample file with > >> >>> >>> code > >> >>> >>> on how to use the layerviewpanel and load a few > >> shapefiles into it. > >> >>> >>> From > >> >>> >>> there on its been difficult to figure out which > objects > >> do what and in > >> >>> >>> what > >> >>> >>> order or arrangement, Is there an object model > diagram > >> available? As > >> >>> >>> of now > >> >>> >>> I would like to make a simple GIS viewer that > can add > >> layers and list > >> >>> >>> them. > >> >>> >>> If i can manage that I'll try my hand at > something more > >> advanced. My > >> >>> >>> eventual goal is to integrate it with an agent > based > >> model i have > >> >>> >>> written in > >> >>> >>> java. > >> >>> >>> > >> >>> >>> Appreciate any help. > >> >>> >>> > >> >>> >>> Jayaram > >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > >> > > ------------------------------------------------------------------------------ > >> >>> >>> Come build with us! The BlackBerry® Developer > >> Conference in SF, CA > >> >>> >>> is the only developer event you need to attend this > >> year. Jumpstart > >> >>> >>> your > >> >>> >>> developing skills, take BlackBerry mobile > applications > >> to market and > >> >>> >>> stay > >> >>> >>> ahead of the curve. Join us from November 9-12, > >> 2009. Register > >> >>> >>> now! > >> >>> >>> http://p.sf.net/sfu/devconf > >> >>> >>> _______________________________________________ > >> >>> >>> Jump-pilot-devel mailing list > >> >>> >>> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> >>> >>> > >> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> >>> >>> > >> >>> >> > >> >>> >> > >> >>> >> -- > >> >>> >> Larry Becker > >> >>> >> Integrated Systems Analysts, Inc. > >> >>> >> > >> >>> >> > >> >>> >> > >> > > ------------------------------------------------------------------------------ > >> >>> >> Come build with us! The BlackBerry® Developer > >> Conference in SF, CA > >> >>> >> is the only developer event you need to attend this > >> year. Jumpstart > >> >>> >> your > >> >>> >> developing skills, take BlackBerry mobile > applications > >> to market and > >> >>> >> stay > >> >>> >> ahead of the curve. Join us from November 9-12, > >> 2009. Register > >> >>> >> now! > >> >>> >> http://p.sf.net/sfu/devconf > >> >>> >> _______________________________________________ > >> >>> >> Jump-pilot-devel mailing list > >> >>> >> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> >>> >> > >> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> >>> >> > >> >>> >> > >> >>> > > >> >>> > > >> >>> > > >> > > ------------------------------------------------------------------------------ > >> >>> > Come build with us! The BlackBerry® Developer > >> Conference in SF, CA > >> >>> > is the only developer event you need to attend > this year. > >> Jumpstart your > >> >>> > developing skills, take BlackBerry mobile > applications to > >> market and > >> >>> > stay > >> >>> > ahead of the curve. Join us from November > 9-12, 2009. > >> Register > >> >>> > now! > >> >>> > http://p.sf.net/sfu/devconf > >> >>> > _______________________________________________ > >> >>> > Jump-pilot-devel mailing list > >> >>> > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> >>> > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> >>> > > >> >>> > > >> >>> > >> >>> > >> >>> > >> > > ------------------------------------------------------------------------------ > >> >>> Come build with us! The BlackBerry® Developer > >> Conference in SF, CA > >> >>> is the only developer event you need to attend this > year. > >> Jumpstart your > >> >>> developing skills, take BlackBerry mobile > applications to > >> market and stay > >> >>> ahead of the curve. Join us from November 9-12, > 2009. > >> Register > >> >>> now! > >> >>> http://p.sf.net/sfu/devconf > >> >>> _______________________________________________ > >> >>> Jump-pilot-devel mailing list > >> >>> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> >>> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> >> > >> >> > >> >> > >> >> -- > >> >> Larry Becker > >> >> Integrated Systems Analysts, Inc. > >> >> > >> >> > >> > > ------------------------------------------------------------------------------ > >> >> Come build with us! The BlackBerry® Developer > Conference > >> in SF, CA > >> >> is the only developer event you need to attend this > year. > >> Jumpstart your > >> >> developing skills, take BlackBerry mobile > applications to > >> market and stay > >> >> ahead of the curve. Join us from November 9-12, > 2009. > >> Register now! > >> >> http://p.sf.net/sfu/devconf > >> >> _______________________________________________ > >> >> Jump-pilot-devel mailing list > >> >> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> >> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> >> > >> >> > >> > > >> > >> > > ------------------------------------------------------------------------------ > >> Come build with us! The BlackBerry® Developer > Conference in > >> SF, CA > >> is the only developer event you need to attend this year. > >> Jumpstart your > >> developing skills, take BlackBerry mobile applications > to market > >> and stay > >> ahead of the curve. Join us from November 9-12, 2009. > >> Register now! > >> http://p.sf.net/sfu/devconf > >> _______________________________________________ > >> Jump-pilot-devel mailing list > >> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> > >> > >> > >> > > ------------------------------------------------------------------------------ > >> Come build with us! The BlackBerry® Developer Conference > in SF, CA > >> is the only developer event you need to attend this year. > Jumpstart your > >> developing skills, take BlackBerry mobile applications to > market and > >> stay > >> ahead of the curve. Join us from November 9-12, 2009. > Register > >> now! > >> http://p.sf.net/sfu/devconf > >> _______________________________________________ > >> Jump-pilot-devel mailing list > >> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> > > ------------------------------------------------------------------------------ > >> Come build with us! The BlackBerry® Developer Conference in > SF, CA > >> is the only developer event you need to attend this year. > Jumpstart your > >> developing skills, take BlackBerry mobile applications to market > and stay > >> ahead of the curve. Join us from November 9-12, 2009. > Register now! > >> http://p.sf.net/sfu/devconf > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> Jump-pilot-devel mailing list > >> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry® Developer Conference in > SF, CA > > is the only developer event you need to attend this year. > Jumpstart your > > developing skills, take BlackBerry mobile applications to market > and stay > > ahead of the curve. Join us from November 9-12, 2009. > Register now! > > http://p.sf.net/sfu/devconf > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > ------------------------------------------------------------------------ > > This body part will be downloaded on demand. > > > ------------------------------------------------------------------------ > > This body part will be downloaded on demand. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
