As one of the co authors, I’m really exited to announce that Quick Recipes on Symbian OS has just been released by Symbian Press. According to the official literature,
The book tells you how to start developing C++ applications for Symbian smartphones from scratch and includes recipes that are divided by technology, including graphics, multimedia, location-based services, networking and messaging. Each recipe explains the length of time needed to implement it, and its difficulty level. The task is then explained in detail, and provides snippets of example code. The full sample code is provided for future reference and for use as a starting point in your own projects.
Get a copy from Amazon here, while its hot baby 😉 While at it, have a look at the book’s WiKi page, where you’ll find the recepies(code examples) and the errata.
Smashing magazine has just posted an excellent article reviewing no less than 35 source code editors. Its good to see an article that finally collates the good ones under one roof. Personally, I use Notepad++, which gives you all the facility of UltraEdit(R) and EditPlus(R) for free (open source) and what’s great, its got an extensive collection of plug-ins and an active developer community. And yes, its written in C++ and fast.
The Carbide.c++ team at Nokia has just published a series of articles that explains the Carbide.c++ build system in-depth and how to get the most out of it. A recommended read for all developing software with Carbide.c++.
A colleague of mine recently popped down at my desk, asking me if there was an easy way to find the macros defined for a Symbian project build configuration. Given that a macro can originate form different places, its not always a easy guess. Of course you can look at the usual suspects, like the HRH file for the platform (\epoc32\include\variant\Symbian_OS_*.hrh) and the MMP file itself for the MACRO directive, but it won’t give you the full list, since the Symbian tool chain will insert its own on top. So how do you get it? Enter Carbide.c++ build configurations.
Ok here’s a bog standard piece of Symbian C++. What’s wrong? Hint, its all in the status…
if (KErrNone == iStatus.Int())
// OnProgressNotificitionL is
// a callback (void)(TNifProgress, TInt)
Still didn’t get it? Read on…
I usually have the Automatic Update services running in my home laptop, still running XP pro by the way. From time to time, it pops up, asking me if I’d like to install security updates and program patches, and being the good user that I am, accept what Microsoft deems best and just get along.
So when yesterday it asked me whether I wanted to install Windows Media player 11, to upgrade the version 10 already installed, I didn’t really think much, after all, I don’t even use that piece of bloatware, there’s way better solution for watching media, VLC and iTunes for music (I admit it may not be the best out there, but its convenient if you own an iPod) and I mean, an upgrade surely will be better, it will stop those patches coming in for media player 10, no?
Right after I agreed with the upgrade and a mammoth 25 megabyte download, (Why? Whatever happened to upgrading only the bits you need? Surely Microsoft hasn’t written the whole software from scratch? I guess Joel is right…) I get this:
WTF? Another 5 megabyte slapped on me on me and only the almighty know’s how many more patches to come! Whatever happened to shipping a new version of a product only when you are confident you can actually add value? What exactly is media player 11 adding that couldn’t have been delivered through patches in media player 10? Its being patched regularly for security holes anyway, how about updating for feature for a change?
Like the vast majority of users out there, I can’t count the number of times I’ve put faith in Microsoft software and got a very raw deal*. But the latest round of shenanigans have forced me to have got typing away again. Its just plain annoying.
P.S. Congratulations, Microsoft, thanks for providing an un-installation option at least, however, be sure to check the discussion at the bottom of the link for frustrated experiences of some users…
Happy new year to everyone! Even to you, the serial spammers, who keep on bombarding the blog with Viagra and P***** enlargement mails!
In the age of MP3s, sound quality is worse than ever.
At least, that seems to be the analysis at RollingStone. Here’s an article on Wikipedia with slightly more detailed technical analysis on the same subject.
While at it, curious readers might want to checkout Mp3Gain. I’ve found it quite useful over the years to normalize my mp3 collection.