Re: [JPP-Devel] make own extension / plugin dependencies

Hi Carl, >can somebody say to me whether dependencies between the plugins are possible or how the communication is between those? Unless you are asking about determining if a plugin is present at run-time, dependency between plugins is managed with the normal Java Class dependency import statemen

Re: [JPP-Devel] make own extension / plugin dependencies

Hei Carl, what I do is using the blackboard. e.g. one plugin dies this: context.getWorkbenchContext().getBlackboard().put(IS_DATASET_ID, datasetid); and the other this: datasetid=context.getWorkbenchContext().getBlackboard().getInt(IS_DATASET_ID); note: . instead of blackboard.getInt() also oth

Re: [JPP-Devel] Feature Info Button in View / Edit Attributes is gray

Yes, It looks like that you did not change the EnableCheckFactory, while you did this for the speed improvements. The necessary changes for the speed improvements are also not in SelectionManager, i.e. the XXXCount methods. I think we leave it as it is right now (due to some additional changes

[JPP-Devel] make own extension / plugin dependencies

hello, i am new user of this list and the openjump software. i want to build an extension with different functions. with the help of the plugin-tutorial i did easy plugins, e.g. one which do db access, other changes attributes or schema..). however, can somebody say to me whether dependencies b

Re: [JPP-Devel] Feature Info Button in View / Edit Attributes is gray

Hi Stefan, So did I apply the same fix to SkyJUMP as I did to OpenJUMP? I'm guessing that I didn't. Do we need to back out that change and live with the performance problems (for million point tasks)? Larry On Wed, Mar 19, 2008 at 3:21 PM, Stefan Steiniger <[EMAIL PROTECTED]> wrote: > Hei L

Re: [JPP-Devel] Feature Info Button in View / Edit Attributes is gray

Hei Larry, the error does not appear in SkyJUMP :) stefan Larry Becker wrote: > Stefan, > > The sourceforge sources are up to date for SkyJUMP. > > Larry > > On Fri, Mar 14, 2008 at 12:25 PM, Stefan Steiniger <[EMAIL PROTECTED] > > wrote: > > Hei Larry, > >

Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests

Peppe, What you are talking about is possible, but I'm not sure it is simple. :] We would need to only read and write the sections of the project file that we are concerned with, and leave the other sections untouched. It could be done. Let's see what the Kosmo guys have to say. Landon On Wed,

Re: [JPP-Devel] developer role

Hei Mukesh, It depends what you will do, and what your project has for needs. We can add you as developer to the project (so that you have write access under those conditions: a) we know about you project (i.e. What are you going to develop? We need to see that your developments are of common i

Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests

SS wrote: > I didn't think about having > the ability to > export a Kosmo or OpenJUMP project file from each > respective program, > but it is a good idea. or find a new 3rd file format that save both projects characteristics (topologic rules, SLD, layer and tables relations, hiperlinks

Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests

Peppe wrote: "Hi, the discussion is going down, probabily we need more time to "digest" the proposal." I don't think we need more time to digest. We just get busy and things die off. Thanks to Peppe for keeping the conversation alive! Kosmo Programmer wrote: "About plug-in models, both Openjump

Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests

Hi again. Your message arrived me later than my previous one, so I am here again. Of course, the SLD is too a good way to give users benefit from both projects just in the moment OpenJump get it (it seems it is coming soon :-) ). Best Regards Antonio Muñoz Giuseppe Aruta escribió: > Hi, the d

Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests

Dear all. Sorry for delay. We think the way Giuseppe show and SS comment can be good like a medium term. This is because it is user driven, and the user could get the benefits. About plug-in models, both Openjump and Kosmo are quite different, and it is not easy to do it without a very hard jo

Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests

Hi, the discussion is going down, probabily we need more time to "digest" the proposal. Anyhow I propone another "path" of collaboration betwee OJ and Kosmo. I saw on "List of changes" that Andreas is working a lot on SLD import/export plugin (I image ter related plugin (ImportSLDPlugIn.java and S