Hemi.app.moduleHemi JavaScript FrameworkHemi JavaScript Framework Project/Hemi/Hemi.app.moduleHemiModules are external script instrumented with a basic API to operate within the Hemi framework and be included in the Hemi.registry service. Similar to Application Components, the concept permits a typical external JavaScript format but which operates within its own namespace. The module class also includes basic support for unit testing, so that modules may be quickly written to act as externally loaded unit tests. For example, the Application Component Tests includes several unit tests for vetting the Application Component class.service3.1.9Static implementation of the hemi.app.module.serviceImpl class.serviceImpl3.1.9The module service provides a convenience for modularizing and managing standard JavaScript as reusable components and tests.NewModuleName of the ModuleXHTML Component acting as a container for the module.Path where the module resides.A framework object for which a decorateModule method is defined.Bit indicating that the path is the text of the module to load.Alternate module type for reference implementations.A new Module object.Creates a new Module object. vMod._IMod(); UnloadModuleImplementationsName of the ModuleBit indicating whether the module implementations were removed.Destroys all module implementations for the specified module. Modules use the hemi.object.addObjectDeconstructor So, destroy is present (or it's a bug) and invoking destroy will also clean up the object. UnloadModuleName of the Test ModuleBit indicating whether the module was removed.Unloads the specified module.LoadModuleName of the ModulePath to the modules directory.Additional script to include in the module prior to the module being instantiated.Bit indicating that the path is the text of the module to load.Alternate module type for reference implementations.A new Module object.Loads a Module definition.ModuleBaseThe ModuleBase is the raw definition from which a Module implementation is created.An array of object ids representing instances of this ModuleBase.ModuleA Module encapsulates the imported JavaScript and an API for operating within the framework.InitializeInvoked when the module is loaded.UnloadInvoked when the module is unloaded or destroyed.A pointer to an underlying XHTMLComponent, if the module is bound to an HTML element via an XHTMLComponent.The name of the module.An anonymous pointer to the Module instance, for refering to the instance from the anonymous scope enclosure.A pointer to the XHTML Node for which the module was loaded.A pointer to the XHTMLComponent created for any Container, if a Container was used. + "this._IMod = function(){ Module = this; };" if(!b) o.raw = x; DecorateModuleHeaderName of the ModulePath to the ModuleThe raw imported text of the module.A value to be included in the module header prior to the module being instantiated.Decorates a module header.DecorateModuleContentName of the ModulePath to the ModuleThe raw imported text of the module.A value to be included in the module prior to the module being instantiated.Decorates a module content.RegisterName of the ModuleObject hash representing the module API.Internal module object.Registers a Module object. m = { name: n, data: c, impls: [] }; return m; Modules are external script instrumented with a basic API to operate within the Hemi framework and be included in the Hemi.registry service. Similar to Application Components, the concept permits a typical external JavaScript format but which operates within its own namespace. The module class also includes basic support for unit testing, so that modules may be quickly written to act as externally loaded unit tests. For example, the Hemi_api.htmlAPI Index