Hi Jody,<div><br></div><div>that's the GeoApi specification no?</div><div><br></div><div>At first we would be using it on the GWT client we where hoping to also include curves, as those can be directly drawn in SVG/VML. At a later stage we could switch the backend to make use of it as well.</div>
<div><br></div><div>Jody, you have been looking into creating you own Geometry library for some time now I understand. How would you approach this? I was hoping to start with something simple, that can grow at it's own pace. Important for me is that I can use the same objects on both client and server (meaning Java with some GWT restrictions).</div>
<div><br></div><div>I am also afraid to be re-inventing the wheel, but using 2 different libraries on client and server would be a shame when using GWT...</div><div><br><br><div class="gmail_quote">2011/7/13 Jody Garnett <span dir="ltr"><<a href="mailto:jody.garnett@gmail.com">jody.garnett@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div><span><div><div><div>
<div>
<span>There is a third model; the ISO19107 model that deals with a few more things; it is however object oriented in nature....<br>
</span>
<span><br>-- <br><font color="#888888">Jody Garnett<br><br></font></span><div><div></div><div class="h5">
<p style="color:#a0a0a0">On Wednesday, 13 July 2011 at 6:36 PM, Pieter De Graef wrote:</p></div></div><blockquote type="cite"><div>
<span><div><div><div></div><div class="h5"><div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">Hi everyone,<div><br></div><div>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).</div>
<div><br></div><div>Now the problem that I'm facing here, is which model to follow....</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>Kind regards,</div>
<div><br></div><div>Pieter De Graef</div></span>
</div></div></div><div class="im"><div>_______________________________________________<br>Discuss mailing list<br><a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</div></div></div></span>
</div></blockquote><div>
<br>
</div>
</div>
</div></div></div></span></div></div><br>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
<br></blockquote></div><br></div>