[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [udig-devel] Dependency graph is getting messy (perhaps)
|
Thanks Jesse, looks like you beat me to it :)
Graham.
Jesse Eichar wrote:
Done done,
I have fixed the dependency and the headless build works again.
Jesse
On 7-Nov-08, at 9:41 PM, Graham Davis wrote:
OK, that makes sense. I won't have time to fix it today (have an
appointment to get to shortly) but I can make the change on Monday.
Otherwise feel free to do it yourself if that is not fast enough.
Graham.
Jesse Eichar wrote:
Hi Graham,
Don't have too much time for this message but here's the deal.
Each plugin has preferences that you can save to. UIPlugins
typically also have a PreferenceStore which simply makes it easier
to store preferences. I added a custom PreferenceStore to
ProjectPlugin to make it easier to store preferences in that
plugin. (I think this is the or at least I am pretty sure it was
could have changed since an older version of eclipse)
So what you can do is move the plugins either to catalog.wms or
catalog.ui.
The dependency graph is important for a couple reasons.
1. There is a feature for platform so users can import just the
catalog code and make their own application without our renderers
and other baggage.
2. Because of the feature dependency graph Application Feature
depends on Platform Feature. If there is a dependency from Platform
to Application uDig cannot be built.
Sorry for the terse email but I have to put somea to bed. If you
dont have time to fix it I will go ahead and do it. I just wanted
to give you time to respond and if you could, fix it.
Have a good weekend.
Jesse
On 7-Nov-08, at 5:27 PM, Graham Davis wrote:
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
_______________________________________________
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
--
Graham Davis
Refractions Research Inc.
gdavis@xxxxxxxxxxxxxxx