Message-ID: <944866243.42238.1371705553670.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_42237_1719244204.1371705553670" ------=_Part_42237_1719244204.1371705553670 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Currently GeoTools and uDig use different frameworks for definin= g maps and map layers, and they have different concepts for rendering and a= ccess to the data. In general, GeoTools is more straightforward and intuiti= ve, whereas uDig introduces some interesting ideas that make the framework = more abstract, but allow faster rendering or f.e. better management of remo= te data sources.
For the GeoWidgets project (which tries to create reusable GIS UI widget= s) to be successful, it is required:
This document shall contain ideas collected from GeoTools/GeoWidgets/Udi= g and other developers, on how such map/layer/rendering/data access API co= uld look.
In order to structure this document following sub pages currently exist:=
Describes why this effort is done and which general ideas have emerged.<= /p>
Describes what is specific to the interfaces used in the mentioned libra= ries and applications and tries to find strengths and weaknesses.
Ideas and issues for the technical realization. Everybody is invided to = share his/her thoughts on this.
UML diagrams, code snippets and images that show how things could work.<= /p> ------=_Part_42237_1719244204.1371705553670--