Re: [JPP-Devel] Weekly Build Disconintued
Done Stefan. I addded also this other idea: We can group, in Layer menu, similar items in submenu, eg. Change style, Copy style and paste style coulg be grouped in a *Style* or *Simbology* submenu (possibily together with SLD items). I picked up this ides from Kosmo 1.2. It seems to me more flexible for work,since people don't use so frequently styles items in a project, and make Layer menu shorter. On the other hand, if my proposals to have some project/style exchange files withn Kosmo will have a resault, this will make more simple for user to exchange both software. Peppe Stefan Steiniger [EMAIL PROTECTED] ha scritto: Peppe, could you add your GUI improvement proposals (2 3) to the usability and translation improvement tracker (http://sourceforge.net/tracker/?group_id=118054atid=997723) and the todo-before-shipping list on the wiki? thanx, stefan - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Inviato da Yahoo! Mail. Tanti modi per restare in contatto con chi vuoi.- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] save dataset as / save selected datasets - dialog
hi all! here is just a little proposal: if you add a new layer and want to save it (right-mouse-menu on layer - save selected datasets), it would be nice if there would be opened a save-dialog (only for new unsaved layers) to store the layer. i know, you should save it first with the save dataset as-menu, but it would be more user-friendly, like the save-dialog in the windows notepad (automatically save as-dialog). greetings, carl- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] save dataset as / save selected datasets - dialog
i've totally forgotten my question :-) is it possible to save the layer with a simple function from a plugin? ( layer.saveall() or something like that?) if you are editing the schema and attributes of a layer, the plugin should save the changes, not save by clicking mouse-menu... carl - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] make own extension / plugin dependencies
ok thanks, i think the blackboard is what i need! carl - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] testing famfam icons for oj toolbar
It looks like the famfam icons are a little smaller. are they available as SVG? If they are, they could be enlarged slightly. I personally don't have a problem mixing the famfam icons with existing icons when a famfam replacement doesn't exist. The Sunburned Surveyor On Mon, Mar 24, 2008 at 7:05 PM, Stefan Steiniger [EMAIL PROTECTED] wrote: Hei, I tried to replace our current toolbar icons with famfam icons. my observations: . famfam icons seem to be a bit too small sometimes . I could not find for all icons an equivalent (e.g. hand and the ruler) I am not sure if we are able to create our own by mixing several? maybe we can consider graphical improvements in a future version (1.3x) any comments? stefan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] save dataset as / save selected datasets - dialog
Carl, You wrote: if you add a new layer and want to save it (right-mouse-menu on layer - save selected datasets), it would be nice if there would be opened a save-dialog (only for new unsaved layers) to store the layer. i know, you should save it first with the save dataset as-menu, but it would be more user-friendly, like the save-dialog in the windows notepad (automatically save as-dialog). I like it! Have you ever used our FeatureTracker on SourceForge? If you submit your ideas there, as well as on the mailing list, we won't loose them. You wrote: is it possible to save the layer with a simple function from a plugin? ( layer.saveall() or something like that?) if you are editing the schema and attributes of a layer, the plugin should save the changes, not save by clicking mouse-menu... I'm not sure about this. You must remember that a Layer is really just a thin wrapper around a source of Feature objects. Ususally this is an ESRI Shapefile or some other type of file. So when you save changes to the schema or contents of a Layer you are really trying to modify the underlying file. An exception to this is they styling of the layer. The information to style a layer is stored in the project file. Maybe one of the other programmers can confirm this for me. I haven't dealt a lot with the styling of layers. I think Paul has done a lot of work in this area, even making some custom Layer Styles. Having said all of that, it is possible to listen for changes to a layer, and you could set up some sort of automatic save in a plug-in. You'd have to [1] be aware of performance issues. You don't want to save a layer everytime the user moves a node on a LineString and [2] remember that you'd need to handle the different file formats you want to support. Remember: Layers inderectly wrap a file that can be used to produce Feature objects! The Sunburned Surveyor On Wed, Mar 26, 2008 at 5:21 AM, Carl Grönniger (entera) [EMAIL PROTECTED] wrote: i've totally forgotten my question :-) is it possible to save the layer with a simple function from a plugin? ( layer.saveall() or something like that?) if you are editing the schema and attributes of a layer, the plugin should save the changes, not save by clicking mouse-menu... carl - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] make own extension / plugin dependencies
Carl, I have designed modifications to OpenJUMP's core that will allow what you propose. However, they have not been integrated into the nightly build or thoroughly tested. You can read more here: http://openjump.blogspot.com/2007/02/supporting-plug-in-dependency-in.html http://openjump.blogspot.com/2007/02/supporting-plug-in-dependencies-in.html If this is something you are intersted in trying out I can produce a modified nightly build that supports plug-in dependency using my system. Then you can try it out. If you like it, and the other programmers have no objections, we can talk about integrating it into the regular nightly build. (The system would not require changes to normal plug-in development. I figured I should say that before someone tried to burn me at the stake.) :] It would take me a week or two to revisit my code, complete testing, and produce the build. The Sunburned Surveyor On Wed, Mar 26, 2008 at 5:23 AM, Carl Grönniger (entera) [EMAIL PROTECTED] wrote: ok thanks, i think the blackboard is what i need! carl - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] [ jump-pilot-Usability and Translation Improvements for OpenJUMP UI-1925858 ] Remove Draw Polygon and Draw Tools from Editing Toolbox
Usability and Translation Improvements for OpenJUMP UI item #1925858, was opened at 2008-03-26 00:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=997723aid=1925858group_id=118054 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Remove Draw Polygon and Draw Tools from Editing Toolbox Initial Comment: In the Editing toool box the Draw contrained polygon and draw constrained linestring seems to do basically the same thing od original Draw polygon and Draw linestring. The usage of keyboard keys help to work on Constrained/Unconstrained mode. The only difference is that original draw polygon has an option to draw holes which draw const. pol. doesn't have. But now, thanks to Erwan's cut cookie polygon, it is not necessary to have the double of the same drawing tools on the toolbox. I propone to eliminate original draw polygon and draw linestring to make the toolbox more flexible. Peppe -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=997723aid=1925858group_id=118054 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] [ jump-pilot-Usability and Translation Improvements for OpenJUMP UI-1925859 ] Add the Union/Cut tools from Tools menu to Editing Toolbox
Usability and Translation Improvements for OpenJUMP UI item #1925859, was opened at 2008-03-26 00:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=997723aid=1925859group_id=118054 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Add the Union/Cut tools from Tools menu to Editing Toolbox Initial Comment: The tools Union-lines, Union 2 polygons, and Larry's cut polygons could have an icon and stay on the Editing toolbox instead on the Tools menu. Peppe -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=997723aid=1925859group_id=118054 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] [ jump-pilot-Usability and Translation Improvements for OpenJUMP UI-1925872 ] Layer menu: group in submenu all Style items
Usability and Translation Improvements for OpenJUMP UI item #1925872, was opened at 2008-03-26 00:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=997723aid=1925872group_id=118054 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Layer menu: group in submenu all Style items Initial Comment: We can group, in Layer menu, similar items in submenu, eg. Change style, Copy style and paste style coulg be grouped in a *Style* or *Simbology* submenu (possibily together with SLD items) Peppe -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=997723aid=1925872group_id=118054 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] save dataset as / save selected datasets - dialog
Hei Carl, I think it is possible, but i am also not sure. If you start with parsing what happens in the save selected datasets function you may find a way. The layer would probably be the currently selected one. You find the corresponding plugin when you use one of the language properties files and look for the name of the function. I.e. search for the string Save Selected Datasets in the file jump_en.properties to obtain the path of the corresponding plugin class. Stefan Carl Grönniger (entera) wrote: i've totally forgotten my question :-) is it possible to save the layer with a simple function from a plugin? ( layer.saveall() or something like that?) if you are editing the schema and attributes of a layer, the plugin should save the changes, not save by clicking mouse-menu... carl - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] Language files
I am working around the Italian Language file to fix the latest modification. I am also giving a review to the main (English) Jump.properties files. 1) There are some items which lack of interntionalization (?): ZoomRealtime and Paste items to point 2) I wander if it is possible to modify the description of some items: a) Transform layer style into SLD to Export symbology to SLD file b) Import SLD to Import symbology from SLD file I think in the nect days I will go on working on Italian files and check other Internat/modify on main language file. If you agree with the proposal 2) I will try to modify also Spanish, French and Portuguese files. For point 1) I probabily need a complete Jump.properties Peppe - Scopri il Blog di Yahoo! Mail: trucchi, novità, consigli... e la tua opinione!- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Language files
Hei Peppe, Giuseppe Aruta wrote: I am working around the Italian Language file to fix the latest modification. I am also giving a review to the main (English) Jump.properties files. 1) There are some items which lack of interntionalization (?): ZoomRealtime and Paste items to point yep.. I saw this as well (there may be some more things open: e.g. some checks are left) 2) I wander if it is possible to modify the description of some items: a) Transform layer style into SLD to Export symbology to SLD file b) Import SLD to Import symbology from SLD file no problem. but be aware that you are not changing the key, only the translations. I actually I found the prbeditor quite handsome for the editing of the entries. You only need to load all files together. Then it shows you on the left the key entry and on the right all translations (I can also send a screen shot). stefan I think in the nect days I will go on working on Italian files and check other Internat/modify on main language file. If you agree with the proposal 2) I will try to modify also Spanish, French and Portuguese files. For point 1) I probabily need a complete Jump.properties Peppe Scopri il Blog di Yahoo! Mail http://us.rd.yahoo.com/mail/it/taglines/yahoo/ymail/SIG=11djrg460/**http%3A%2F%2Fwww.ymailblogit.com%2Fblog%2F: trucchi, novità, consigli... e la tua opinione! - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Kosmo and OpenJUMP common area of interests
Hi to all. I'll shed a little bit light on the issues from a developer point of view (both proposals from Giuseppe and another one that Sunburned Surveyor mentioned): 1) Kosmo plug-in model I'll start with a little bit of history to clarify some ideas: Kosmo started on August 2005. Our starting seed was the JUMP 1.0 fork implemented by the Agiles group (the two starting developers of Kosmo were part of the founders of this group). This fork implemented an on-demmand framework to the existing JUMP datasource framework. Why don't we use the 1.1.2 JUMP version that was already present at that date? When we implemented the on-demmand framework on the last version, the results that we obtained were worse that those obtained with the 1.0 fork. So we decided to start with it and added to this version some of the improvements that were made to JUMP from the 1.0 to the 1.1.2 version. As we were advancing in the development of Kosmo, we have added some of the improvements made to JUMP and also to OpenJUMP. The plugin model that Kosmo uses is basically the same: we have added some methods to the interfaces and the abstract classes, but they haven't been changed heavily. There is no plugín dependency system implemented. The extension model have been also improved, but is almost the same too. 2) Save as - project file format I think that a common project file format won't be a good choice: currently each application uses its own project saving framework and it'll be difficult for each one to change it to a common one. I think that a better choice would be to implement a import/export OpenJUMP project option in Kosmo and an import/export Kosmo project option in OpenJUMP. We share some common objects (Task, Category, Layer, FeatureCollections, DataSourceQuery, JUMP Styles, ...) that can be recovered from the project XML file and loaded into each one. 3) SLD Import/Export Kosmo only supports SLD export so far (the import plugin is planned but it's not implemented yet). As Giuseppe says, this format can be used to export/import the layer simbology between the two projects, as SLD is a standard and it's not binded to a determinate application. Kosmo also allows to save its own simbology format because we use some improvements that are not present in the SLD standard. But most of the Kosmo simbology can be exported to a SLD file without problem. Each application could accept the parts of the standard supported, and the rest of the file could be ignored. I think the SLD format it's a good choice. Regards, PD: We've tested the Kosmo SLD export against UDIG 1.1 rc14 and all of the tests have succeded. I've also test against the last OpenJump nightly build with some sld files generated by Kosmo and the OJ SLD import plugin has a problem when reading the color values: it seems to read the color value string with a lot of spaces before and after it, and the Color.decode() function fails (this could be corrected by calling to the method colorString.trim()). Giuseppe Aruta escribió: Hi Antonio, let me resume the two i(my) proposal that could be object of this discussion:. Just in order that developers can have an idea (from user point of view). 1) a save as to project file format shared by two software. This format (Jump, Kosmo or other) would not be alterate by saving option. eg. If I create a project in Kosmo with hyperlink or advanced style, when I open this project in OJ (which hasn't hyperlink or advanced style), modify something and save again to the project file, this doesn't alterate Kosmo's functionalities (hyperlink etc.) 2) Possibility that Kosmo and OpenJUMP would save the layer style to the same file type. Actually Kosmo saves to an its own style files (SLS) format and to SLD for web proposal. OpenJUMP doesn't have a save style file but newer Nightly build allows to export/import to SLD. The proposal is omologate the two SLD projects to let talk each other (I did a test and OJ doesn't import Kosmo SLD files) not only for web but also to exchange basic layer styles parametres (Colours of line, vertices and polygons, line width - possibily line type and simple poligon fill) I invite the other OpenJUMP developers to say their idea about. Best regards Peppe */listas [EMAIL PROTECTED]/* ha scritto: Hi Landon, Peppe and everybody. You are right Peppe, we were in East Holidays and I too needed to talk with our main developer team people (really I am not a developer and I am not able to speak about code, so I need them) :-) . I hope this afternoon some information to continue speaking. Best regards Antonio Giuseppe Aruta escribió: Hi London, I think that the break of comunication in these days regarding Kosmo-OpenJUMP common project was due to East holidays. And also because Antonio Muñoz probabily needs to talk with other Saig team
[JPP-Devel] Updates to OpenJump Printer plugin
To User and Developers I have just posted a new version of the OpenJump Printer plugin. It contains a number of enhancements: * All furniture items can now have their size scaled for printing. * Each OpenJump project can have several user-defined printer configurations (i.e different paper sizes and furniture items) that can be created and retrieved as required. Usual site: http://www.cadplan.com.au Please report any problems thanks Geoff -- Dr Geoffrey G Roy Cadplan 129 Gloster Street, Subiaco WA 6008 Tel: (08) 9381 4870 Fax: (08) 9382 4459 Email: [EMAIL PROTECTED] http://www.cadplan.com.au - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
