initial import of widgets/models test app for using models in widgets… now to actually implement the functionality...
pass widgets directories to processModel()
made most logger.debug calls logger.info for easier troubleshooting
pass in all search paths to processModels(), including PROJECT/app
update version
change collection name from items to songs in widgets/models test app
allow new dir to be passed to findModelMigrations()
Alloy.createWidget can have either the controller name or arguments as the 2nd parameter (ALOY-529)
use <Widget> element in test apps
update docs for createWIdget() to reflect changes for ALOY-529
document "args" param in Alloy.createXXX calls as {Object}
working with processModels2() to test widget models
make sure the model directory exists before attempting to read it
use Widget instead of Alloy in widgets/models
add WIDGET_OBJECT to constants
manage current widget manifest in compilerUtils.js
add alloy/widget.js module for functions/properies specific to each widget
account for widget-level collections and models
use appropriate widget id value in widget.js
don't initialize currentManifest