Things are getting pretty crowded in our current folder structure. Im
thinking we could group things by purpose rather than a mixing a lot of
things together. There's a lot of crossover, so there would be plenty of
READMEs and dynamic references I think.
- webapp/
- fluid-components/
- fss/
- flash/
- templates/
- js/
- real-world-demos/
- sakai/
- uPortal/
- bSpace/
- jQuery/
- functional-demos/
- inline-edit/
- keyboard-a11y/
- pager/
- renderer/
- reorderer/
- ui-options/
- fss/
- tests/
- WEB-INF/
I think it may be long, but its pretty straightforward. If you want to
learn, functional-demos is for you. If you're a partner and you want to see
specific implementations, real-world-demos is for you. fluid-components
would be framework + dev content only. No mixing of stuff.
Any thoughts?
Jacob
--
Jacob Farber
University of Toronto - ATRC
Tel: (416) 946-3002
www.fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
