Hi list and PMCs! Moovida and my self have been discussion what next generation resource persistence in uDig might look like. We have started to write a RFC proposal, which has the potential to add
- Real project support, allowing users to move projects around - Better concurrency control, using a main-stream transaction framework, redusing the complexity of uDig model maintenance - Real-time and fault-tolerant sharing of uDig resources (aka social editing) - And some other cool stuff The changes we are talking about are substantial. I have therefore already started on some "proof of concept" work, migrating current uDig models to CDO to see if this can be done without to much work. After 10 hours of work, all models are migrated to CDO. This involved fixing dependencies on interface now removed from Geotools, and changing dependencies from EObject to CDOObject (extends EObject) and InternalEObject to InternalCDOObject. I have not completed the migration yet, but I am able to add new projects and maps to views using standard methods. When I have concrete results, I will push a branch to my udig-platform clone<https://github.com/kengu/udig-platform>at github. Naturally, we would love some (a lot of) feedback on the RFC, which is located here: http://udig.refractions.net/confluence/display/UDIG/Next+generation+resource+persistence+in+uDig It is a big change (and probably a lot of work), a broad discussion about pros and cons is therefore necessary before I can commit to this work. Cheers, Kenneth Gulbrandsøy
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
