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.

Sign up for GitHub

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

Jump to bottom

tree editor UI #5

Open
KevinField opened this issue Aug 7, 2015 · 1 comment
Open

tree editor UI #5

KevinField opened this issue Aug 7, 2015 · 1 comment

Comments

@KevinField
Copy link
Collaborator

With drag-n-drop, colour picker, and image uploader.
@KevinField
Copy link
Collaborator Author

We'd have to be a bit careful with a normal tree editor interface, that it remains intuitive to use, and that updates to one section happen to all of its extra references: even with a loop checker, our data may not be a tree: menu 1 could refer to menus 2 and 3, but menu 2 could also refer to menu 3, for example, and in a directed graph sense this is not a loop. Should this be allowed or should everything have to be a proper tree (not just for the sake of a tree editor UI, but the end user also)?

This was referenced Aug 12, 2015
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KevinField