Moriel Schottlender 3101bfc537 Separate model's symbolic name and model's source ... This should have been done from the beginning; the model manager pulls models by their symbolic names. So far, we've used the source for that, but that assumes that two modules always have different sources, and that is absolutely not necessarily the case. For example, internal local bundles will each be a model, but have the same ('local') source. They should still be differentiated in the manager by their names, but the source should state clearly that it is local. For this, the models now have "getName" method and the name is created separately from their source. Items also preserve a reference to their parent's symbolic name so they can provide that for items that require the controller to manipulate a specific model. Change-Id: I8c39d5d28383d11fb330addce21e07d5c424da6f		2016-06-09 16:20:57 -07:00
..
mw.echo.Controller.js	Separate model's symbolic name and model's source	2016-06-09 16:20:57 -07:00