This week’s featured article in Nokia Asha category is Handling multitouch in Java ME by jappit.
This article explains how to handle multitouch interactions in Java ME, by using the Nokia UI API.
The Nokia UI API offers multiple features useful to enhance functionality and user experience of a Java app. Those features include full support for multitouch interactions, that are supported on Series 40 Touch UI devices.
This article illustrates with a code example, how these features can be used to handle multiple touches, and how those touches can be displayed on screen or used to perform specific tasks within a Java app.
This week’s featured article in Windows Phone category is Adding multilingual support to your Windows Phone application using the Multilingual App Toolkit by PedroQ.
This article explains how to localize your Windows Phone application using the Multilingual App Toolkit. It allows you to easily localize your app, either by yourself or by using Microsoft Translator. You can also easily share the translation files with someone and then import them into your project.
Read this article and localize your Windows Phone applications.
Hola a todos! Continuamos la serie de artículos sobre el SDK de trabajo con imágenes publicado por Nokia. Si te perdiste los anteriores, puedes verlos aquí: Nokia Imaging SDK 1: Introducción Nokia Imaging SDK 2: Editando imágenes Nokia Imaging SDK 3: Aplicando filtros a imágenes. En este segundo artículo vamos a empezar a trabajar con imágenes. Este SDK nos facilita la edición de las mismas, permitiéndonos rotar y recortar nuestras…(read more)
Let me start by saying that by reading this you’ve already wasted too much time thinking about this question.
In theory it’s a simple decision.
If you have dynamic content that it would be useful to display on a wide live tile then you should include one.
If you don’t then you shouldn’t.
i.e. Don’t include a wide tile if it’s just a static logo.
So why even discuss this?
Well, most of the
Whether it directly relates to the content of an app or just from an about page, lots of apps contain links to Twitter that are opened in the web browser (IE).
Unfortunately, lots of apps do this wrong!
“Wrong? Really? What do you mean?” – I hear you ask.
Well, they don’t do it in the quickest, simplest, and cheapest (in terms of network data costs) way.
A few weeks ago I created some nuget packages to make it easier to work with the WMAppManifestFile, so you don’t have to manually edit it.
Since then I’ve realized that to indicate that you want an app to use more memory if available or to require that your app must have more memory to run (and therefore can’t run on low memory devices) also requires manually editing the WMAppManifest.xml file.