Sergio, You wrote: "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."
This is good news. I'm not sure how much the guts of Kosmo has changed in comparision to OpenJUMP, but this means that at least the plug-in framework may be close to being compatible. I'll have to figure out how to download the Kosmo source code so I can look at the methods that were added. What are the chances that a plug-in written for OpenJUMP could run in Kosmo without major modifications? Are the basic data structures within the cores of both programs essentially the same? You wrote: "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." We should remember that migration to a common project file format could be an long-term goal, and not something that would need to be done immediately. We could determine what a common project file format might look like, and then work towards using that format over the next couple of years as we make other changes. You wrote: "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." This is an excellent idea. I should add it as one of my future projects, at least until another programmer decides to tackle it. :] The Sunburned Surveyor On Wed, Mar 26, 2008 at 12:42 PM, SAIG - Listas <[EMAIL PROTECTED]> wrote: > 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 > > > before taking a decision. Let us wait a couple of days. > > > BTW Kosmo put on their web site some manuals about Kopsmo and > > how to > > > develop extensions (Kosmo_manual_desarrollador.pdf and > > > Kosmo_manual_extensiones.pdf). > > > > > > Peppe > > > > > > */Sunburned Surveyor /* ha scritto: > > > > > > Peppe, > > > > > > Can you get a hold of the Kosmo team and see if there is any > > interest > > > in working on a common project file format? > > > > > > The Sunburned Surveyor > > > > > > On Thu, Mar 20, 2008 at 1:37 AM, Andreas Schmitz wrote: > > > > Giuseppe Aruta wrote: > > > > > > > > Hi, > > > > > > > > > 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 SLDImporter.java) are > > > > > for import/export SLD). > > > > > > > > yes, the SLD import/export is more or less finished. > > > Unfortunately, I'll be on > > > > vacation the next month, so I'll probably only get to it after > > > that. What's > > > > missing is a dialog to offer the user which style he wants to > > > import (in case of > > > > multiple ones and ones with filters) and some general stability. > > > > > > > > If someone wants to try it out with Kosmo-generated SLD (of > > > course also with > > > > completely unrelated SLD) I'd like to hear about it. I'm also > > > open for > > > > suggestions on how to handle more complicated situations. > > > > > > > > Best regards, Andreas > > > > -- > > > > l a t / l o n GmbH > > > > Aennchenstrasse 19 53177 Bonn, Germany > > > > phone ++49 +228 18496-11 fax ++49 +228 1849629 > > > > http://www.lat-lon.de http://www.deegree.org > > > > > > > > ------------------------------------------------------- > > > > On June 17 is deegree day - Am 17. Juni ist deegree day > > > > http://deegree.org/deegreeday > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > Version: GnuPG v1.4.6 (GNU/Linux) > > > > > > > > iD4DBQFH4iJc737OVr+Ru7oRAnH6AJUdlDhcTqTXrHM7JxAeSHNrdpRxAKDXU1BJ > > > > WTP/3Ha2VfpBdvRk7WL5ng== > > > > =iFgP > > > > -----END PGP SIGNATURE----- > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Microsoft > > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > > _______________________________________________ > > > > Jump-pilot-devel mailing list > > > > Jump-pilot-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > 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. > > > > > ------------------------------------------------------------------------ > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Jump-pilot-devel mailing list > > > Jump-pilot-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > Inviato da Yahoo! Mail > > <http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=52437/*http://it.docs.yahoo.com/mail/overview/index.html>. > > > > Tanti modi per restare in contatto con chi vuoi. > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > -- > > Sergio Baños Calvo > > Jefe de desarrollos > Sistemas Abiertos de Información Geográfica, S.L. (SAIG S.L.) > Tlfno. móvil: 685005960 > Tlfno. fijo: (+34) 954788876 > > E-mail: [EMAIL PROTECTED] > > > ------------------------------------------------------------------------- > 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
