I am fine for the revolution; should however talk with Justin who put a lot of thought into the revolution and has a proposal outlining the marching orders for the feature collection plot.
I would support the revolution in order to get feature collection separate from java.util.Colleciton; if you guys really wanted to soften the blow we could commit to the DefaultFeatureCollection class API as representing an in memory feature collection (and replace the current implementation with ListFeatureCollection internals). Aside: I am not sure about ListFeatureCollection; I suspect a HashSet based implementation may perform better; and offer us greater protection against duplicates. Jody On 05/06/2010, at 7:42 PM, Michael Bedward wrote: > On 5 June 2010 19:25, Andrea Aime wrote: >> >> /me really hates feature collections being writable. Would be +1 making >> them read only right now > > I'm with you comrade. Shall we plot revolution for 2.7 ? If we got > the docs and examples re-jigged on trunk we might get away with it > because 2.7 offers so many nice new features to sweeten the pill for > users. > > Michael ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
