Hi Pieter, this may not directly answer your question, but you could use the existing JSTS library: https://github.com/bjornharrtell/jsts - this is basically a port of the Java Topology Suite. The advantage would be that you don't need a JS wrapper - you could use JTS on the server and JSTS on the client. And if things you need are missing in JSTS, you could contribute them.
Just my 2¢ - sorry if they are inappropriate. Andreas. On Wed, Jul 13, 2011 at 10:36 AM, Pieter De Graef <[email protected]> wrote: > Hi everyone, > for the Geomajas project, we are looking into separating the Geometry > functionality into an independent project. In other words, I am talking > about a Geometry project for the Web. This code would be written in Java for > GWT and thus be available on Java backends as well as client environments > (we intend to add a JavaScript wrapper around the GWT code). > Now the problem that I'm facing here, is which model to follow.... > On one hand there is the Simple Feature Specification which is clearly an > Object Oriented model with the advantage that it is well known but is also > more difficult to implement the JavaScript wrapper around. > On the other hand we could follow a service based model (more like SFS for > SQL) which is easier to get up and running, easier to create a JavaScript > wrapper for and easier to translate into web services. > As it's difficult for us to chose and as it's a pretty crucial decision for > the future of the Geomajas project, I as wondering how you guys feel about > this. > Kind regards, > Pieter De Graef > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/discuss > > -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers. _______________________________________________ Discuss mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/discuss
