Archived Talk:Optimize HERE Map Type Selector for Asha 305, Asha 306 and Asha 311
Hamishwillee - This is not the recommended implementation
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.
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)
- Replace these texts with pictures which are touchable icons.
06:39, 2 August 2012 (EEST)