View Full Version : Repository class pattern for controllers

3 Jan 2013, 2:57 AM
What would be a good/recommended design pattern for having repository classes that are shared between controllers, or even application-wide? (This should work in Sencha Architect as well)

A convenient way is to add a whole controller class, which can be called from other controllers via .getController(). But what would be "best practice" ?


7 Jan 2013, 10:15 AM
Controllers shouldn't really be called by others, you should either fire events on the application and be listenable from controllers or I use utility singelton classes