Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two Treeview link chooser on same page #20

Closed
TheMaaarc opened this issue Jan 3, 2018 · 7 comments
Closed

Two Treeview link chooser on same page #20

TheMaaarc opened this issue Jan 3, 2018 · 7 comments

Comments

@TheMaaarc
Copy link
Member

Only the "Default container" that you click on should be opened. Not both.

2018-01-03 09_14_53

@nadar
Copy link
Member

nadar commented Jul 10, 2018

We should discuss about a general solution for links, this could also be used within zaa-links and everywhere else where page selection is done (like now, but different layout. Maybe a modal?)

@TheMaaarc
Copy link
Member Author

What exactly do you want to discuss? The zaa-link already uses the treeview for internal link selection, right?

The issue here refers to the bug that if you click on "Default container" in the second link list it closes/opens it in both lists.

@nadar
Copy link
Member

nadar commented Jul 10, 2018

This is because its the same directive, opening linke selection in a new modal would fix this problem and then we could maybe improve the link selection in general (with the containers, etc.)

@TheMaaarc
Copy link
Member Author

Ahh, okay. Well, maybe a modal would be a good solution. The tree can grow quite big for certain sites.

@nadar
Copy link
Member

nadar commented Jul 10, 2018

Yes i agree. So that's why i am saying, maybe we should restructure the whole element to fix all the issues. I think its worth to spent some time on this.

@nadar
Copy link
Member

nadar commented Jul 31, 2018

We should make a list of changes, so we can do them all together (see also #124).

@nadar
Copy link
Member

nadar commented Oct 17, 2018

As discussed today with @TheMaaarc we are going to use a combination of two already known elements the collapsible global search:

image

And the existing cms tree view:

image

There will be a search field. When a container does not provide results for the given search term, the container will be hidden (so we also need a message which says no results where found):

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants