Framework APIs
The Palm® Mojo™ APIs include a range of controller methods, storage and UI functions, development aids and various features that you might need within your application. This is the default location for API reference information; it will be here unless you are looking for information on a widget or service, in which case see sections Widgets and Services API.
Notes :
- You can find the specific API documentation listed in the following table.
- For related tutorial information, such as for controllers, events, widgets, and storage, see Application Basics in the Mojo Developer Guide. There are also some technical notes that overlap with the information below, but they are referenced within the individual API documents.
| API | Description |
|---|---|
| Mojo.Animation | Holds the infrastructure for coordinating timers for multiple animations, and animating DOM element styles and numeric values over time. |
| Mojo.Animation.Quene | Allows for running multiple animations using a shared timer, since the overhead of running multiple timers is pretty high. |
| Mojo.Char | Holds character code values and some useful key code checking methods. |
| Mojo.Controller | Controller functions designed to assist in managing stages and scenes. |
| Mojo.Cookie | Creates a cookie object with a particular name. |
| Mojo.Depot | Stores JavaScript objects in a database. Currently implemented as a framework wrapper around HTML5 active record access. |
| Mojo.Drag | Creates container destinations and draggers for drag and drop items. |
| Mojo.Event | Holds functionality related to the UI Toolkit Events. |
| Mojo.Environment | Provides information on the platform on which the application is running. |
| Mojo.FilePicker | Method to pick a single file from the device's local storage. |
| Mojo.Format | Functions related to formatting dates, times, and numbers. |
| Mojo.Function | Used to "debounce" multiple calls to a function. |
| Mojo.Function.Synchronize | Used to ensure that a set of callback functions are all called at the same time. |
| Mojo.Locale | Returns an array containing the names of the weekdays in calendar order for the current locale. |
| Mojo.Log | Provides an efficient way to output interesting information from a running application, but not have it slow down the application. |
| Mojo.Menu | Unlike all other widgets, Menu widgets are not declared in your scene view file, but are simply instantiated and have their actions handled from within your assistant completely. |
| Mojo.Model | Contains helper functions for dealing with data in a JSON object. |
| Mojo.Service | An on-device "server" for any resource, data, or configuration that can be exposed for developers to use with their applications. |
| Mojo.Timing | Controls for timing. |
| Mojo.Transition | Contains public constants for the graphical transitions usually used for pushing and popping scenes. |
| Mojo.View | All UI layout files are located in the views folder of your application. Much of the user interface in the SDK is assembled out of text files containing fragments of HTML and special tags indicating locations to insert dynamic data. |
| Mojo.Widget | The actual widget implementations are "widget assistants" in the various widget_*.js files, and common widget behavior is mostly encapsulated in widget_controller.js. |
| Mojo | This section contains some methods that can be used to debug your applications and other utility functions (assert, require, loadScriptWithCallback ...) |