Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> com >> openwave

•com.openwave.oui.* (166)

Package Samples:

• com.openwave.oui.framework
• com.openwave.oui.rendering.alcatel
• com.openwave.oui.rendering.generic
• com.openwave.oui.rendering.msie5
• com.openwave.oui.rendering.nokia.nokia9110
• com.openwave.oui.rendering.nokia
• com.openwave.oui.rendering.upgui
• com.openwave.oui.rendering.upguinoext
• com.openwave.oui.rendering.uptext
• com.openwave.oui.rendering.uptextnoext
• com.openwave.oui.waomelements

Classes:

• Format: The Format object is intended to overcome several differences in the support of input masks (AKA formats or input formats) in handsets by different vendors. Formats are very useful for guiding users typing text into an input field. When properly deployed, formats save users from excessive typing and, to an extent, validates the data before they are sent to the server. In short, formats are extremely important for usability. Unfortunately, there are differences in the support of format by the different handsets that often force developers to renounce input masks. In this context, the Format object ...
• BodyPager: One of the worst limitations when supporting multiple devices is that the maximum deck size for all the devices is limited by the smallest maximum size among the set of devices. At the current state of the technology, this maximum size seems to be the 1492 bytes supported by the Nokia 7110. This constant is problematic, since it forces devices that support larger deck sizes to work below their capabilities. This problem can be resolved in some cases, by using the BodyPager object. In cases where large amounts of text have to be delivered to handsets, the BodyPager can ensure that larger amounts ...
• Table: The Table Object is useful for building tables without breaking the rendering on phones that do not support tables. In spite of the fact that tables are part of WML 1.1, some phones (typically the Nokia 7110) do not support tables and merely ignore table tags ("table","tr" and "td") when these are encountered. The unfortunate consequence of this is that developers refrain from using tables, since this would make the content on some browsers meaningless. OUI takes a different approach to the problem. There are three ways of interpreting the meaning of information laid out in a table: Row logic Column ...
• DoElement: The DoElement object represents <do> elements. This element is mainly used inside templates. DoElements can be attached to cards, but this is not the recommended way to use them. <do> elements effectively implement navigational element on some browsers (typically the UP.Browser), while they have a secondary role on other phones (Nokia 7110, for example). For this reason, programmers should use the addPrimaryPath(), addSecondaryPath() and addSidePath() Card methods (and their relatives) rather than DoElements directly. Those method will abstract way browser differences while maintaining ...
• Form: At times, applications require users to insert several pieces of information. In these cases you should use a form. There are two kinds of forms: elective forms and wizards. Elective forms present multiple entry fields for the user to fill in the same card while wizards collect information from users, one step at the time. If you wonder which kind of form offers better usability, the answer is: "it depends". Users of the Nokia 7110 find elective forms intuitive (in spite of the high number of clicks required to operate them), while users of UP.Browser find wizards more intuitive. The Form object ...
• Head: A Head object encapsulates knowledge about <head> elements. This object is important for exploiting advanced functionality of the Openwave platform such as pre-fetch, bookmark control, deck caching (TTL, Time to live) without breaking the code for the other browsers. Please note that some of this functionality only works in UP.Browser in connection with MAG (AKA UP.Link gateway). Some work with UP.Browser regardless of the gateway and some work on Nokia phones too. Creation date: (4/4/2001 3:37:20 PM)
• SimpleLink: The simple link object is just a plain <a href="url"></a> link. Encapsulation into an object is intended for support of the "accesskey" attribute. "accesskey" is an Openwave extension that lets developers associate a number between 0 and 9 with the link. This will be a keyboard accelerator for power-users who will manage to trigger the link simply by pressing the corresponding number. Creation date: (4/4/2001 3:37:20 PM)
• AbsPicker: This object is simple. It's basically just a wrapper around the <select>/<option> element. It allows users to select one option from a finite set of possible choices. Support for this object is similar in all the devices. There are mainly two reasons for encapsulating it: getting it to work with the Form object and protecting developers from possible problems when new devices are introduced. Creation date: (4/4/2001 3:37:20 PM)
• Picker: This object is simple. It's basically just a wrapper around the <select>/<option> element. It allows users to select one option from a finite set of possible choices. Support for this object is similar in all the devices. There are mainly two reasons for encapsulating it: getting it to work with the Form object and protecting developers from possible problems when new devices are introduced. Creation date: (4/4/2001 3:37:20 PM)
• PickerCard: There are cases where users should set a variable with one single click and then move on. While this is similar to what both Menus and Pickers achieve, those two objects don't really maximize usability in a cross-browser fashion for this specific case. The PickerCard object is a special object that achieves that. Creation date: (4/4/2001 12:57:36 PM)
• Menu: Menu navigation is better implemented with different constructs for different devices (or class of devices). The UP.Browser is better served by the <select>/<option> construct, while other browsers work more usably with variations of the classical list of hyperlinks. Creation date: (03-05-2001 12:40:25)
• TaskMenu: Menu navigation is better implemented with different constructs for different devices (or class of devices). The UP.Browser is better served by the <select>/<option> construct, while other browsers work more usably with variations of the classical list of hyperlinks. Creation date: (13-06-2001 12:40:25)
• Deck: The Deck Object is a high-level object. It is useful as a container of multiple templates and cards. Plain WML and WML with Openwave extensions have different DTDs. Encapsulating the deck into an object makes sure that the most appropriate DTD is delivered to the user agent. Creation date: (4/4/2001 12:57:28 PM)
• Anchor: The anchor object encapsulates anchors. It is similar to the SimpleLink object in many ways. The main difference is that any task can be associated to an Anchor, while SimpleLink implicitly defines a <go> task. Creation date: (4/5/2001 10:08:44 AM)
• Image: Image objects encapsulate the <img> tag. It is possible to assign different pictures for different classes of devices. If this feature is not exploited, every device will get the picture specified in the constructor. Creation date: (4/5/2001 10:08:44 AM)
• Task: Task objects abstract WML tasks as you know them: go, prev, noop and refresh. Tasks can be passed to Anchors, DoElements and to the Navigation Paths in Cards and Menus. Creation date: (4/4/2001 3:37:20 PM)
• Onevent: The Onevent object represents <onevent> elements. This element is used inside templates and cards. Creation date: (4/5/2001 10:08:44 AM)
• Template: A Template object encapsulates knowledge about templates. Creation date: (4/5/2001 10:08:44 AM)
• Input: The input object encapsulates the input element. Creation date: (4/4/2001 3:37:20 PM)
• Card: Card objects encapsulate the content of cards. Creation date: (4/4/2001 12:57:36 PM)
• Button: Insert the type's description here. Creation date: (4/5/2001 10:08:44 AM)
• Paragraph: Insert the type's description here. Creation date: (4/5/2001 10:08:44 AM)
• PathTask: Insert the type's description here. Creation date: (4/5/2001 10:08:44 AM)
• DeviceContext: Insert the type's description here. Creation date: (18-04-2001 10:00:07)
• ErrorMsg: Insert the type's description here. Creation date: (18-05-2001 10:12:49)

Home | Contact Us | Privacy Policy | Terms of Service