A colleague asked me today why on side-loading an example application for testing all the data previously saved in application’s isolated storage was lost. Is that normal? And if so, how can one still test use cases such as application updates, when it is important that data saved by the old version of the app remains accessible to the new application instance?
Well, it is normal. If you are using the Application Deployment tool (
XapDeploy.exe), that is .
We have updated the Asha design guidelines (minor edits to texts and graphics) and added some new material!
The Nokia Asha icon toolkit now includes templates for list and Category bar icons.
An all-new piece of the offering is the Nokia Asha UI Toolkit; a collection of realistic UI views and components that can be used to create mockups which are close to the final visual result. The toolkit contains drawing files representing LCDUI and LWUIT components for Nokia Asha.
The toolkit is available for Adobe Illustrator CS5 and Inkscape version 0.48 or above.
Go check them out!
When it comes to installing the Nokia Imaging SDK to your Windows Phone 8 projects, the easiest way is to use NuGet. Until today, you still had to complete the installation by manually editing your project file (.csproj), but thanks to the fantastic input of PedroQ, an active member of the SDK discussion board, the installation is now significantly simpler. Kudos PedroQ!
Windows Phone 8 provides a variety of ways of launching your application. They all pass a URI to the
RootFrame of the application. If you want to map the URI to another in order to customize the behaviour of the app depending on different launching scenarios, you can make a custom URI mapper class inherited from
UriMapperBase and then set the URI mapper to
In this post, we’ll list and group the URIs coming from the different methods of launching an application.
Do you have an Android app you would like to port to the new Nokia Asha software platform 1.0? If yes, then you will love the latest update to our porting library. The library compares platforms and gives information on development tools and portability of the application types.
I’ve recently run into some misunderstandings with developers regarding dialog interaction in Asha UI; I hope this post will help clarify things.
In my previous blog post I stated that backstepping is always done via the hardware back key and there mustn’t be software back or exit buttons on screens. This is completely true. However, when talking about dialogs, there is another aspect that needs to be considered.
Finally one of the things I personally (and I know loads of other developers) have been awaiting for ages has arrived.
Here at Nokia, we’ve had great maps with our devices for many years, but in general if you wanted to use maps in your own application, you had to code it in. And if you wanted it to do something really great, it often meant that you needed to have rather good programming skills. You could do simple routing with just few lines of code though, but implementing a real voice guided navigation was not a trivial task.
Would you like to test, how your Java ME enabled device supports audio mixing? In general, all the Series 40 devices since Series 40 5th Edition support it (and Symbian devices too), but Nokia Asha software platform 1.0 devices don’t support it.
This wiki article shows, how audio mixing is done in MIDlets. There is also a test MIDlet with source code included in the article.
Although LCDUI provides many ready-made components, some of the items you find in native apps are missing. LWUIT framework provides additional components, and also animations, but it’s still not guaranteed it would offer everything you need.
If you really want to impress your users, you may run into a situation where you need to customize your UI with your own components. Whether you are using Form-based CustomItem or Canvas-based CanvasGraphicsItem, creating customized components is fairly similar. You could even create a generic class that only implements painting the graphics of your component. Regardless of which approach you choose, porting from one to another is a trivial task. The selection between Form and Canvas is dictated by the overall UI you want to build.
To get you started, here are a few Wiki articles you might find interesting:
-Custom category bar
-Custom search bar
The easiest way of logging is to add
System.out.println() lines to your code. This can be useful in emulator environment, but in real devices something else is needed. One efficient way is to use Microlog logging library. It supports Java ME and Android and makes it possible to log to file, to PC via Bluetooth and also to servers online. Only couple of lines of code need to be added to the MIDlet source code.
Read more about logging with Microlog from Developer Nokia Wiki.