-
Notifications
You must be signed in to change notification settings - Fork 47
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
Support of more than 62 nodes #93
Comments
I've been thinking about a search mode for a while now (like less/vi, triggered with '/'), which would reduce the list of nodes to a number that is manageable using the current shortcut system. Do you have a better/different idea? |
I like the idea with the search mode similar to vim. |
Search would be great! Another benefit of the search is less time and difficulty to perform actions on a node. For example: as a new user, if I wish to perform an action to the |
Since there is interest in this, let's try to brainstorm. What do you think about the following UI flow:
The drawback that I see is that we change node keybindings, i.e. your What do you think? Can you imagine a better alternative? |
Alternative (let's call this variant B):
I guess that's more in line with how other tools do it. |
Variant b sounds quite nice! 👍 |
I implemented a draft solution in #97. Let's continue the discussion there. Beta-testers welcome! |
Fixed in #97. |
Unfortunately, if I start more than 62 nodes, then I don't have the possibility to control the nodes >62 in the command line interface as I can only refer to nodes 0..61 via a-z,A-Z,0-9.
Did you ever think of an command line interface for more than 62 nodes?
The text was updated successfully, but these errors were encountered: