TODO

* use Thread.new for build to allow concurrent build and processing (colorization)
  of output
* design to allow output to be directed to a different window, though initially
  just the current stdout
* refactor duplicate code in spec & feature step definitions
  - the feature is supposed to exercise the whole stack, from view through
    controller to model.  the duplicate code indicates a bigger problem, that
    the feature therefore tests too low a level with the model & view tightly
    coupled to controller in core.rb
  - follow MVC
    - model = project.rb (an abstraction of filesystem)
    x controller = controller.rb
    x view = cli.rb
    - is this design really MVC?
      - how does controller make changes to a view?  currently there is no
        way (e.g. rails 'render')
      - really, the goal is not strict adherence to MVC, but to abstract
        out the cli and filesystem from the core of the app (controller.rb)
        in preparation for possible future 'railsification' of the app
* config.rb
  - generate config via setup.rb hook
  - see example code from Mozillion
    - http://svn.luon.net/filedetails.php?repname=goat&path=/trunk/lib/pre-setup.rb
    - http://svn.luon.net/filedetails.php?repname=goat&path=/trunk/lib/post-clean.rb
* configuration/options
  - use OptionParser

See also:

doc/live-workbench.mm
    Freemind mindmap to brainstorm ideas for the project

doc/live-workbench-stories.otl
    vim-outliner outline of possible stories to implement in cucumber