This article presents a mechanism for using active objects for implementing message passing between (equal) threads. This is not a new idea by any standards, but having come across a working implementation for it some time ago, I found it elegant and useful enough to improve it further and present it here. Now, the explicit use of threads is often discouraged in Symbian, and even if they should be used, the client-server framework wrapped around the server thread is in most cases more than enough to provide inter-thread communication. However here I try to present a solution to a problem where there are 2 equal producer/consumer threads that require two-way communication not easily available via client-server framework.

When I started understanding ECom architecture of Symbian, I tried to map it with some design pattern from the GoF book. This way I found out that the Strategy Pattern described as one of the Behavioral Patterns is the closest match. Let me share my understanding with you.

When I started understanding Active Object framework in Symbian, it was difficult for me to grasp the idea how the front end UI is not frozen, in the event of long running task, even when we don't use multiple threads. But when i started understanding the active object framework in conjunction with the client-server architecture of symbian, I got the idea. I would like to share it with you.

If an application runs and performs all required task for the user or client, doesn’t means that it is complete in all the sense. Using performance analysis tools like profiler we can find out how our application is performing internally means in terms of speed, memory usage and power utilization. There are lots of issues which can reduce performance of your application; and here is a list of some of them

A short introduction to Symbian UIDs

This tutorial provides an insight to good programming practices and practices that can preferably avoided while programming in Symbian environment.

Early in 2007, Nokia announced the Web Runtime (WRT) technology as one of the great news for the S60 platform. This technology will be available with all S60 3rd. Edition Feature Pack 2 devices and allows development of applications (called widgets) for S60 smartphones using standard Web technologies such as: XHTML, CSS (Cascading Style Sheets) and JavaScript, besides bringing cutting-edge Web 2.0 applications to your device with the use of AJAX (Asynchronous JavaScript And XML).

In this article we'll introduce the Web Runtime technology, will show what's the importance of it for the quick and easy building of mobile applications, besides presenting the tools you'll need to develop widgets using WRT. We'll also build a simple example application to show you how the whole development cycle works.

Here is the list of CNTMODEL panics. These are not documented in my working SDK and may happen when you are dealing with contacts.