Re: [udig-devel] Dependency graph is getting messy (perhaps)

[Graham Davis <gdavis@xxxxxxxxxxxxxxx>]

Hi Jesse,

Yes it looks like I added this to access preferences for things like 
disk-caching vs in-memory tile caching,  and also for choosing the 
number of threads that would be used for making tile requests at any one 
time. 

I did not realize there was a dependency boundary to be aware of.  So, 
if I were to remove this dependency, how can I access preferences?  I've 
been doing something like this:

String dir = 
ProjectPlugin.getPlugin().getPreferenceStore().getString(PreferenceConstants.P_WMSCTILE_DISKDIR);

How can I do something similar from the catalog.wms package without the 
ProjectPlugin?  Thanks,

Graham


Jesse Eichar wrote:
> I took a look and it looks like the dependency is to access 
> Preferences defined in the project plugin.  I think we can remove that 
> dependency fairly easily
>
> Jesse
>
> On 7-Nov-08, at 9:27 AM, Jesse Eichar wrote:
>
> > Mainly for Emily and Jody I think,
> >
> > I just discovered that catalog.wms depends on project.  Jody can 
> > chime in as well but up until now the layers were:
> >
> > Printing
> > Application - project, renderers, tools
> > Platform - catalog
> >
> >
> > Seems to me that this is causing the boundary between application and 
> > platform to blur.  Are you sure you need that dependency?
> >
> > Jesse
> >
> > _______________________________________________
> > 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


--
Graham Davis
Refractions Research Inc.
gdavis@xxxxxxxxxxxxxxx