Re: [udig-devel] RE: RE: Problems adding a layer programmatically

[ukpete <pete@xxxxxxxxx>]

Gotcha.  I think some confusion in my mind rises from the design
differentiation between "internal" and the "public" interfaces - while the
name is suggestive that the internal is well, specific only to UDIG, many of
the methods it provides are the ones that you need to manipulate maps/layers
and so on - while the "public" ones are for read-only purposes.

As I've gone through the documentation - and read many of the postings, a
fair few examples do seem to happily expose the internal objects for use in
various read/write/edit operations.  So its difficult from a best practices
standpoint to determine what the appropriate interface/object to use is.

Pete



Cory Horner wrote:
> 
> ukpete wrote:
>> 
>> Yeah, I tend to use the versions in internal for that reason.  Not best
>> practice, but I *need* those methods, and many of the useful ones are not
>> provided in the public interfaces.
>> 
>> import net.refractions.udig.project.internal.Map;    (etc)
>> 
>> Pete
> 
> Whenever this is the case, please get on this list and scream "i need a 
> public method"!
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/Feature-Selection-using-example-tf3116329.html#a8641042
Sent from the udig-devel mailing list archive at Nabble.com.