On 2014-05-28, at 3:48 PM, Justin Obara wrote: questions arose regarding how best to organize the various demos. Currently we have demos, instructional-demos, integration-demos, stand-alone demos, and manual tests. It's hard to know the difference between these.
Good questions, Justin. I looked back though past emails and discussions and found this email: http://fluid.2324889.n4.nabble.com/Proposed-folder-hierarchy-for-Infusion-code-td8919.html Basically, the proposal was: src framework components lib module demos showcase instructional integration <- to be destroyed standalone tests For the demos/instructional folder, the hierarchy would mirror, as much as reasonable, the hierarchy of the source folder. In general: demos/instructional framework core prefs renderer components componentX shared css shared.css html shared.html js shared.js demoX css file.css html file.html js file.js demoY css file.css html file.html js file.js componentY etc -- Anastasia Cheetham Inclusive Design Research Centre [email protected]<mailto:[email protected]> Inclusive Design Institute OCAD University
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
