Thanks for the great discussion today guys :-) I just have one comment about duplicating work / functionality. I really like the idea of duplicate renderers - it makes our interfaces so much stronger.
A quick example is the go-1 renderer; without the go-1 renderer in recent years (ie two rendering systems) hacks were added to the streaming renderer to make up for lack of datastore QA. I would hope that having more people using the FeatureSource API we could of caught the gaps in functionality earlier. As it was the streaming renderer had hacked around a lot of QA problems and it was months-years before I found out about them. The XML case is harder (we are talking different API rather than different plug-in implementations). I hope our XML road map can cover thephasing out the old DOM / SAX code :-) I know we can do this with both solutions; I just want to see it done. > What's more painful is to have all this duplication around (gtxml vs > jaxb, streaming renderer vs go renderer, ...) but it seems like the > only way we can collaborate. We need more interfaces so keep > everybody working on its implementations, eventually we may end up > having two parallel set of modules doing similar stuff for most of > the functionalities, but I'm not really seeing any good way out of this. All the best, Jody ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
