Hi Guys,
I got online with Skype and talked with Justin one evening this week, and learned about all the stuff he has not been sending to email!

Here is the ground we covered (GeoTools only):
- a code review of the ResourceCollection, FeatureCollection, FeatureState ideas in geotools 2.2.x (yeah a code review for me). The result was Justin wants FeatureState to be a Feature (so he does not have to cut and paste some code), I would rather it not support the Feature interface (cause it is really a "mixin" providing the attribute, getBounds, getType information for a FeatureCollection. But I did not care enough to complain much. The only problem is that the FeatureState.getType() explicitly must return a FeatureCollectionType when mixed into a FeatureCollection. Since this is API only used by those implementing a FeatureCollection from the inside out I figure they can read the javadocs.

And GeoAPI/GeoTools:
- the GeoAPI TypeFactory and friends, were in a bit of a mess and we cleaned them up. I made Attribute.getType() manditory (allowing for things like a FeatureCollection to be used "naked" - ie without an AttributeDescriptor() describing how it is contained in something else. Justin took a mental vacation and broke my mind with generics on the TypeFactory methods....

I was hoping to review your work on the weekend Justin (ie when I have volunteer time) - but so far I don't see an update. Can you commit please?

Jody



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to