I was asked to bring my Engage-newbie eyes to help with the tasks of
restructuring the file hierarchy. Many thanks to Yura and Colin for
helping me to understand how Engage works, and for answering all of my
questions.
With a bit of brainstorming, Colin and I have come up with the
following proposed structure. We invite comments, questions,
suggestions. Soon.
/infusion
/engage-client
|- /framework
|- /components
|- /ArtifactView
|- / <subfolders as current for all components>
|- /Browse
|- /Cabinet
|- /NavigationList
|- /Description
|- /ScreenNavigator
|- /Tags
|- /infusionTesting
|- /integration_demo
|- /mobileFSS_demo
/engage-server/src/webapp
|- /kettle
|- /js
|- <config files>
|- /application
|- /js
|- EngageApp.js
|- <config files>
|- /services
|- /artifactView
|- /js
|- artifactView.js
|- /browse
|- /js
|- browse.js
|- /kettleDemo
|- <as existing>
|- /WEB-INF
** remove /mapping from SVN altogether
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
