Coloured Debug Output on BlackBerry
While working on a project that involved lots of time sensitive heuristics that prevented stepping through the code I got frustrated with having to search for my debug output hidden amongst the Rim VM messages:
While working on a project that involved lots of time sensitive heuristics that prevented stepping through the code I got frustrated with having to search for my debug output hidden amongst the Rim VM messages:
Find Your MP is a BlackBerry application for UK users that allows you to query the TheyWorkForYou.com database and find out information about MPs based on postcode, name and consituency. The MP detail screen shows what party the MP belongs to and any positions they’ve held over various parliament sessions.
Realised today that I’m 32 and have never coded the Mandlebrot Set.
Current project, making the BlackBerry look more stylish, one app at a time.
I had some discussion on Twitter this week about the secret connection string that allows BlackBerry applications to use Rim’s BIS-B transport for network connections – I couldn’t put my point across in a tweet so here’s the gist.
NordvästLibrary is a growing collection of components you can use in your BlackBerry applications. There are two versions of the library; one for pre-OS5.0 API and another for post-OS5.0 API.
I’m working on a project that’s going to be using the 5.0 api so sat down this weekend and wrapped up the screen transition logic into a nice simple class (as suggested here).
The BlackBerry API for OS 5.0 (beta) introduces the ability to use slick screen transitions (Viigo has had this for a while) but for some reason both examples from Rim use needlessly complex logic that is guaranteed to confuse newer BlackBerry developers, below is a very simple application that doesn’t make use of Runnable/Threads.
I’ve been working on-site with a client who has a problem with a BlackBerry application that only appears on hardware and not in the simulator. Trying to find the cause of the issue meant we had to create multiple test applications to narrow it down, this also meant we had to repeatedly load the app onto a device which was taking around five minutes each time, luckily I remembered a little trick an old colleague showed me that I’ve not used for a while.