Gabriel Roldán wrote:
>> FeatureCollection and events:
>> ----------------------------
>> oog.feature has:
>>   FeatureCollection
>>   DataFeatureCollection
>>     
Regardless of waiting for Justin or not these classes need to not extend 
java.util.Collection; the "for loop" syntactic sugar is too dangerous. I 
am still waiting on feedback from two ideas:
- feature visitor returning a result
- review of design decisions in google collections api (which has the 
same restrictions of scale we are faced with)
>>   FeatureEvent
>>   FeatureListener
>>     
These are used by FeatureStore
>> ogt.feature (in gt-api) has:
>>   FeatureCollection
>>     
I would not mind using this interface.
>>   CollectionEvent
>>   CollectionListener
>>     
The GeoAPI data access stuff needs to be thrown out. End of story.
>> Gt API Name, NameImpl:
>> ---------------------
>> These are essentially identical with the latter having been edited more
>> recently. Can we change the former to extend the latter and deprecate it
>> or simply remove it?
>>     
> that's a surprise to me. I though we only had NameImpl.... seems like a 
> mistake to me and we should just remove one of them (Name).
>   
Name was used during the transition period. There is a conflict between 
Name and Generic Name at the geoapi level that
has yet to be resolved very well.
>> Gt API filter:
>> -------------
>> Most of the classes in ogt.filter in the gt-api module seem to be
>> deprecated but this appears to not have been done systematically so, for
>> example, Expression is deprecated but not ExpressionType which it
>> extends. So what's going on?
>>     
We need to retire the geotools classes. ExpressionType I believe can 
still be determined using a utility method (a bunch of code uses it in 
switch statements).
> That's a (huge) technical debt of the library (and thus of us) 
> <http://docs.codehaus.org/display/GEOTOOLS/Technical+Debt>.
>
> The change to geoapi filter was supposed to fully happen for 2.4, I tried and 
> did some of the move to geoapi filter, others did the same, but we got stuck 
> on some datastores being really difficult to port and lack of spare time.
>   
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://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to