Project:
| View Revisions: Issue #27349 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0027349: [API Deprecation] The HookManager does not have to depend on the OB.MobileApp.model object | ||
| Revision | 2014-08-16 15:17 by Orekaria | ||
| Description | There is no reason for the HookManager to depend on when the OB.MobileApp.model is created, thus, the objects must have their own namespace Reason for this API change: If the HookManager depends on OB.MobileApp.model, the creation of the model have to be done before the HookManager attaches to it. This behavior is unwanted and leads to: - unnecessary restrictions in further code developments - errors if the HookManager is not available when requested - errors if the HookManager was instanciated before the model was, because if OB.MobleApp.model is initialized after the HookManager, the HookManager is removed Changelog: - OB.UTIL.HookManager now instanciates itself - removed the initialization 'this.hookManager = new OB.UTIL.HookManager();' in ob-terminal-model.js - renamed all occurrences of OB.MobileApp.model to OB.UTIL.HookManager Howto update custom code for this change: - rename all occurrences of OB.MobileApp.model to OB.UTIL.HookManager Regressions will happen if the OB.MobileApp.model is not renamed to OB.UTIL.HookManager after applying this patch |
||
| Revision | 2014-08-16 15:09 by Orekaria | ||
| Description | There is no reason for the HookManager to depend on when the OB.MobileApp.model is created, thus, the objects must have their own namespace If the HookManager depends on OB.MobileApp.model, the creation of the model have to be done before the HookManager attaches to it. This behavior is unwanted and leads to: - unnecessary restrictions in further code developments - errors if the HookManager is not available when requested - errors if the HookManager was instanciated before the model was, because if OB.MobleApp.model is initialized after the HookManager, the HookManager is removed Changelog: - OB.UTIL.HookManager now instanciates itself - removed the initialization 'this.hookManager = new OB.UTIL.HookManager();' in ob-terminal-model.js - renamed all occurrences of OB.MobileApp.model to OB.UTIL.HookManager Howto update custom code for this change: - rename all occurrences of OB.MobileApp.model to OB.UTIL.HookManager Regressions will happen if the OB.MobileApp.model is not renamed to OB.UTIL.HookManager after applying this patch |
||
| Revision | 2014-08-16 14:59 by Orekaria | ||
| Description | There is no reason for the HookManager to depend on when the OB.MobileApp.model is created, thus, the objects must have their own namespace If the HookManager depends on OB.MobileApp.model, the creation of the model have to be done before the HookManager attaches to it. This behavior is unwanted and leads to: - unnecessary restrictions in further code developments - errors if the HookManager is not available when requested - errors if the HookManager was instanciated before the model was, because if OB.MobleApp.model is initialized after the HookManager, the HookManager is removed. |
||
| Revision | 2014-08-16 14:58 by Orekaria | ||
| Description | There is no reason for the HookManager to depend on when the OB.MobileApp.model is created, thus, the objects must have their own namespace If the HookManager depends on OB.MobileApp.model, the creation of the model have to be done before the HookManager attaches to it. This behavior is unwanted and lead: - unnecessary restrictions in further code developments - errors if the HookManager is not available when requested - errors if the HookManager was instanciated before the model was, because if OB.MobleApp.model is initialized after the HookManager, the HookManager is removed. |
||
| Revision | 2014-08-16 14:52 by Orekaria | ||
| Description | There is no reason for the HookManager to depend on when the OB.MobileApp.model is created, thus, the objects must have their own namespace | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |