![]() The uDig architecture makes heavy use of the Eclipse IAdaptable approach to problem solving. ![]() We would like to take advantage of this independence and take a role similar to OpenLayers for web mapping, acting as a single "clearing house" framework allowing teams to leverage spatial data using their choice of spatial toolkit, scripting language, and even geometry representation. What does the future of uDig look like beyond 2.0? The uDig Platform has a strong integration story, and is fully capable of integration with other toolkits and rendering chains beyond our core use of GeoTools. ![]() Upgrade to Eclipse 4.x for a new look and feel (given community interest) Submission of all dependencies for IP review Note: This is a milestone target, pre-packaged download will be from as we will not of completed parallel IP process yet. Upgrade to Eclipse 3.8 (to avoid issues on OSX) This is especially important as GeoCoding technologies are developed, as this is a roadblock for those seeking to bridge between their business data and a good mapping solution.īy the end of the uDig 2 Series we want to nail our reuse story for RCP developers, and earnestly collect tools and processes for our Desktop users. We also look forward to collaboration with fellow LocationTech projects as they complete incubation. Making this functionality available for our Desktop users, and our SDK developers, is a great technical direction.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |