In many applications with a toolbar, you can right-click the toolbar to customize it (rearrange where the controls are). You can also add/remove control text/icons, and you can select "use small size" (Disk Utility is a reasonable implementation of the features mentioned - some lack the use-small-size option). There's also a hide option, though that doesn't seem useful in this situation.
It'd be nice on small-screen devices (like my MBA) to be able to reduce the toolbar size some.
• First Item
• Last Item
• Random Item
• And I guess when the "Allow List To Single Ports" will be implemented, the team will probably also add an "Iterate List" option.
The idea here would be to get also either a "Get Item at Index" that would have a sub-menu listing the indexes (may be a problem in the case of very very long lists) or better as Martinus suggested, a prompt that would allow us to enter an index value (integer).
This would avoid having to manually add "Get Item`nodes in between.
It would be nice to be able to render directly to the editor background. That way the logistics of working with multiple windows will be a little less hassle when working with only one screen (less wasted screen estate). Preferrably with a node transparency option. It would also make (video) tutorials a bit easier as the result is displayed directly if screencasting or recording.
An observation ... when creating compositions I find clear layout is crucial. I find myself clumping functional units together, eg: IO section, display section and so on. Then occasionally one want to connect one part with a distant other part which often involves connections passing under nodes and immediately seems to make things messy, especially when the source or destination cannot be seen on the screen at once. This confusion also arises from links connections from the right to the left in a composition, eg: those pesky window request frame connections.
What I think would be "nice" would be a node that acts as a "sink" for data+events and another node that acts as a "source". These would be associated together by an id, or better a name. They could of course be colour coded ... seems to me this could be used to add clarity to larger compositions.
