Re: [JPP-Devel] Question about Mneu Items for Plugins

Dear Michael Yes, I think that would be quite OK Geoff Michaël Michaud wrote: >> Juar a thought however, It might be worthwhile establishing a standard >> name (in English and other languages) for at least one menu item that >> could be used by plugin developers to add items too. I know we c

Re: [JPP-Devel] Question about Mneu Items for Plugins

> (1) Simplicity, especially from the plug-in developers perspective. I > don't think it would be wise to require plug-in developers learn an > additional GUI toolkit. If we can use the toolkit in the core without > requiring it for plug-ins, I'd feel better. In the way I imagine that, the plu

Re: [JPP-Devel] Question about Mneu Items for Plugins

hi, there is as well a class MenuNames.java which provides default values (necessary for translation). Apart from extension there is also one called simply "PlugIns" please have a look on that class. But it is only available in OpenJUMP stefan Geoffrey G Roy schrieb: > Dear Michael > > Yes, I

[JPP-Devel] R: OpenJUMP and postgreSQL/PostGIS

Hi Michaël, I'm glad to see you took the time to look into the different PostGIS drivers and here follows details about mine. If you wonder why I wrote it in the first place, having the others available, the problem was that we have mixed case names for tables and fields (i.e. "ElementoStradale"

Re: [JPP-Devel] Question about Mneu Items for Plugins

I thought that it was time to start a new thread for this topic since the original one was up to 15 posts and was kind of hijacked anyway. :-) To sum things up so far. Michaël and Sunburned seem to be interested in making OpenJumps GUI configurable by using an external XML file. I am mostly inte

Re: [JPP-Devel] Question about Mneu Items for Plugins

I've separated this post from the previous one because this one simply presents my opinion and does not have anything to do with the right way to implement a feature. My premise is that user configurable GUIs are a "bad thing." Sure, they can be lots of fun and I will admit to having enjoyed chan

Re: [JPP-Devel] Question about Mneu Items for Plugins

Right on Larry! I have exactly the same opinion (which is one reason why we didn't spend any time creating an XML UI config file in the first place). The other advantage of having the UI config in Java is that then the development tools manage change for you (e.g. if you change the name or int

Re: [JPP-Devel] Question about Mneu Items for Plugins

Larry, Please see my comments below. SS You wrote: "I am mostly interested in using the already existing workbench-properties.xml to allow lib/ext plugins to be added without the necessity of creating an Extension." I think this is an idea with merit. I never really understood the point of the

Re: [JPP-Devel] Question about Mneu Items for Plugins

I think I need to clarify something. :] I was only participating in the discussion with Michael, and I don't have my heart set on a GUI that can be configured by the user. I definitely don't have any time to work on another feature. (If I take on something else I think Stefan will choke me with h

Re: [JPP-Devel] Question about Mneu Items for Plugins

I meant to say "This does create a little more work for the developer, but is easier for the user", not "This does create a little more work for the developer, but is easier for the developer." Sorry if that confused any readers. SS On 5/9/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote: Lar

Re: [JPP-Devel] OpenJUMP and postgreSQL/PostGIS

puh.. well done investigations sounds like we need to throw off the postgis_1_0_0 code and make the jump-internal datastore framework work??? Actually the postgis_1_0_0 jar file was as well from original JUMP if i remember correctly? stefan Michaël Michaud schrieb: > Hi everybody, > > I trie

[JPP-Devel] Rationale for Extension concept

In response to SS's puzzlement about the Extension concept, here's the rationale: Originally JUMP just had the concept of plugins, but this quickly turned out to be limiting. Many JUMP add-ons (to use a neutral term) comprise a whole collection of inter-operating plugins. They may also contai

Re: [JPP-Devel] New Feature Documentation Sample

SS, a couple of comments: - where's the logo from? Is this OJ's new logo? (I've always thought it should use the Kangaroo from the Jump-Project pages - I can probably make sure this is available if there's interest) - It might be helpful to show the entire OJ screen in at least some of the s

Re: [JPP-Devel] New Feature Documentation Sample

Martin, Thank you for the response. You wrote: "Where's the logo from? Is this OJ's new logo? (I've always thought it should use the Kangaroo from the Jump-Project pages - I can probably make sure this is available if there's interest)" This is the logo that I had designed for the JUMP Pilot

Re: [JPP-Devel] New Feature Documentation Sample

Sunburned Surveyor wrote: > > You can learn more about Scribus here . It > is basically an open source version of Microsoft Publisher, only I > like it more. :] As far as I know the SLA he file format used by > Scribus is not proprietary. Yay! I'll have to check it ou

Re: [JPP-Devel] Rationale for Extension concept

Martin, This should be very helpful to Larry and others. I will take a close look at the Javadoc and source code for the Extension and Registry classes in the next couple of days. Thanks for the great explanation. The Sunburned Surveyor On 5/9/07, Martin Davis <[EMAIL PROTECTED]> wrote: In r

Re: [JPP-Devel] Question about Mneu Items for Plugins

Thanks a lot you for your participation to this debate about ui. Larry helped me a lot to make the question clearer, and both his opinion and Martin's one are very important to me. Thanks also to SS who helped me to weigh the pros and cons. My feelings were (I say were because I'm not so sure any

Re: [JPP-Devel] R: OpenJUMP and postgreSQL/PostGIS

Hi Paolo, Thanks for your reply, it makes things clearer to me. If I may, I would like to ask 2 or 3 more questions. Do you mean that you cannot access mixed case table names or field names from OpenJUMP's standard plugin, even quoting the names like "tablename".'fieldname" ? I should try anyway

Re: [JPP-Devel] Rationale for Extension concept

I add my thanks, So more easy to understand with some clear explanations from the designer than trying to read java code in my favorite editor :-) . I'll add this in the wiki. Michael Sunburned Surveyor a écrit : > Martin, > > This should be very helpful to Larry and others. I will take a clos

Re: [JPP-Devel] Rationale for Extension concept

My thanks too, Martin. I guess I hadn't understood the nuances that you brought out about Extension and Registry. For example, we haven't been overriding the getVersion() method in our Extension (fixed now). So after all of this discussion, where are we? Michaël still needs an easier method of

Re: [JPP-Devel] Rationale for Extension concept

>The >workbench-properties file would allow these users to only install the >features they need, and are compatible with their version of OpenJump. > > Hi Larry, Let me do it completely clear. The workbench properties file seems to already have the feature you describe. One can read from the d

Re: [JPP-Devel] Rationale for Extension concept

Hi Michaël, You are right. No additional functionality is required. There is only one problem. It doesn't work right now unless you are in the development environment. At least, I have never been able to get it to work in a runtime deployed version of JUMP. Larry On 5/9/07, Michaël Michaud <

Re: [JPP-Devel] Rationale for Extension concept

Larry Becker wrote: > > Michaël still needs an easier method of associating menu items with > plug-ins. Perhaps just additional convenience methods in > FeatureInstaller? The OJ committee will have to decide this. > Yes, it seems like some well-designed convenience methods might give Micha

Re: [JPP-Devel] Rationale for Extension concept

Hmm... if that's the case, it would be nice to get that fixed. That might take care of your problem right away. I think the workbench-properties file assumes that the referenced plugins are already in your classpath - could that be the problem? I agree that this isn't great for the average u

Re: [JPP-Devel] Rationale for Extension concept

"Too much good stuff." I think Martin and Larry have gone a little over my head. :] I will try to take a closer look at the Extension class so I can understand what they are talking about. I hope that we can find a clean solution that will meet Larry's needs. He and his team at ISA really do gre