In
Part 2 of this series
I had finally managed to get the primary scene ground objects into place. Since then, I’ve made some reasonable progress on the game. The following demo shows some of the initial collision detection working.
Read more…
As I’ve continued hiring at
mFoundry
(if you live in the Bay Area,
check us out
), I’ve been very busy non-coding. As usual, that implies the need for a non-work programming project. As I mentioned
in my last post
, I’ve started digging into Android programming. I decided it would be interesting to try to do a game of some sort. Given that I have zero skill with graphics, I had to cheat a bit. I’m attempting to build an Android version of the
Pingus
game using the graphics and levels from their source code and the very cool Android game engine
AndEngine
.
Read more…
In my previous entries , I’ve discussed a few things that caught me off guard while learning iPhone development. In the last couple of weeks, I’ve picked up an Android device to dig into that platform a bit and probably will spend less time playing with iPhone development. Before I move too far away from iPhone, I wanted to wrap up the remaining differences I found interesting between the iPhone and Java platforms.
I’m continuing to make slow forward progress with my DAAP-based music player for the iPhone. My most recent changes have taken this in the direction of being much more like the standard music player functionality on the iPhone. In particular, I’ve switched over to using a tab view controller for the major perspectives of viewing the music database.
Given Motorola’s push into the Android space , it comes as no surprise that they are trimming down the number of developers on the Eclipse Mobile Tools for Java project. MTJ project lead, Christian Kurzke, announced via the mailing list that three of the key “Motorola sponsored” developers have been reassigned to a different project and will no longer be sponsored to develop the Eclipse MTJ features. The good news is that Gustavo, Diego and David have expressed interest in continuing to be involved as individual contributors. In addition, Jon Deardon from Research In Motion will most likely be joining the list of official contributors very soon.
As Christian pointed out via his email, now would be an excellent time to consider getting involved in the Eclipse MTJ project. Even something as simple as being involved on the mailing list can help us out. If you are a mobile developer using Eclipse Mobile Tools for Java, consider contributing a patch to provide a cool new feature or to fix the bug that annoys you the most. Not a developer, but still want to contribute? We can always use help with documentation and project marketing. Pitch in and lend a hand!
In my last post , I was pretty negative about the available BlackBerry user interface controls. While that fact hasn’t changed, I didn’t want to leave the impression that the BlackBerry API’s provide nothing to developers. The API’s provide lots of interesting functions including the ability to extend menus within other applications. Take a look at the following from the default messaging application on a 4.5 device.
Before Facebook Installation
This shows the menu in this application before installing the Facebook application. After installation, you can see that the Facebook application has added a new menu item to this application.
After Facebook Installation
This is a pretty nice feature of the API. Although I don’t have actual code to show for this, my assumption is that this is provided by using:
API’s like this allow for incredible integration with the rest of the applications on the device, opening up many very interesting opportunities.
I continue to be impressed with the build quality and overall polish of the BlackBerry Bold as an end-user device… at least for basic functionality. While some may not like the way BlackBerry push email works, I find it to be pretty nice.
As a developer, I’m much more disappointed developing using the BlackBerry native API than I expected I would be when I started playing with my little ZBerry project. Marcus Watkins offers excellent insight into the world of BlackBerry development , which I won’t try to rehash here. The part that I find incredibly frustrating is the lack of decent reusable user interface controls. As Marcus details in his blog post, the provided UI functionality has the bland look and feel of the base operating system. Even more frustrating to me is how little flexibility there is even within the standard controls. For instance, I wanted to provide the user the ability to customize the font used in the text display. Using the standard functionality yields the following dialog. Read more…
The Eclipse Project has released version 3.5 of the Eclipse platform as part of the Galileo Release Train. There are announcements and discussions all over the place, like here , here and here . The question is where is the love for the Mobile Tools for Java ? The Galileo release marks the graduation of the Mobile Tools for Java project from incubation, providing a solid set of tools for JavaME development in Eclipse. The involvement from the various member companies has been excellent during the development of MTJ and transition from EclipseME. I have to admit that I’m a bit disappointed at the lack of coverage of the release. Pass the word that MTJ is the way to develop for JavaME.
The Pulsar project also saw an initial early release with Galileo. I will provide some background on this project in an upcoming post.
I’ve decided to dub this little hobby project ZBerry (BlackBerry Z-Machine Interpreter). I made some progress this weekend allowing stories to be selected from the file system via a new “library” view.
ZBerry Library Selection
I need to add some suspend/resume support before this thing becomes really very usable on a phone, but some progress anyway…
I was recently struggling to understand how to text alignment works with the BlackBerry Graphics drawText function. Having developed for MIDP on JavaME for a number of years, I found that the way the BlackBerry API works is a bit counter-intuitive until you understand how it works. I expected that this code would work, based on JavaME: