Now this process isn’t 100% ideal. If you are an experienced developer you probably already know you need four key components.
- Rapc compiler
- Signature tool
- Simulator
- Javaloader
The first two components works fabulously in Linux. The second (signature tool) needs a kick in the pants to work (shame shame shame!).
The third is hit or miss when using Wine. So a less painful option is to put windows in a virtual machine and run the simulator there (more on that later).
And the fourth I just can’t get past. There is the barry project which has made impressive progress in the last few months and lists javaloader support as on the roadmap for milestone 4. RIM, if you have any sympathy for us non-windows users show these guys some love and send them some specs for heaven sakes!
This article presents the basics for compiling, signing, and debugging BlackBerry applications with Linux.
Continue Reading »
This was actually pretty trivial since the MDS simulator is pure Java, and a good portion of it is actually just Tomcat. Since Tomcat is not developed by RIM, the chances where pretty good that there where no hard coded backslash directory separators (no, I will never let that go)
MDS simulator log output
All you have to do is create a new script to replace the various batch files that ship with the MDS simulator. Here is the replacement for run.bat
#!/bin/bash
for i in classpath/* webserver/lib/*; do
MDS_CP=$i:${MDS_CP}
done
java -classpath ${MDS_CP} -Xmx512M -DKeystore.Password=password \
net.rim.application.ipproxyservice.IPProxyServiceApplication \
-log.console.dump
Don’t forget to set the execute permission:
chmod +x run.sh
To shutdown MDS, just hit <ctrl>+c in the terminal window to kill the process.
8800 Simulator in Wine/Linux
Call me crazy but I just can’t seem to accept that if you want to (or have to) write BlackBerry software you’re stuck with Windows. It bugs me.
There is good news and bad news regarding the simulator. The good news is with a recent version of Wine you can actually get the BlackBerry simulator to run. The bad news is that it’s a bit buggy, and debugging hardly works at all.
Continue Reading »
Being obsessive and all, I decided to sit down and figure out why the signature tool doesn’t seem to work in Linux. After all it’s a rather trivial Java application. I suspected from the start that the symptom was some sloppy programming on RIM’s part, hard coding Windows style path names and my suspicion was correct. After modifying two class files and reassembling SignatureTool.jar the signature tool worked like a charm!
I don’t know what the legality is regarding redistribution of RIM’s development tools, specifically ones that have been modified so what follows is a description of the steps required to modify SignatureTool.jar to work in a Unix style file system (forward slash for directory separators).
Continue Reading »
I received an email from Keith Neufeld (awesome electronics blog) about my Arduino LCD library with some tips on how to improve it. So over the weekend I dived in and did just that.
Specifically, this version removes the hard coded delays after each command is sent to the LCD and checks the LCD’s busy flag. This is a cleaner approach and should mean that the library works more reliably with various LCD modules (hopefully). The setup method has been cleaned up as well to make initialization by instruction just work without any hacks.
Of course, this does mean that the RW pin on the LCD must be connected to the Arduino instead of connecting to ground.
As before, see the Arduino LCD Library page to get the latest version of the code.
I’ve written a library for interfacing the Arduino with HD44780 based LCD modules. For now it lives here on my site, but if it’s popular enough it might need to move somewhere like the Arduino Playground.
Check out the Arduino LCD Library page for more details.
Here is a short video demonstrating an animation sample.
In this two part series I’m going to try my best to describe how I use Apache Ant and Eclipse to write/debug software for the BlackBerry platform.
Continue Reading »
So I’m watching High Fidelity and thought I would make a top 5 list of my own.
So top 5 dream jobs:
- Robot maker
- Prop maker for the movie industry
- Google Python developer
- Bar owner
- BlackBerry software developer
I don’t really want to be a BlackBerry developer but I had a hard time coming up with a 5th so I just put what I am currently doing (check out bbTv).
You know what I’m tired of? I’m sick of people in my MSN list having HUGE nick names. I come from a time when ICQ was the messenger and even then it was a cute little gimmick that people familiar with IRC laughed at. Regardless a nick name should be one to three words long at the most! None of these phrases a half a paragraph long telling a life story. Also, whoever thought of the “Buddy Icon” should be shot.
Well that’s not fair, it can be cool if you use something like Spider Man or Optimus Prime. But these people these days seem to want to use some picture of themselves smiling having fun with all their smiling friends. I don’t want to see you and your friends having fun. I want to see something clever and origional.
So with that said, I’m out. I’m not doing anything interesting these days so I should probably put “something” on this damn blog.

Ok, so you have an arcade joystick which you either built or bought but you really want to play some “Golden Tee” or “Marble Madness”. Well you could buy an arcade trackball already assembled, or if you are lucky enough to find one for cheap at a surplus store you can be a man and build one yourself.
Check out the Arcade Trackball page for details on how to connect a USB mouse to an arcade trackball. Your drunkin’, arcade gamin’, buddies will be super impressed.