improve browser-based workflow

[forresto]

Throwing this here, my response to a gripe on the FBP list:

We're working on it. I agree that it is painful, so I'll be making this a priority as I get used to browser-side NoFlo. On the roadmap:

• Adding components one-at-a-time from files as they are added to graph
• Making new components and editing CoffeeScript or JavaScript within the ui
• Build: concatenating and minifying the components in a particular graph into one .js file

[bergie]

To add to the build step: remove all unused components from the built file (requires a NoFlo-specific component plugin, and particularly for componentjs/builder.js#125 to be merged)

[forresto]

In the build step, it would be nice if I could specify library files per component.

For example with noflo-seriously it would only include the effects used: https://github.com/forresto/noflo-seriously/blob/master/component.json

[forresto]

Tagging #61 and this thread on the FBP group.

[bergie]

For the building step, this is solved by https://github.com/noflo/grunt-noflo-browser