UX improvement: shortcut for New node about nodebox

[Shrinks99]

I would second this comment though I wouldn't go with Shift+A, Blender's default shortcuts are not exactly "industry standard" as they'd be the first to admit.

I would instead suggest the tab key, the default shortcut for adding new nodes in Nuke, Natron, Maya, Blender's "Industry" keymap, and Houdini... among others.

Ctrl+Shift+N is a really bad choice for this shortcut. Adding nodes to the graph is an incredibly common task and should be made as friction-less as possible. I would highly recommend condensing it to the tab key, this will result in serious speed improvements and will make users with experience in any other node-based software feel more at home in Nodebox.

[rachellewillemsma]

Agreed, having the tab key as a new node shortcut would be drastically more efficient. I wasn't even aware there was a shortcut until now. Adding nodes is pretty much the primary thing a user does in this program, so would make sense to make the shortcut as short as possible.

[fdb]

Currently, you can double-click to place a new node where you want it to appear. This solves the problem of NodeBox having to figure out where to place the new node...

[Shrinks99]

Nodebox already does a reasonably good job of placing nodes in the graph when users utilize the shortcut, type to find the node they want, and hit enter. This text-based workflow is the primary way that people add nodes in node-based software.

Nodebox has integrated its graphical discovery system and text interface for adding new nodes to the graph within the same window. This is all well and good, no complaints here. The problem this issue is trying to address is the non-standard and slow shortcut for opening the new node window.

[rachellewillemsma]

Yes, the problem is with the need to use the mouse every time a new node is added. It seems using Ctrl+Shift+N simply places the node in the centre of the current view. I see no reason why a shorter keyboard shortcut could not do the same. Nothing wrong with just keeping the double click shortcut as a secondary option if the user wishes to specify an exact location for the node.