 |
|
   |
|
|
 |
Q: What is Openwave SDK 5.1? A: Openwave has made this available so that you can begin to experiment with XHTML Mobile Profile & CSS Mobile Profile applications and services. Q: Why use XHTML Mobile Profile & CSS Mobile Profile? A: : XHTML Mobile Profile and CSS Mobile Profile are expected to be the mark-up languages (WML2) for WAP 2.0. The WML2 portion of the WAP 2.0 WAE is in public review as of this writing. Openwave SDK 5.1 includes a phone simulator incorporating Openwave Universal Browser 1.0 which supports the expected WAP 2.0 WAE. Q: When will XHTML phones be on the market? A: While XHTML phones will begin shipping in Japan for Christmas, 2001, we do not expect XHTML phones to be on the market in the rest of the world until mid-2002, with significant volumes not appearing until well into the latter half of the year. Q: Can I create M-Services or WAP 1.2 applications and services with 5.1 SDK? A: Yes. Simply develop with the Siemens S45 or the Generic devices. Q: Can I connect the XHTML device to a WAP gateway? A: No. You must use HTTP Direct Mode. If you try to connect to a WAP gateway, such as devgate2.uplanet.com, the Simulator will hang until the connection times out. Openwave Mobile Browser, Universal Edition, contained in the XHTML device, does not use WAP. Anticipating WAP 2.0, it is designed for an end-to-end HTTP and (W)TCP/IP environment. A WAP gateway will not be able to connect to it. Q: The Simulator is frozen, do I need to kill the SDK? A: : Probably not. If you have tried to connect the XHTML device to a WAP gateway, you just need to wait until the connection has timed out. When control returns, go to the Device Settings dialog from the Simulator Menu and change your setting to HTTP Direct. Q: What is XHTML Mobile Profile? A: XHTML Mobile Profile is a superset of XHTML Basic. XHTML Mobile Profile is the set of XHTML tags we expect to be approved (along with CSS Mobile Profile) as WML2- the mark-up language for WAP 2.0 WAE. Documentation on XHTML Mobile Profile is included with Openwave SDK 5.1. Q: What is CSS Mobile Profile? A: CSS is a powerful system of style and formatting control designed to work in conjunction with XHTML. Mobile Profile is a set of elements appropriate to a small, portable device such as a phone. We expect CSS Mobile Profile to be approved as part of WML2- the mark-up language for WAP 2.0 WAE. Documentation on CSS Mobile Profile is included with Openwave 5.1 SDK. Q: After cancelling a previous install attempt, your setup always launches in maintenance mode, but with nothing installed. You are unable to uninstall. The TARGETDIR is erroneously set to the Windows directory. This happens after you cancel a setup in an early stage. A: Normally, when the installer is run and the directory does not exist then the installer runs in first time mode and if the user cancels neither the directory nor the file is created. Normally, when the directory and the file both exist the installer runs in maintenance mode and if the user cancels the setting in setup.ilg are left unchanged. What seems to happen to a user is that she installs the package, later the setup.ilg file is lost for some reason: perhaps it is moved by an accidental gesture in Windows Explorer, perhaps Scandisk loses it while repairing disk damage or whatever. The next time that the user runs the installer, either the original or from add/remove programs, it unexpectedly runs in first time mode. The user has doubts and so she cancels. This will leave an unusable setup.ilg on the machine, causing the described symptoms. Steps to reproduce: 1. Install an application 2. Delete all of the files from its C:\Program Files\InstallShield Installation Information\{...GUID...} directory. 3. Run the installer again and press Cancel to the Welcome wizard dialog. 4. Run the installer again, you are now in maintenance mode with nothing installed and a faulty target directory. Workarounds: Delete the file C:\Program Files\InstallShield Installation Information\{...GUID...}\setup.ilg. For this you must first make the hidden directory C:\Program Files\InstallShield Installation Information visible. Status: InstallShield has confirmed that this is a bug in IS 6.22 and 6.31. Q: How to view Chinese Characters using SDK 5.1? A: You can view Chinese characters with SDK 5.1 that runs on windows 2000 platform. Please follow these steps to set up your machine and simulator: 1)Open "Regional Options" in control panel 2) On the General tab, under Menus and dialogs, select the language you want. On language settings, choose both simplified Chinese and traditional Chinese. 3)Launch SDK 5.1 and choose generic. 4)Set the device font to "NSimSun" and script to "CHINESE_GB2312" for simplified Chinese. For traditional Chinese you need to set device font to "PMingLiU" and script to "CHINESE_BIG5". Q: What are the new GUI elements that I can use? A: The GUI elements that have been introduced as part of the M-Services initiative are as follows: --Pop-up Lists --Radio Buttons --Push Buttons --Horizontal Rules Additionally, the Openwave Mobile browser contains enhanced support for the <input> elements, the title attribute for the Q: Why should I be concerned about the Openwave Mobile Browser GUI? A: The M-Services initiative from the GSMA contains a requirement for handsets to support a GUI. This will allow developers to develop more usable and intuitive content for devices, thereby improving user satisfaction and increasing the likelihood of users continuing to use the service. To achieve this, deliver the best user experience, and an advanced graphical user interface, Openwave presents the new UI features of the Mobile Browser. Q: When will phones with the Openwave Mobile Browser version 5 GUI be available? A: Openwave first introduced the Graphical User Interface (GUI) in Mobile Browser WAP Edition Version 5 at the GSM World Congress in February, 2001. Handsets containing the GUI began shipping in the European market in late Summer 2001, with the release of the Siemens S45. Many more models are expected to be released into the worldwide GSM Market before the end of the year. Q: What new tags and/or attributes are supported? A: The following list contains the new attributes/tags which are supported by Mobile Browser WAP Edition Version 5: < select type="list"> < select type="popup"> < select type="radio"> Q: Can I view WML 1.3 GUI content with the UP.SDK 4.1?. A: You can view your WML 1.3 GUI content on the UP.SDK 4.x only when connecting through a WAP Gateway (i.e. devgate2.uplanet.com). The UP.SDK version 4.x does not support WML 1.3 GUI content in HTTP Direct mode. Please be aware, that as older browsers do not support the new elements, your WML 1.3 application may not render as you anticipate, and you will need to continute to maintain your existing WML 1.1 application. Q: Will my existing WAP applications work on new GUI phones? A: You can definitely view existing, non-GUI WML content on an Openwave Mobile Browser GUI phone. However, to take advantage of the full feature set of the Mobile Browser GUI, you will need to design your application to make use of the WML GUI elements. Q: What is the difference between the Mobile Browser V5 GUI browser and a Mobile Browser V5 textual browser? A: The Mobile Browser V5 textual browser has all of the features such as User Agent profiling, WTLS Class2, Download Fun, support for WAP Push, etc??, minus the GUI interface. The V5 textual browser will render content the same way as the Mobile Browser v4.x browsers. Q: What image formats are supported by the browser? A: Image support depends on the hardware. All Openwave Mobile Browser devices support WBMP and BMP. Color devices will support 8 bit PNG images by default. Support for other image format will be dependent on the device. Please note that PNG images will not be rendered on a monochrome device. If you want to use color image in you application for devices that support color, your application will need to detect if the device support such format. This will be discoverable from the HTTP_ACCEPT header, or the UAProfile. Q: What is the official name for this WML with GUI tags? A: WML 1.3 with GUI extensions. Q: What DTD do I need to use? A: The official DTD to be used to deliver WML 1.3 with GUI extensions is: < !DOCTYPE wml PUBLIC "-//PHONE.COM//DTD WML 1.3//EN" "http://www.openwave.com/dtd/wml13.dtd"> Q: How do I create a popup menu to be used for navigation? A: Use to build a menu on the softkey. This menu will be accessible through out the card. Q: Why does my causes compilation errors? A: The is the only do element that needs to be within a paragraph (< p> ....< /p>). Placing the button outside of the paragraph will cause compilation error. Furthermore, buttons are not allowed within a table cell. Q: Why does onpick attribute not work with < select type="popup"> or < select type="radio">? A: The "popup" and "radio" select types are designed for assigning values, not as a navigation element. As such, the onpick attribute will be ignored for < option>s within these types of select elements. Q: Why does the second select list on a card render as radio buttons? A: If type is not specify in the second select list, the browser will automatically render the second select list a radio button. This feature will allow users to be able to select items in the second select list. Q: Why does the new attribute and the < hr/> tag causes compilation errors? A: Please ensure you are using the correct DTD: < !DOCTYPE wml PUBLIC "-//PHONE.COM//DTD WML 1.3//EN" "http://www.openwave.com/dtd/wml13.dtd"> Q: How do I preselect value for the popup and radio buttons? A: You can use the value attribute in the list to specify the default selection. < select type="popup" name="ccard" value="Master Card">< option value="VISA">VISA < option value="Master Card">Master Card < option value="American Express">American Express < /select> Q: Why can't I use multiple="true" attribute with popup and radio buttons? A: Multiple item selection is reserved for select type="list". Q: Can I modify the entries in the browser menu? A: No, this is the browser's default menu. All WML application should use the < do type="options" > to create their own menus. Q: How do I detect GUI browser devices? A: All V5 GUI browser will contain the text "(GUI)" in the User Agent string. Since other browser may use the text "GUI" in their user agent string. Your application should first check if the browser is an Openwave mobile browser first by checking if either "UP.B" or "UP/" is in the User Agent string. Please read the Mobile Browser WAP Edition Version 5 Style Guide for more details. Q: Can I have buttons side by side? A: Yes, the buttons does not truncate text so make sure the size of the title in the button does not exceed the screen width. Your paragraph setting needs to be in wrap mode i.e. . If your paragraph is in "nowrap" mode the button will be rendered on its own line.
Example: Buttons side by side.
< p mode="wrap"> < do type="button" label="Main Menu"> < go href="index.wml"/> < /do> < /p> Q: How do I render a single check box? A: You can use multiple select list with a single option to render as check box. < select name="wrapping" multiple="true"> < option value="true">Gift Wrapping?($$1)< /option> < /select> Q: Can I have buttons in a table? A: No, the button is a element and hence it is not allowed in the element. |