Re: [JPP-Devel] [openjump-users] openjump.exe with ini
On 01.09.2010 15:46, Larry Becker wrote: BTW, I have nothing against retiring the bin directory, but it might break the startup scripts. true, I can check and modify the windows and linux scripts, if we agree on retiring '/bin'. And again I want to lobby for a one for all solution.Let me summarize: - we try to be 'cross-platform' - but can't support different distributions for each operating system - user must be able to change the java runtime parameters (e.g. memory settings) - runtime parameters cannot be changed inside the running environment, but have to be given as parameters Only solution I see is a unified launcher (java) run by native launchers for the different os's. I like the simplicity of startup scripts, but am pretty sure that end users are more confused than supported by them (which should i use, how can i configure ...). regards ede -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] wishlist
Stefan mentioned that there isn't a road map for OJ, but is there a place to jot down improvement ideas? Here are a couple on my wishlist: 1) The ability to specify which columns are editable in an layer's attribute table. Right now, the FID and geometry column are hard-coded as being the only columns that are not editable. I would like to see this driven off the layer's FeatureSchema. Perhaps there could be a isAttributeReadOnly(int attributeIndex) method added to the FeatureSchema that could be used in LayerTableModel.isCellEditable(int rowIndex, int columnIndex). Primary key attributes that belong to a DynamicFeatureCollection driven off a database is one example of a non-editable column. 2) The ability to customize the tooltips for previously installed plugins on a layer's right click context menu. For example, I could have a custom implementation of a Layer that is backed by a custom FeatureCollection. If I mark the layer as readonly, the Editable menu item is correctly greyed-out. The tooltip says something like This layer cannot be made editable. The menu item is greyed-out ... obviously it's not editable. I would like to change the tooltip to explain *why* the menu item is greyed-out ... which is particular to my custom FeatureCollection. IE. No Primary Key found on the underlying database table Adhoc queries cannot be made editable SQL Server DataStores cannot currently be made editable 3) A new UpdatablePlugIn interface with methods like getPluginVersion(), getPluginURL(). All implementations of the interface could be listed in the extensions tag in the About window. A user could choose to update a selected plugin where a new plugin jar and all the jar's dependencies would automatically download, available upon application restart. I know, I know. This would require a huge framework and lots of developer time, but it sure would be nice to have. Cheers, -- Kevin -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] my availability - and admin rights
Hei, I was going to add this to my previous email, but better to have this separate. A note with respect to my availability: As I said I will check email in September once in while during my travels - starting tomorrow for 5 days to US, then again on September 13 to Europe. But maybe I even have time for a release if we get the Nightly-Built back running and can translate the languages (well.. it may be October by then). If I am going to travel from Middle of October on is still unclear - but likely. However, Michael and Landon/Sunburned Surveyor have admin rights on SourceForge. Larry is not an Admin on SourceForge but can basically do everything too (I/Michael can make him one if he wishes) - besides some others (such as releases etc.). Michael and Landon also have manager rights for openjump @ google groups (Michael is also owner). On JPP devel: I guess Landon would then need to clean up the JPP-Devel spam box (not sure who else is an admin there besides Landon). if there any questions on this, send them to me but not over the list i.e. directly to me (as they otherwise get filtered into the sub-folders, and I won't check all incoming emails there). cheers from Calgary, stefan -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] wishlist
Hei Kevin, thanks for you thoughts. Sounds all pretty reasonable to me - the only issue is developer time ;) In general we have at SourceForge the Bug Tracker and Feature-Request Tracker. So that would be the place to add your 3 wishes: http://sourceforge.net/projects/jump-pilot/support We actually had also a TODO.txt file in the trunk, but it is not used. thanks again, and its actually nice to know that Refractions-Folks besides Martin is still interested in OJ development :) cheers from Calgary to Victoria stefan Kevin Neufeld wrote: Stefan mentioned that there isn't a road map for OJ, but is there a place to jot down improvement ideas? Here are a couple on my wishlist: 1) The ability to specify which columns are editable in an layer's attribute table. Right now, the FID and geometry column are hard-coded as being the only columns that are not editable. I would like to see this driven off the layer's FeatureSchema. Perhaps there could be a isAttributeReadOnly(int attributeIndex) method added to the FeatureSchema that could be used in LayerTableModel.isCellEditable(int rowIndex, int columnIndex). Primary key attributes that belong to a DynamicFeatureCollection driven off a database is one example of a non-editable column. 2) The ability to customize the tooltips for previously installed plugins on a layer's right click context menu. For example, I could have a custom implementation of a Layer that is backed by a custom FeatureCollection. If I mark the layer as readonly, the Editable menu item is correctly greyed-out. The tooltip says something like This layer cannot be made editable. The menu item is greyed-out ... obviously it's not editable. I would like to change the tooltip to explain *why* the menu item is greyed-out ... which is particular to my custom FeatureCollection. IE. No Primary Key found on the underlying database table Adhoc queries cannot be made editable SQL Server DataStores cannot currently be made editable 3) A new UpdatablePlugIn interface with methods like getPluginVersion(), getPluginURL(). All implementations of the interface could be listed in the extensions tag in the About window. A user could choose to update a selected plugin where a new plugin jar and all the jar's dependencies would automatically download, available upon application restart. I know, I know. This would require a huge framework and lots of developer time, but it sure would be nice to have. Cheers, -- Kevin -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] wishlist
Ah, great, thanx Stefan. I'll add the requests there so others can comment/poke holes/massage/scrap the ideas. Yeah, OJ is by far my preferred desktop GIS client. The fact that OJ is so tightly coupled with JTS (which is the backbone of PostGIS through GEOS) makes it great to work with. Cheers, Kevin On 9/1/2010 11:48 AM, Stefan Steiniger wrote: Hei Kevin, thanks for you thoughts. Sounds all pretty reasonable to me - the only issue is developer time ;) In general we have at SourceForge the Bug Tracker and Feature-Request Tracker. So that would be the place to add your 3 wishes: http://sourceforge.net/projects/jump-pilot/support We actually had also a TODO.txt file in the trunk, but it is not used. thanks again, and its actually nice to know that Refractions-Folks besides Martin is still interested in OJ development :) cheers from Calgary to Victoria stefan Kevin Neufeld wrote: Stefan mentioned that there isn't a road map for OJ, but is there a place to jot down improvement ideas? Here are a couple on my wishlist: 1) The ability to specify which columns are editable in an layer's attribute table. Right now, the FID and geometry column are hard-coded as being the only columns that are not editable. I would like to see this driven off the layer's FeatureSchema. Perhaps there could be a isAttributeReadOnly(int attributeIndex) method added to the FeatureSchema that could be used in LayerTableModel.isCellEditable(int rowIndex, int columnIndex). Primary key attributes that belong to a DynamicFeatureCollection driven off a database is one example of a non-editable column. 2) The ability to customize the tooltips for previously installed plugins on a layer's right click context menu. For example, I could have a custom implementation of a Layer that is backed by a custom FeatureCollection. If I mark the layer as readonly, the Editable menu item is correctly greyed-out. The tooltip says something like This layer cannot be made editable. The menu item is greyed-out ... obviously it's not editable. I would like to change the tooltip to explain *why* the menu item is greyed-out ... which is particular to my custom FeatureCollection. IE. No Primary Key found on the underlying database table Adhoc queries cannot be made editable SQL Server DataStores cannot currently be made editable 3) A new UpdatablePlugIn interface with methods like getPluginVersion(), getPluginURL(). All implementations of the interface could be listed in the extensions tag in the About window. A user could choose to update a selected plugin where a new plugin jar and all the jar's dependencies would automatically download, available upon application restart. I know, I know. This would require a huge framework and lots of developer time, but it sure would be nice to have. Cheers, -- Kevin -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] wishlist
Hi Kevin All your propositions seem reasonnable and valuable for OpenJUMP. As Stefan said, the main problem is development resources. I cannot evaluate precisely the work to do without a deeper look, but it concerns core classes and will need caution and tests. Are you volonteer to develop these features ? Michaël Le 01/09/2010 20:15, Kevin Neufeld a écrit : Stefan mentioned that there isn't a road map for OJ, but is there a place to jot down improvement ideas? Here are a couple on my wishlist: 1) The ability to specify which columns are editable in an layer's attribute table. Right now, the FID and geometry column are hard-coded as being the only columns that are not editable. I would like to see this driven off the layer's FeatureSchema. Perhaps there could be a isAttributeReadOnly(int attributeIndex) method added to the FeatureSchema that could be used in LayerTableModel.isCellEditable(int rowIndex, int columnIndex). Primary key attributes that belong to a DynamicFeatureCollection driven off a database is one example of a non-editable column. 2) The ability to customize the tooltips for previously installed plugins on a layer's right click context menu. For example, I could have a custom implementation of a Layer that is backed by a custom FeatureCollection. If I mark the layer as readonly, the Editable menu item is correctly greyed-out. The tooltip says something like This layer cannot be made editable. The menu item is greyed-out ... obviously it's not editable. I would like to change the tooltip to explain *why* the menu item is greyed-out ... which is particular to my custom FeatureCollection. IE. No Primary Key found on the underlying database table Adhoc queries cannot be made editable SQL Server DataStores cannot currently be made editable 3) A new UpdatablePlugIn interface with methods like getPluginVersion(), getPluginURL(). All implementations of the interface could be listed in the extensions tag in the About window. A user could choose to update a selected plugin where a new plugin jar and all the jar's dependencies would automatically download, available upon application restart. I know, I know. This would require a huge framework and lots of developer time, but it sure would be nice to have. Cheers, -- Kevin -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] my availability - and admin rights
Thanks for the update Stefan. I'll try to keep everyone happy while you are running around the world. :] The Sunburned Surveyor On Wed, Sep 1, 2010 at 11:37 AM, Stefan Steiniger sst...@geo.uzh.ch wrote: Hei, I was going to add this to my previous email, but better to have this separate. A note with respect to my availability: As I said I will check email in September once in while during my travels - starting tomorrow for 5 days to US, then again on September 13 to Europe. But maybe I even have time for a release if we get the Nightly-Built back running and can translate the languages (well.. it may be October by then). If I am going to travel from Middle of October on is still unclear - but likely. However, Michael and Landon/Sunburned Surveyor have admin rights on SourceForge. Larry is not an Admin on SourceForge but can basically do everything too (I/Michael can make him one if he wishes) - besides some others (such as releases etc.). Michael and Landon also have manager rights for openjump @ google groups (Michael is also owner). On JPP devel: I guess Landon would then need to clean up the JPP-Devel spam box (not sure who else is an admin there besides Landon). if there any questions on this, send them to me but not over the list i.e. directly to me (as they otherwise get filtered into the sub-folders, and I won't check all incoming emails there). cheers from Calgary, stefan -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
