The simulator skins tutorial was quite popular, 57 likes on the first day, wow! I finished up the rest of the skins mentioned in that post, and they can be found in the Vase API SVN. Here’s the current full list, and some screenshot samples:
BlackBerry Bold 9790
Creating a Device Simulator Skin for a QWERTY Symbian Device
Just a quick post to demonstrate listening for key presses on a physical device and determining the keycode generated by that keypress. This is a non-GUI Builder app, and will display the keycode values to the screen when keys are pressed, released, and long-pressed. It will also display gamefire key values. When running the app, to enable the exit button, press the game fire button to go to passthrough mode, then press it again to go back to monitor mode. Read more…
There’s been a growing interest within the Codename One discussion forums in contributing code to the Codename One project. I’m sure the guys would appreciate the help, since they are mainly two guys producing a pretty large free project. I recently made a small contribution, and I still have the configuration details fresh in my mind, so I thought I’d jot down some hints for others that might not want to go through the process of researching how to set up their environment. This blog posting will also help developers better debug and profile their Codename One based projects, regardless of contributions to the product.
Initially I will provide instructions for Eclipse, because that is what I use, but if there’s enough demand, I’ll write up an additional article for the Netbeans users… although, much of what you read here will be easy to translate to a Netbeans environment anyways.
Something to keep in mind before getting started, we will NOT be gaining any special privileges to the Subversion repository, these instructions will have you checking out code as an Anonymous user, and contributing the code to the Codename One developers (Shai and/or Chen) through the Codename One issue tracker. Read more…
I just want to share a tip that will make life much easier when dealing with webservices. Often, when developers need to debug webservice calls, they will start by blindly making API calls to inspect the headers and payload to determine what they are receiving from the webservice. There is a much easier way that does not involve modifying your code at all, nor is there a great deal of setup, it takes about 2 minutes total.
UPDATE @ 2012-04-12 – The Codename One guys have been busy! They introduced some new debugging tools built into the Simulator, thanks!