Browsing

Nokia Mobile Internet Toolkit 4.0 FAQ

(20-May-2003)

What is the Nokia Mobile Internet Toolkit Starter Pack? What are the other Toolkit downloads?
How can developers send content to more than one SDK at a time?
Why are developers no longer able to connect to remote sites?
What is the Update Manager? How does it work?
What happened to the debugging views?
The Nokia Mobile Browser 4.0 simulator is included with the Toolkit, but why aren't any handset SDKs included in the Toolkit 4.0 Starter Pack download?
Why do the handset SDKs have to be downloaded separately?
Which SDKs allow developers to view push messages?
Which SDKs allow developers to view an MMS message?
Does the Nokia Mobile Internet Toolkit support WAP 2.0 or WAP NG?
How can developers change the way an SDK connects to the Internet?
What is the Document Type Definition (DTD) Manager?
What SDKs support XHTML MP and CHTML?
What is the SMIL editor?
When should developers use an SMIL file in an MMS message?
Why does the Series 60 1.0.6 Content Authoring SDK ignore the SMIL file in MMS messages?
Why doesn't the Toolkit run on Linux?
How do developers send a push message to the Nokia Mobile Browser 4.0 simulator from an external application?
What causes the "More than maximum number of redirections has happened" error message when developers try to visit a particular WAP site?
How can developers show the Euro (€) symbol on a WML card?
Why don't any of the SDKs downloaded for previous versions of the Toolkit work?
What is the Nokia Mobile Browser 4.0 simulator?
How do developers input text and numbers using the Nokia Mobile Browser 4.0 simulator?
What character encoding is supported in the Toolkit?
How can developers stop the content in their ASP-driven application from caching and not displaying their dynamically generated content?
What is the difference between a Service Indication and a Service Loading push message?
Why did version 3.1 of the Toolkit expire? Why do developers have to upgrade to version 4.0? Why is there an expiration date on the Toolkit?
How is WMLScript used with an XHTML Mobile Profile file?

• What is the Nokia Mobile Internet Toolkit Starter Pack? What are the other Toolkit downloads?

• In version 4.0 of its award-winning set of content-authoring tools, Nokia separated the Nokia Mobile Internet Toolkit into three products to better fulfill user needs and to allow for speedier updates in future releases. The Nokia WAP Gateway Simulator and the Nokia Mobile Browser Simulator are now separate products that can be downloaded and installed on a PC and used either independently or in conjunction with the Nokia Mobile Internet Toolkit 4.0. The Starter Pack includes all of the different tools that used to be shipped under the Nokia Mobile Internet Toolkit name.

• How can developers send content to more than one SDK at a time?

• The SDK Control Panel will show developers all of the compatible Nokia SDKs they have installed on their system and, when applicable, the currently running instances of each one. Developers can use the SDK Control Panel to select which SDKs they want to send the file they are editing to and even start new instances.

• Why are developers no longer able to connect to remote sites?

• Most likely this is because they are relying on the Nokia WAP Gateway Simulator for their WAP Gateway connection and have not started it yet. In previous versions of the Toolkit, the WAP Gateway Simulator was started automatically. In version 4.0 of the Toolkit, the WAP Gateway Simulator must be started manually. The advantage of this method is that the WAP Gateway Simulator is only running when developers need it to be running (and not needlessly using system resources); also, they can use it with an SDK when they do not have the Toolkit running, e.g., during demonstrations or when working with other tools.

• What is the Update Manager? How does it work?

• The Update Manager is an additional utility provided with many Nokia tools that allows developers to automatically check the available tools and SDKs on the Forum Nokia Web site and compare them to the tools and SDKs they have installed on their system. By launching the Update Manager, they will see all of the products they have installed, whether or not there are any new versions available, and if there are any additional SDKs that work with the tools installed. If developers find a new tool they want, they can quickly download it from the Update Manager.

• What happened to the debugging views?

• The debugging views that were available in previous versions of the Toolkit (such as current, session, cookies, etc.) have been removed from this version and are available as part of each SDK. This was done to support multiple SDK content previewing and to allow them to be customized for each SDK's capabilities. To get this information for an SDK, developers should select "Diagnostics" from their menu system. Note: The Nokia 7210, Nokia 3510i, and Series 60 1.0.6 SDKs do not yet have Diagnostics as an option.

