[OSM-talk] Re: osmeditor2 to Java, and a common Java OSM client library

Nick Hill nick at nickhill.co.uk
Thu May 25 15:01:32 BST 2006


This thread of discussion is becoming more technical and specific so 
have also posted to dev. Please post any replies to this to dev.

Nick Whitelegg wrote:
...


> I'm not very keen on the "one 
> editor to rule them all" idea, as I think each editor fulfills a slightly 
> different purpose, and I would very much like to continue to develop 
> osmeditor2 as "my idea" as to what I would like out of an OSM editor. 

A substantial common codebase on which to build customised java OSM 
applications would provide the best evolutionary outcome whilst 
providing single point API migration.

I like the idea of an applet which can determine the available resources 
limits then provide the user with an option of applet or josm level 
functionality.

> So what I will probably do (unless I get negative feedback from people, or 
> do not have the time) is put osmeditor2 into feature freeze until July 
> (when I will have much more free time than I do now), and then convert it 
> to GCJ-compatible Java. It might also be good if everyone working on 
> editors could collaborate on a common library to represent the data model 
> (the Nodes, Segments, Ways etc) and server-communication.

Imi did mention a common set of data representation libraries a couple 
of months back. If applet, josm and osmeditor-java all used and 
developed these. Perhaps Jeeps could become a java class as a common 
applet resource

I think that is a great idea. How do we practically do this?









More information about the talk mailing list