#2132 closed enhancement (fixed)
Ability to compile full dependency list of a resource
Reported by: | jng | Owned by: | jng |
---|---|---|---|
Priority: | low | Milestone: | Maestro-5.0 |
Component: | Maestro | Version: | |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description
Currently, when looking at a dependency list of a resource (via properties). It only shows direct dependencies. What would be useful is to be able to compile a list of full dependencies.
So for example, a full dependency list for a Map Definition would not only include its Layer Definitions, but their Feature Sources and any Symbol Libraries and Symbol Definitions used.
Change History (5)
comment:1 by , 12 years ago
comment:3 by , 12 years ago
I don't see the change here (local build following SVN update)!? From the Sheboygan .MapDefinition I see the layer definitions and watermark in the properties reference but not the feature sources.
comment:5 by , 12 years ago
I see it now. Personally I think having similar (but not quite the same) list as context menu and properties reference is a little confusing - but still overall more beneficial overall to have it at all! I maintain a dependancy-walker style UI showing the relevance of the resources to each other would be the icing on the cake.
A cascading recursive type tree control would be a nice UI for that feature