• The Nokia Mobile Browser 4.0 simulator is included with the Toolkit, but why aren't any handset SDKs included in the Toolkit 4.0 Starter Pack download?

• Handset SDKs for the Toolkit are now separate downloads, which enables users to have as few or as many SDKs as they like. This also allows additional handset SDKs to be released, downloaded, and installed as they become available, without making developers download and reinstall the entire Toolkit application. Additionally, users no longer have to wait for a new version of the Toolkit to be released in order to have access to the latest available handset SDKs.

• Why do the handset SDKs have to be downloaded separately?

• Handset SDKs for the Nokia Mobile Internet Toolkit are now separate downloads so that users can have as few or as many SDKs as they like. This also allows additional SDKs that are released to be easily downloaded and installed without making developers download and reinstall the entire Toolkit application. Additionally, SDKs can now be used as stand-alone applications without the Toolkit.

• Which SDKs allow developers to view push messages?

• Push messages can be viewed using the Nokia Mobile Browser 4.0 simulator and the Nokia 7210, Nokia 3510i, and Nokia 5100 SDKs (available via separate download). Note: The WAP Gateway Simulator must be running for push messages to be received by the Nokia 7210 and Nokia 3510i SDKs.

• Which SDKs allow developers to view an MMS message?

• MMS messages can be viewed using the Nokia 7210, Nokia 3510i, Nokia 5100, and Series 60 1.0.6 SDKs (available via separate download).

• Does the Nokia Mobile Internet Toolkit support WAP 2.0 or WAP NG?

• The Toolkit is WAP 2.0 compliant. The Nokia Mobile Browser 4.0 simulator supports the markup language specifications of WAP 2.0, as does the Nokia 5100 SDK (available via separate download).

• How can developers change the way an SDK connects to the Internet?

• Developers can change the connection method for each SDK in its Device Settings. They can use the included WAP Gateway Simulator (default settings) or enter the IP address and port number for an external WAP Gateway. Some device SDKs, such as the Nokia Mobile Browser 4.0 simulator, will also let developers change the connection type.

• What is the Document Type Definition (DTD) Manager?

• The DTD Manager is a utility that can be used to import DTDs into the Toolkit. Once a DTD has been imported, developers can use it in the Toolkit editors to author, edit, and validate files.

• What SDKs support XHTML MP and CHTML?

• The Nokia 5100 SDK supports both XHTML Mobile Profile and CHTML markup languages.

• What is the SMIL editor?

• SMIL is a presentation language that is used in MMS. Developers can use the SMIL editor to specify the presentation of attachments in an MMS message, and then attach that SMIL file when authoring an MMS file.

• When should developers use an SMIL file in an MMS message?

• SMIL can only help with the presentation of other attachments in the MMS message. Thus, if developers do not want to control the presentation and simply want each attachment displayed in the order in which they were added to the MMS message, there is no need to use SMIL. However, if they want to change the order of the attachments or combine multiple attachments in one "slide" (such as a .txt file and a .gif file), then they must use SMIL. Some Nokia phones, such as the Nokia 7210 and Nokia 3510i, do not support SMIL. When one of these phones (or phone SDKs) receives an MMS message that includes an SMIL file, the user will be shown a message such as "default1.smil Object format not supported." The rest of the attachments will then be shown in the order in which they were arranged in the MMS message.

• Why does the Series 60 1.0.6 Content Authoring SDK ignore the SMIL file in MMS messages?

• The first two lines of the SMIL file (the xml declaration and the doctype) must be removed so that the first code within the SMIL file is the smil xmlns line. If these two elements are not removed, the Series 60 1.0.6 Content Authoring SDK will not use the SMIL file for the presentation of the attachments in the MMS message (although all of the attachments will still be visible).

• Why doesn't the Toolkit run on Linux?

• Currently the Toolkit is only supported on Windows 2000 and Windows XP operating systems. Although the majority of the Toolkit is written in the Java™ programming language, there are certain components written in native languages that prevent Nokia from providing a version for alternate operating systems at this time.

• How do developers send a push message to the Nokia Mobile Browser 4.0 simulator from an external application?

