Tools

Namespaces

Variants

Views

Actions

Search

Contents

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Comments

Hamishwillee - This is not the recommended implementation

Hi r60600

As I understand it the problem faced is that "The Type selector control from the Nokia Map API for Web is designed for a wider screen than a typical web widget". The problem version of the API you're talking about is an old version, and your solution is to replace it with another out-of-date old version of the api which appears a bit better.

That doesn't make sense to me. In general we'd recommend that anyone who wants to use maps on a Java ME device use the "Maps API for Java", rather than trying to get the web API work through the browser - for a start, as far as I know you'd get offline maps, and a framework designed to work on the device.

Please look closely at the English - I don't understand the first sentences.

Regards

Hamish

hamishwillee
07:47, 30 July 2012 (EEST)

Hamishwillee - Suggestions for improvement

Suggestion from our technical expert is that the following applies to an implmentation that is "optimised for touch":

Unwrapped Texts do not display well on a small screen

If you resize the screen then the USER has to scroll too much. = Poor UI

Much better to use icons – touchable and meaningful

Do not keep them displayed over the MapCanvas when not required. Screen is too small.

Suggestion is that you use icons instead like the Java Me IconCommandBar - so you could rewrite this example:

Write a custom MapCompoment extending the TypeSelector component. (This has been done with the Tabbed InfoBubble)

When the MapComponent is attached to map, do some JavaScript magic to retrieve the DOM element holding the texts “Street Map”, “Satellite” etc.

Replace these texts with pictures which are touchable icons.

There is then no need resize the screen, and the Web App is properly touchable.

This article uses a deprecated version of the Nokia Maps API for JavaScript to display a Map on a Java ME device. The Nokia Maps API for JavaScript is not considered to be an appropriate API to use in the Java ME environment, as a large JavaScript library would need to be regularly downloaded onto a memory constricted device, and un-cached Map tiles would need to be regularly requested which would result in a large amount of data traffic.

Nokia offers two alternative APIs which are more suitable for Java ME development

For a simple static map using the RESTful Maps API within a web widget is considered to be a reasonable lightweight solution.

Static mapping services do not cache or tile the images when requested, therefore each request involves a round trip to the server. If the map on a mobile application needs to be refreshed at any time, using a caching library will result in a reduction in network traffic after around three maps have been displayed. An explanation of this can be found here

Asha 305, Asha 306, Asha 311 are Series 40 devices with new full touch UI which will provide a better user experience for map operation. And developers may not construct ScaleBar and ZoomBar for user. But these devices only support HTML 4.0, Developers can only use Nokia Map API for Web to display map in Browser or Widget.

Because these 3 Asha devices's portrait screen width is less than width of horizontal extending TypeSelector. Maybe many developers don't think it's a question because user can rotate to landscape screen which has full width and is fit for 2 hands hold. But I think developers had better provide users another convenience way which let them operate map when only can use single hand.