This time my post will be a short one. :)
You know, I've been thinking about writing some posts on various design patterns applied in Symbian OS core components. My motivation is first that I enjoy reading/using code that has been carefully and nicely designed. Second, I wanted (and I still do) to encourage each developer to always think before starting to implement any solution for a given task/problem. It may sound as a cliche, but I found it a very common pattern that people (i.e. developers) had not considered how others will use their module (niceness of interface, readability of source code, etc.), how it fits into the big picture, how future-proof it is, etc. You know, ideally you shouldn't just code something, but rather do it nicely. That's the difficult part.
Even though I found this idea pretty challenging I've kept postponing my first article on this topic for various reasons. Now I'm late - at least with the first article. :) I've just noticed that rensijie from NewLC.com had posted two article about design patterns:
- When Symbian met Design Patterns (1) -- State Pattern and
- When Symbian met Design Patterns (2) -- Proxy Pattern