Using group optional attribute to create an hierarchical layer tree - #355
Open
jgrocha wants to merge 4 commits into
Open
Using group optional attribute to create an hierarchical layer tree#355jgrocha wants to merge 4 commits into
jgrocha wants to merge 4 commits into
Conversation
Member
|
I currently don't have time to look into this, sorry. I hope to find time for this next week. Others are free to revoew of course. |
Contributor
There was a problem hiding this comment.
Shouldn't this happen in after it has been ensured groupString !== "" in line 175?
Contributor
|
Hi @jgrocha, Besides some minor issues which I addressed directly as line comments (see above) I have some major points which should be done before we can merge this:
|
Member
|
Hey @jgrocha do you think you can tackle the comments of @chrismayer? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi devs,
I recovered these two classes that help create a layer tree, from an
groupattribute. I also add an example of usage, togeoext2/examples/tree/.The only change in the existing code proposed in the PR is an additional protection (if clause) in
src/GeoExt/tree/Util.js,updateLayerVisibilityByNodefunction, to make sure that we have a layer associated with the node before checking the layer's visibility. I think this test is necessary, since we might have nodes in the tree (not leafs) without a layer.The two classes proposed in this PR are:
GeoExt.tree.LayerTreeBuilderthat extendsGeoExt.tree.PanelGeoExt.tree.LayerGroupContainerthat extendsGeoExt.tree.LayerContainerComments are welcome.