Re: [JPP-Devel] SEXTANTE forks ?
Hi Ben, (i) sounds all good to me - I am glad that you don't want to do deeper changes any time soon. (ii) well, I should have thought about something like that with the language folders.. thing is, I am having a swiss mac ;) Anyway my system language is german. (iii) Thanks for the access. I will try and see if I can co-sync the SVN's cheers from Santiago stefan Message: 1 Date: Tue, 28 May 2013 12:36:20 +0200 From: Benjamin Ducke bendu...@fastmail.fm Subject: Re: [Gvsigce-devs] SEXTANTE forks ? To: gvsigce-d...@lists.sourceforge.net Message-ID: 51a488a4.6090...@fastmail.fm Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Stefan On 05/27/2013 07:13 PM, Stefan Steiniger wrote: Hi Benjamin, sorry for this very late response. I subscribed to the digest mode.. Anyway - I think having Java Sextante at CE SVN, should be fine. We, OpenJUMP, have the bindings on our SF SVN. I think, important would be, if you guys would ping us, in case the models are changed (so, major classes like the Vector Raster layer Interfaces) and stuff that would have an effect on loading/displaying gui elements. Sure, if there are any changes that could break the bindings, I will make a dedicated post to this list. But I don't anticipate anything like that in the near future. For now, most of my work will concentrate on enhancing support for SAGA and R. Actually the only problem (with 1.0) we have so far is, we do not know where to put the documentation htmls so that they get loaded. The helps doesn't seem to be working in neither place even if we define it on startup - so I guess it is somewhere else loaded from (Well some stuff is shown, but I don't think it is all: basically only the command line stuff but no real explanation, what is what and no images) The HTML documentation is produced from LaTeX sources. This process needs to be optimized and most of the documentation must be rewritten to reflect the recent changes. I will do that once I have finished all work for the SAGA and R interfaces. When you install the docs, the main documentation (HTML and PNG files) should go into sextante-dir/docs/en/general. In the past, there used to be problems with the en pages not being found on a system that uses e.g. a de locale. In those cases, I worked around the problem by just copying the en folder as a new de folder. btw. you can find me as mentaer on SF. But for browsing the svn with Eclipse it shouldn't be necessary. I have given you developer level access to our SVN at https://svn.code.sf.net/p/gvsigce/code/trunk That way, you can commit any changes directly and we don't have to use pesky patch files. Cheers, Ben Ah, maybe another note: I actually think that our model/binding is not much different from Kosmo's with respect to layers. But I am not really sure about it. cheers, stefan -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] SEXTANTE forks ?
Hi Benjamin, sorry for this very late response. I subscribed to the digest mode.. Anyway - I think having Java Sextante at CE SVN, should be fine. We, OpenJUMP, have the bindings on our SF SVN. I think, important would be, if you guys would ping us, in case the models are changed (so, major classes like the Vector Raster layer Interfaces) and stuff that would have an effect on loading/displaying gui elements. Actually the only problem (with 1.0) we have so far is, we do not know where to put the documentation htmls so that they get loaded. The helps doesn't seem to be working in neither place even if we define it on startup - so I guess it is somewhere else loaded from (Well some stuff is shown, but I don't think it is all: basically only the command line stuff but no real explanation, what is what and no images) btw. you can find me as mentaer on SF. But for browsing the svn with Eclipse it shouldn't be necessary. Ah, maybe another note: I actually think that our model/binding is not much different from Kosmo's with respect to layers. But I am not really sure about it. cheers, stefan -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] SEXTANTE forks ?
Hallo Stefan, I'm CCing your email to the gvSIG CE dev list, so we can coordinate this better. Victor Olaya, Benjamin Ducke and Fran Puga will read this email also here. Fran Puga (Cartolab-gvSIG developer) has sent a couple of patches last week. This email goes also to these developers in CC. Could you please sign the gvSIG CE dev list (http://gvsigce.sourceforge.net/joomla/index.php/community/mailing-lists) and follow the discussion here? The repository of the java version of SEXTANTE for gvSIG CE is now here: http://gvsigce.sourceforge.net/joomla/index.php/sextante. The latest release for this version (SEXTANTE-gvSIG CE) has been published here: http://gvsigce.blogspot.de/2013/03/sextante-news-and-inofficial-preview.html We are glad to read about your interest for SEXTANTE in OpenJUMP and would like to help you to find a good solution for your project. Let us discuss this here together. See you (maybe in Rapperswil?) Jose -- José Canalejo www.csgis.de De: Stefan Steiniger sst...@geo.uzh.ch Para: José Antonio Canalejo Alonso jacanal...@yahoo.es CC: OpenJump develop and use jump-pilot-devel@lists.sourceforge.net Enviado: Martes 14 de Mayo de 2013 2:42 Asunto: Re: SEXTANTE forks ? Hola Jose (CC jpp-dev), I am reading this email below late and have now a question. Where should I/we watch out for Sextante changes (e.g. an 1.1 release?). I.e. what/where is the repository now and where will releases be published. I ask, because I am with the OpenJUMP team, and as you may know, Sextante is part of OpenJUMPs PLUS edition. saludos, stefan Am 24.03.13 04:33, schrieb José Antonio Canalejo Alonso: No, it ins't a fork. Just to clarify, the original java source code of SEXTANTE has been transfered (in coordination with the original creator of SEXTANTE) to the gvSIG Community Edition (CE) repository NOT to the official gvSIG repository [1]. gvSIG CE is a fork of gvSIG made in 2011. In SEXTANTE there are now two versions: one in python managed by the QGIS community, one in java managed by the gvSIG CE project. Both versions are well coordinated with the original SEXTANTE project team. QGIS and gvSIG CE have been the projects with more activity behind SEXTANTE since its creator announced that the development of SEXTANTE could not continue as a full-time work. Best regards Jose [1] http://gvsig-ce-users.1049287.n5.nabble.com/Gvsigce-users-SEXTANTE-news-and-inofficial-preview-td5706342.html -- José Canalejo www.csgis.de On 03/23/2013 10:15 AM, Brian Hamlin wrote: Hi All - I am reading a blog post today on planet.osgeo.org about SEXTANTE moving to python, while the original code will be part of gvSIG now.. plus some new improvements.. A classical fork it appears.. I imagine the Live will host gvSIG and so continue to benefit from that branch.. But it raises the question, what to do with the new python SEXTANTE ? no rush, but interesting development -- Brian M Hamlin The new python Sextante is in the QGIS plugin, which I think we're already shipping. It's not a classic fork in my understanding because one of the key authors is the same for both variants. Although it's actually possible that the python version may become the primary one and wrapped by java in gvSIG rather than being maintained in java. So, I don't think there's anything else to do about it for us. Thanks, Alex ___ Live-demo mailing list live-d...@lists.osgeo.org mailto:live-d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://live.osgeo.org/ http://wiki.osgeo.org/wiki/Live_GIS_Disc ___ Live-demo mailing list live-d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://wiki.osgeo.org/wiki/Live_GIS_Disc -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] SEXTANTE forks ?
forgot the cc ;) Am 14.05.13 10:05, schrieb Stefan Steiniger: Hi Jose, thanks, I just subscribed to the gvSIG CE dev list. Unfortunately I am not able to make it to Rapperswill. I am currently living in Chile.. so trips to Europe are far from being cheap and take a long time too... :( saludos de Santiago stefan Am 14.05.13 02:02, schrieb José Antonio Canalejo Alonso: Hallo Stefan, I'm CCing your email to the gvSIG CE dev list, so we can coordinate this better. Victor Olaya, Benjamin Ducke and Fran Puga will read this email also here. Fran Puga (Cartolab-gvSIG developer) has sent a couple of patches last week. This email goes also to these developers in CC. Could you please sign the gvSIG CE dev list (http://gvsigce.sourceforge.net/joomla/index.php/community/mailing-lists) and follow the discussion here? The repository of the java version of SEXTANTE for gvSIG CE is now here: http://gvsigce.sourceforge.net/joomla/index.php/sextante. The latest release for this version (SEXTANTE-gvSIG CE) has been published here: http://gvsigce.blogspot.de/2013/03/sextante-news-and-inofficial-preview.html We are glad to read about your interest for SEXTANTE in OpenJUMP and would like to help you to find a good solution for your project. Let us discuss this here together. See you (maybe in Rapperswil?) Jose -- José Canalejo www.csgis.de *De:* Stefan Steiniger sst...@geo.uzh.ch *Para:* José Antonio Canalejo Alonso jacanal...@yahoo.es *CC:* OpenJump develop and use jump-pilot-devel@lists.sourceforge.net *Enviado:* Martes 14 de Mayo de 2013 2:42 *Asunto:* Re: SEXTANTE forks ? Hola Jose (CC jpp-dev), I am reading this email below late and have now a question. Where should I/we watch out for Sextante changes (e.g. an 1.1 release?). I.e. what/where is the repository now and where will releases be published. I ask, because I am with the OpenJUMP team, and as you may know, Sextante is part of OpenJUMPs PLUS edition. saludos, stefan Am 24.03.13 04:33, schrieb José Antonio Canalejo Alonso: No, it ins't a fork. Just to clarify, the original java source code of SEXTANTE has been transfered (in coordination with the original creator of SEXTANTE) to the gvSIG Community Edition (CE) repository NOT to the official gvSIG repository [1]. gvSIG CE is a fork of gvSIG made in 2011. In SEXTANTE there are now two versions: one in python managed by the QGIS community, one in java managed by the gvSIG CE project. Both versions are well coordinated with the original SEXTANTE project team. QGIS and gvSIG CE have been the projects with more activity behind SEXTANTE since its creator announced that the development of SEXTANTE could not continue as a full-time work. Best regards Jose [1] http://gvsig-ce-users.1049287.n5.nabble.com/Gvsigce-users-SEXTANTE-news-and-inofficial-preview-td5706342.html -- José Canalejo www.csgis.de On 03/23/2013 10:15 AM, Brian Hamlin wrote: Hi All - I am reading a blog post today on planet.osgeo.org about SEXTANTE moving to python, while the original code will be part of gvSIG now.. plus some new improvements.. A classical fork it appears.. I imagine the Live will host gvSIG and so continue to benefit from that branch.. But it raises the question, what to do with the new python SEXTANTE ? no rush, but interesting development -- Brian M Hamlin The new python Sextante is in the QGIS plugin, which I think we're already shipping. It's not a classic fork in my understanding because one of the key authors is the same for both variants. Although it's actually possible that the python version may become the primary one and wrapped by java in gvSIG rather than being maintained in java. So, I don't think there's anything else to do about it for us. Thanks, Alex ___ Live-demo mailing list live-d...@lists.osgeo.org mailto:live-d...@lists.osgeo.org mailto:live-d...@lists.osgeo.org mailto:live-d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://live.osgeo.org/http://live.osgeo.org/ http://wiki.osgeo.org/wiki/Live_GIS_Disc ___ Live-demo mailing list live-d...@lists.osgeo.org
Re: [JPP-Devel] SEXTANTE forks ?
Hola Jose (CC jpp-dev), I am reading this email below late and have now a question. Where should I/we watch out for Sextante changes (e.g. an 1.1 release?). I.e. what/where is the repository now and where will releases be published. I ask, because I am with the OpenJUMP team, and as you may know, Sextante is part of OpenJUMPs PLUS edition. saludos, stefan Am 24.03.13 04:33, schrieb José Antonio Canalejo Alonso: No, it ins't a fork. Just to clarify, the original java source code of SEXTANTE has been transfered (in coordination with the original creator of SEXTANTE) to the gvSIG Community Edition (CE) repository NOT to the official gvSIG repository [1]. gvSIG CE is a fork of gvSIG made in 2011. In SEXTANTE there are now two versions: one in python managed by the QGIS community, one in java managed by the gvSIG CE project. Both versions are well coordinated with the original SEXTANTE project team. QGIS and gvSIG CE have been the projects with more activity behind SEXTANTE since its creator announced that the development of SEXTANTE could not continue as a full-time work. Best regards Jose [1] http://gvsig-ce-users.1049287.n5.nabble.com/Gvsigce-users-SEXTANTE-news-and-inofficial-preview-td5706342.html -- José Canalejo www.csgis.de On 03/23/2013 10:15 AM, Brian Hamlin wrote: Hi All - I am reading a blog post today on planet.osgeo.org about SEXTANTE moving to python, while the original code will be part of gvSIG now.. plus some new improvements.. A classical fork it appears.. I imagine the Live will host gvSIG and so continue to benefit from that branch.. But it raises the question, what to do with the new python SEXTANTE ? no rush, but interesting development -- Brian M Hamlin The new python Sextante is in the QGIS plugin, which I think we're already shipping. It's not a classic fork in my understanding because one of the key authors is the same for both variants. Although it's actually possible that the python version may become the primary one and wrapped by java in gvSIG rather than being maintained in java. So, I don't think there's anything else to do about it for us. Thanks, Alex ___ Live-demo mailing list live-d...@lists.osgeo.org mailto:live-d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://live.osgeo.org/ http://wiki.osgeo.org/wiki/Live_GIS_Disc ___ Live-demo mailing list live-d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://wiki.osgeo.org/wiki/Live_GIS_Disc -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
