<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> and we're trying to determine how we can get some serious editing<br>
> capabilities into our web mapping apps. As you can see from the<br>
> wireframes above, we've explored use cases ranging from attribute<br>
> editing to vector editing to full on versioning<br>
<br>
</div>I guess that brings about the point raised by Matt (we're talking<br>
client-side too!), since in this case versioning would not be a client<br>
side technology-agnostic (you'd need GeoServer for it) functionality.</blockquote><div><br></div><div>To clarify, that GeoEditor project is part of our OpenGeo roadmap, which is why it has GeoServer dependencies. Anything that is too server-specific for the GeoExt community (like versioning widgets, until there is a versioning transaction standard) would be maintained as part of a separate repository of code that extends GeoExt. </div>
<div> </div></div>-- <br>Sebastian Benthall<br>OpenGeo - <a href="http://opengeo.org">http://opengeo.org</a><br><br>