Here are some more suggestions. I really really like WM, so don’t take these suggestions as complaints. They are simply suggestions.
How about being able to “write output to disk” from a context menu (on output nodes only, naturally) so that I don’t have to open the properties panel to do it.
While we are at it, how about being able to edit paths directly (know where it says Filename: and Set?) That way if I am just changing a version number I can get in there and switch it without having to use the gui (which on Windows always seems to dump me in the wrong directory).
And while we are on that subject, the File Output nodes are good in that they remember the path to where they were pointing when you click “Set”. File Input nodes, however, don’t. They just revert back to whichever directory was last accessed.
It would be nice if the File Output and File Input properties panels were resizable (or at least the Filename fields were longer). Right now all I can see is the path, but not the actual filename. I have to click in the field and then scroll to read the file name.
Even better would be if the properties-panel-as-a-modal-dialog were to go away. Instead, we could have a properties panel that was docked on the right in the same way there are controls on the left. Optionally, this docked panel could be shown as a separate window, but still always be active. In this way, whenever I click on a node, it’s properties would load into this area on the right. And simply clicking on a node will let me see the properties instantly, but without interrupting my flow. Similar to the Properties panel in Maya or Shake.
Change the nodes in a manner similar to how Apple’s Shake works. In Shake I can view one node, and change the settings in another. Now, I know I can do this in WM as well, but the interface in Shake is much smoother. If I double click a node I will look at the output of that node as well as see the properties of that node. If I click on a little box on the left of a node, that is the node I am looking at. If I click on a little box on the right of a node, that is the node I am editing. This makes it very easy to modify settings in one node while seeing the output of another. Low priority since we can already do this, just think it might be a smoother way to go.
Have an option to allow the lines connecting the nodes not be bold, as well as allowing the text under a node to not be bold.
Here’s a big one. I suspect that WM evaluates all nodes when I say “Write output to disk”, and not just those that are connected in the network that has the file output node in it. I am currently working in tiles, and have 16 separate trees going on, each with their own input and output nodes. When I try to write one of the output nodes, I can see that each and every node in the entire file is built. Since this is taking an awful long time, I am going to separate the trees into individual files. But that seems a pain. It would be nice if the app automatically culled any nodes that were not linked to the current tree while it was building.
That’s it for this time. Keep up the good work 
Ben
