Roadmap Notes

From LilyWiki

As the end of the beta cycle draws near, here are some ideas for the road ahead

1. Tests: test harness for automated unit testing.
2. Documentation:
   1. need a better way to automatically generate external reference documentation.
   2. Need app code docs.
   3. Need some proper tutorials.
3. Need an optimized, cross-browser version of Lily that can run a patch in a webpage See Dechromification for details.
4. New UI:
   1. curved/angled (canvas-based) connections.
   2. connection color should be user definable.
   3. "dockable" debug window
   4. integrated object inspector
   5. "hoverable" object quick-help
   6. "themeable" patch defaults
5. Code Overhaul:
   1. New message class that wraps all messages, enable mixing arguement types, eliminate need for parsing.
   2. Consistent member naming
   3. Only one global object
   4. Eliminate patch scope event registration for externals
   5. Remove old subpatch code.
6. Better debugging:
   1. Show last error.
   2. Visual feedback for message passing.
7. New objects:
   1. canvas based version of the "svg" object,
   2. new web apis,
   3. screenshot extern
8. Need alignment & snap to grid options to simplify UI building.
9. Web Site
10. Need a way for users to share patches
    1. This might be within the app or on a website.