[udig-devel] feature editor tutorial vs default data set

[Jesse Eichar]

The plus is that we don't have to support anything.  The BIG minus is  
that it makes more work for the end developer.  They need to know  
about Selections and IAdaptable and such.  That the big win for our  
framework.  The learning curve is much less.  No opinion on this until  
I think about it...  Although I'm leaning towards less maintenance.

Jesse

On 9-Nov-07, at 6:51 PM, Jody Garnett wrote:

> I have also had the thought to move in the direction of "normal"  
> PropertyPages. There is one downside to this; right now the  
> FeatureEditor remembers the last selection (so you can click around  
> on some other views and the editor remains focused on the last  
> feature selected).
>
> What do you guys think?
> Jody
>> I am looking at doing a feature editor here; and our code in  
>> tutorials does not match the countries.shp we ship as part of our  
>> default data download.
>>
>> So my question is:
>> - should I update the example code?
>> - or is our default dataset wrong?
>>
>> I am going to update the code, and hold off committing until I hear  
>> one way or the other.
>>
>> Aside: Making a custom feature editor for your own content is a  
>> great way to only show users some of the attributes, and to provide  
>> custom data entry validation.
>>
>> Jody
>>
>> _______________________________________________
>> User-friendly Desktop Internet GIS (uDig)
>> http://udig.refractions.net
>> http://lists.refractions.net/mailman/listinfo/udig-devel
>
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel