Hemi.app.spaceHemi JavaScript FrameworkHemi JavaScript Framework Project/Hemi/Hemi.app.spaceHemiApplication Spaces are controlled environments in which the content (XHTML and XML nodes) drives the implementation (via Application Space Definitions). XHTML Nodes (Presentation Nodes) that match space definitions are represented as XHTML Components. XHTML Components can automatically load Application Components, Modules, and Templates (which in turn spawn their own Application Space). These components can be retrieved using unique object identifiers, or more friendly reference identifiers which are contextually sensitive to the space. Form fields are augmented by the Hemi.data.form service to create Virtual Forms. Spaces can load automatically, or use the Hemi.task service to bootstrap asynchronous dependencies.service3.1.9Static implementation of the Application Space service.serviceImpl3.1.9The Application Space service is used to create managed environments within Web pages. Each Application Space uses its XHTML contents for self-configuration, instrumentation, and contained lifecycle management.onspaceconfigloadThe EngineObject for which the configuration was loaded.Message published to all subscribers when configuration has been loaded.getPrimarySpaceThe primary space object.Returns the primary application space. If a space is not explicitly created prior to the page loading, then, by default, a primary space object is created for the HTML BODY.clearAppSpaceName or object reference of the Space to clear.Clears the specified Space, and destroys all components of the Space. TODO: Refactor This is effectively identical with the configureSpace pre-step, Without the cleanup routines for Form and Parent Node 2007/02/03 Clear out any XHTMLForm references to this Engine clearAppSpacesClears all Spaces, and destroys all components in each Space.loadSpacesBit indicating that a primary space should be defined if one is not specified. This param will always be true if any space exists and none are marked as primary.Object in which to search for potential space declarations.Processor to assign to the space. Used for pre-processing XML templates and configuration.XML Handler to use when invoking setInnerXHTML.Finds all spaces on the current Web page and loads them. A space node is either the body element, or a span, div, or form element with an is-space attribute. return t.loadSpaces(1); createSpaceXHTML ElementBit indicating the space is being forced.Processor to assign to the space. Used for pre-processing XML templates and configuration.XML Handler to use when invoking setInnerXHTML.Callback handler to be invoked when the space is initialized.A new space object that has been tasked to initialize.Creates a new Application Space. alert(n + ":" + at + ":" + a + ":" + ht + ":" + h); configureSpaceA space object.Name of SpaceService configuration.Applies the specified configuration to the specified engine. This can be used to repurpose Space objects, or to load alternate content into the Space. var d1 = new Date(); alert(_s.config_task); if (!c) c = "self"; Don't require external XML this.log("Time to configure = " + (new Date()).getTime() - d1.getTime()); alert("Time to configure = " + ((new Date()).getTime() - d1.getTime())); SpaceThe DOM Node associated with this Space.The unique identifier of this Space object.The friendly name of this Space object.The loading state of the space.The ordinal index of this Space object.The configuration name for this Space object. This value specifically applies to a Space Configuration file.The task object associated with this Space. All Spaces are bootstrapped with a Task object.Bit indicating whether this is the primary engine. There can only be one primary engine per hemi.app.space.serviceImpl instance.Cache of implementation constructors used to build the content within the Space.ProcessorAn object reference to this Space object.An XHTML Node, or string.Allows a document to be processed by an outside process before it is copied into the space context.getContainerThe node containing the Space object.Returns the node that contains the Space. For example, a DIV node on which the Space was defined.getSpaceObjectsArray of objects created for this Space. All objects are likewise registered with the hemi.registry.service.Returns an array of objects created for this Space.getSpaceObjectIndex into the objects array.Object created for this Space.Returns the specified object created for this Space.getSpaceObjectByNameName of an object.Object created for this Space.Returns the specified object created for this Space.getSpaceObjectsByClassCSS class name.Array of objects with the specified class.Returns an array of objects with the specified class.isSpaceObjectByNameName of an object.Bit indicating whether the object exists in this Space.Returns true if the object exists, false otherwise.getPrimitiveWireIdentifier of a primitive wire.PrimitiveWire object.Returns the specified PrimitiveWire.addSpaceObjectA framework object.Reference identifier that can be used to identify this object within the space.Adds the specified object to the application space.removeSpaceObjectFrameworkObject identifier.Removes references to the specified identifier from the space.newSpaceObjectXHTML Element representing the space.Unique identifier.Friendly name for the object.Task object used to load this space.Index of space relative to adjacent spaces.Space initialization callbackNew space object.Creates a new Space object. Copy css class names into css_map Application Spaces are controlled environments in which the content (XHTML and XML nodes) drives the implementation (via Application Space Definitions). XHTML Nodes (Presentation Nodes) that match space definitions are represented as XHTML Components. XHTML Components can automatically load Application Components, Modules, and Templates (which in turn spawn their own Application Space). These components can be retrieved using unique object identifiers, or more friendly reference identifiers which are contextually sensitive to the space. Form fields are augmented by the Hemi.data.form service to create Virtual Forms. Spaces can load automatically, or use the Hemi.task service to bootstrap asynchronous dependencies.Hemi_api.htmlAPI Index