The current interface of the editor (not the dashboard, only the editor) is really annoying for any non-trivial project. So I would like to discuss what to do with it. Notice that I'm neither a designer or an UI/UX expert, thus, I would like to hear from people with more expertise on this.
I have some suggestions (they can -and should- be divided into other issues before implementing them):
The left panel could show a simpler list organized in hierarchies, similar to any code editor (e.g., sublime text), where we could click on some category (e.g., nodes, or trees, or composite) and show/hide its content.
The left panel MUST have a search field in order to filter the nodes and trees.
The right panel could be completely removed. User could double click onto a node (or Edit > Node properties) to open a modal screen. This would remove the live update of the node and simplify A LOT the undo/redo logic.
The right panel could be a small panel with fast shortcuts (pretty much like any vector or image editor like inkscape and photoshop). This would be a toolbar on the right side.
Creating a connection to an empty space or right clicking on the canvas could open a simple popup to select a node (would be an alternative to dragging the nodes from the left panel). This popup would have a search field. This feature is based on the Unreal Blueprint editor.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27362865-new-editor-ui-ux?utm_campaign=plugin&utm_content=tracker%2F18331319&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F18331319&utm_medium=issues&utm_source=github).
The current interface of the editor (not the dashboard, only the editor) is really annoying for any non-trivial project. So I would like to discuss what to do with it. Notice that I'm neither a designer or an UI/UX expert, thus, I would like to hear from people with more expertise on this.
I have some suggestions (they can -and should- be divided into other issues before implementing them):