• The Nokia Mobile Browser 4.0 always listens for incoming push messages on UDP port 2948, the port specified in the WAP specifications for receiving push messages. If developers have a push gateway, they need to specify the client address of the host running the Toolkit in the control section of the PAP message they send to the push gateway. If they are using the Nokia Push Gateway API, they will specify this as an argument to the push() method. Other gateways may have libraries to help write push initiators that generate PAP messages. If developers don't have a push gateway, they need to write a push initiator that encodes the push message, and then transmits the message over a WAP stack to the Toolkit. This push initiator would typically be linked to server-side stack and encoder code to do this. The Toolkit will accept WAP-encoded SI, SL, CO, and multipart messages received at its push listening port.

• What causes the "More than maximum number of redirections has happened" error message when developers try to visit a particular WAP site?

• There is a WAP conformance requirement that the maximum number of redirects is limited to five and the site the developer was trying to access went over that limit. Because the Toolkit complies with conformance standards, it is required to stop and issue a warning to users once the limit has been exceeded.

• How can developers show the Euro (€) symbol on a WML card?

• They should use € in your WML code.

• Why don't any of the SDKs downloaded for previous versions of the Toolkit work?

• The Nokia 6210, Nokia 7110, Nokia 3330/3390, Nokia 8310, and Nokia 6590 SDKs that are compatible with the Nokia Mobile Internet Toolkit 3.1 have been retired and will not work with version 4.0. Instead, developers should use the Nokia 7210, Nokia 3510i, Nokia 5100, Series 60, and forthcoming SDKs.

• What is the Nokia Mobile Browser 4.0 simulator?

• The Nokia Mobile Browser 4.0 simulator is a reference implementation of Nokia's latest mobile Internet browser. The Nokia Mobile Browser 4.0 is WAP 2.0 compliant, natively supporting XHTML Mobile Profile, WAP CSS, and WML 1.x, as well as GIF image types and color.

• How do developers input text and numbers using the Nokia Mobile Browser 4.0 simulator?

• Although there is no keypad for this simulator, developers can input text using their PC keyboard.

• What character encoding is supported in the Toolkit?

• Supported encoding formats in text editors include Unicode (UTF-8 and UTF-16), ISO-8859-1 through ISO-8859-9, Chinese (GBK and Big5), and Japanese (SHIFT_JIS).

• How can developers stop the content in their ASP-driven application from caching and not displaying their dynamically generated content?

• They can use the Response.ExpiresAbsolute property to achieve immediate expiration of a file, or they can use a negative number for the Expires property.

• What is the difference between a Service Indication and a Service Loading push message?

• Service Indication messages only send an alert that a document is available for downloading, while Service Loading messages may interrupt other activities and force a message to be fetched automatically from the assigned server and then displayed in the browser.

• Why did version 3.1 of the Toolkit expire? Why do developers have to upgrade to version 4.0? Why is there an expiration date on the Toolkit?

• The Toolkit is a free product that Nokia provides to mobile Internet application developers. In order to ensure that users are working with the latest and most accurate technologies and simulations and to optimize Nokia's product and customer support, users must upgrade to the latest version of the Toolkit once their current version expires. All mobile Internet applications that worked with previous versions should work with version 4.0, and if developers have any difficulties or questions they can receive support from Nokia and their peers on the Forum Nokia Discussion Boards. Anyone installing an expired version of the Toolkit will have a 30-day grace period to upgrade to the latest version. Toolkit versions prior to 4.0 are no longer available from Forum Nokia.

• How is WMLScript used with an XHTML Mobile Profile file?

• WMLScript cannot be called directly from an XHTML Mobile Profile file. However, developers can call a WML file from an XHTML Mobile Profile file and that WML file can then call WMLScript. Here is an example of how to trigger an alert using the WMLScript Dialog Library:

  --------------dialog.xhtml---------------
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN"
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Dialog</title>
</head>
<body>
<h1>WMLScript Dialog from XHTML-MP File</h1>
<p>
When I select <a href="dialog.wml#go">this link</a>, I will see a WMLScript alert dialog.
</p>
</body>
</html>
--------------dialog.wml------------------
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="go" title="go">
<!-- Card never visible to user -->
<onevent type='onenterforward'>
<go href="dialog.wmls#displayalert()"/>
</onevent>
</card>
</wml>
--------------dialog.wmls-----------------
extern function displayalert()
{
Dialogs.alert("Look, it's an alert");
WMLBrowser.refresh();
WMLBrowser.go("dialog.xhtml");
}
-------------------------------------------


Rate This