The application/oipfApplicationManager embedded object
If one of the methods on the application/oipfApplicationManager is called by a webpage that is not a privileged DAE application, the OITF SHALL throw an error as defined in section 10.1.1.
The Widget installation has started. This state SHALL be used to indicate that the download of the Widget package is completed (possibly because the Widget was already stored locally) and the OITF is ready to start the Widget installation process. This state SHALL NOT be signalled if the package download fails.
The Widget installation has completed successfully
The Widget installation has failed either because the Widget package download failed or because, after the download, the Widget installation process failed.
The Widget uninstallation has started
The Widget uninstallation has completed successfully
The Widget uninstallation has failed
The local storage device is full
The Widget cannot be downloaded
The Widget package is corrupted or is an Invalid Zip Archive (as defined in [Widgets-Packaging] )
Widget’s Signature Validation failed
The Widget exceeded the maximum size for a single widget allowed by the platform, as defined in section 9.1.
The user and/or the OITF denied the installation or update of a Widget
The function that is called when the OITF is running low on available memory for running DAE applications. The exact criteria determining when to generate such an event is implementation specific.
readonly WidgetDescriptorCollection widgets
A collection of WidgetDescriptor objects for the Widgets currently installed on the OITF.
Application getOwnerApplication( Document document )
Get the application that the specified document is part of. If the document is not part of an application, or the calling application does not have permission to access that application, this method will return null.
The document for which the Application object should be obtained.
ApplicationCollection getChildApplications( Application application )
Get the applications that are children of the specified application.
The application whose children should be returned.
Provide a hint to the execution environment that a garbage collection cycle should be initiated. The OITF is not required to act upon this hint.
void installWidget( String uri )
Attempts to install on the OITF a Widget located at the URI passed. If the Widget is stored on a remote server it SHALL first be downloaded. This specification does not specify where the OITF stores the Widget package, nor does it define what happens to the original package after the installation process has finished (regardless of whether it succeeded or failed).
When trying to install a Widget with an “id” that collides with the id of an already installed Widget (where the “id” is defined in section 7.6.1 of [Widgets-Packaging] along with the extension defined in section 11.1 of this specification), the OITF SHOULD ask the user for confirmation before installing the Widget. The OITF SHOULD provide information about the conflict (e.g. the version numbers, if available) to allow the user to decide whether to proceed with the installation or to cancel it.
If the user confirms the installation, then the new Widget SHALL replace the one already installed; any storage area associated with the replaced Widget SHALL be retained. Note that the user can also choose to downgrade a Widget, i.e. install an old version of the Widget to replace the installed, more recent, one.
The resource locator in form of a URI, which points to a Widget package to be installed.
void uninstallWidget( WidgetDescriptor wd )
Uninstalls a Widget. If this Widget is running it will be stopped. Any storage areas associated with the uninstalled Widget SHALL be deleted.
A WidgetDescriptor object for a Widget installed on the OITF.
For the intrinsic events listed in the table below a corresponding DOM event SHALL be generated in the following manner:
Corresponding DOM event
DOM Event properties
Context Info: None
Context Info: appl
Context Info: appl
Context Info: appl
Context: wd, state, reason
Context: wd, state
NOTE: the above DOM events are directly dispatched to the event target, and will not bubble nor capture. Applications SHOULD NOT rely on receiving the events listed above during the bubbling or the capturing phase. Applications that use DOM event handlers SHALL call the addEventListener() method on the application/oipfApplicationManager object. The third parameter of addEventListener, i.e. “useCapture”, will be ignored.