TamsS60 - the S60 Blog

A German web site called NokiaPort.de has uploaded the following image claiming it to be a fake:

I personally do not know how to classify it; as the folks at NokiaPort aren’t quite sure about what to do with it. However, the following things speak for the image’s authenticity:

The c button
The C button has a weird little distortion at the right side. This reminds me of my N71’s keys - the text on the keys eventually rubs off…especially on a prototype device!

Lens distortions
Looking at the black bottom rim, one can clearly see orange color abberations - this could well mean that we are looking at a real device.

As no similar Nokia device currently is on the market and the E65 is being sold off, it’s very probable that this is a real device. But - as said - no confirmation for now…

Fake or not? Please let us know!

Developers who read OpenSource code sometimes probably know the SDL - cutting a long story short, the SDL is a multimedia library that is intended for easy porting. Once SDL is ported to a new platform, porting SDL-based applications is very easy(if the rest of the code is portable).

Anyways, S60 developers are now in luck if the information on this web site is correct - the rather bold promise is as following:

S60 SDL is a Simple DirectMedia Layer adaptation for S60. SDL is a cross-platform multimedia library: Applications and libraries built on SDL can easily be ported to another operating systems. Usage of S60 SDL is not restricted to porting; S60 multimedia applications can be implemented without deep knowledge of Symbian C++ native API and a developer can use SDL and standard C interfaces. The SDL development supports both Nokia OpenC and Symbian stdlib (ESTLIB) C implementations.

With S60 SDL it is possible to port applications to S60 without a single code change. However S60 SDL has a special S60 API that makes integration to mobile platform easier. In practice S60 devices usually has a small screen and limited input posibilities, and CSDL interface helps to do adaptation without changes to the original code base.

The S60 SDL supports OpenGL ES development. Its possible to create SDL Surface for OpenGL ES content and manage that with SDL’s platform independent OpenGL API. In S60 devices that dont have hardware accelerated OpenGL, a software rendered is used automatically.

Anyone of you has further information? Please let us know!

Before we start this article: I am not an enemy of UIQ by any means. However, I come from the Palm OS side - and have seen platforms die before. For me, it looks like UIQ is going down - Palm OS Cobalt also looked beautiful on the draftboard!

UIQ Technology has recently released a new version of UIQ 3.3 - the basic tenor seems to be about hitting the mass market. It is said to be better compatible with Carrier’s certification process; and also brings along a consistent 5way navigation.

The company also hopes that this release will unite the “forks” between the versions UIQ 3.0(used by Sony Ericsson) and 3.1/3.2(used by Motorola) - UIQ 3.3 is said to be software-compatible with existing applications.

So far, so good. But who is left in the UIQ boat:
Motorola
Motorola currently offers two touchscreenless devices running UIQ - namely the now-dead Z8 and the Z10. A touchscreen device was rumored a few months ago, but was not heard from since. Things generally look dull inside of the big M; especially seeing that the company plans to split off its cellphone division.

Sony Ericsson
Sony Ericsson - once manufactured lovely cutting-edge UIQ phones. However, the current high-end models are starting to get old, and the Windows Mobile powered XPERIA is more-less round the corner.

The current UIQ lineup consists of consumer-centric devices that IMHO will not generate much third party software sales - developers should not expect much here.

Where do you think that UIQ is heading? Please let us know!