Oct 172005

As I started playing with Motorola’s SDK, I realized there was little to no mention of a phonebook API. Some more poking around revealed that it was not present in the JARs associated with the emulator.


Turns out that the materials required to make use of this API are only available under NDA from Motorola. And for some random yahoo like me, that process is started by filling out a questionnaire on the Motorola developer site. And as of this writing, submitting that form yields a server error.


 Posted by at 3:19 am
Oct 152005

I’ve never cared for NetBeans. Historically it’s been slow, ugly, and the UI has been chock full of (what I found to be) unintuitive contrivances. With recent releases the speed has improved dramatically. The appearance has also improved; though there are still significant problems: notably a lack of antialiased fonts.

So why revisit it? Well, from what I’ve seen so far, the mobile application development support is very slick. And this 5.0 beta I’m playing with addresses some of the more glaring UI issues. The mobile application development support just might be enough for me to forgive NetBeans’ remaining flaws. After all, I use emacs normally; obviously I can live without antialiased fonts.

 Posted by at 6:38 am
Oct 152005

Okay… If I do this, I don’t want to create some application that lives in a totally different world from the standard phone book; even though it sucks, the standard phone book is too integrated with the overall function of the phone. It has to be leveraged for an enhanced phone/address book app to be any use to me.

The Bad News: MIDP 2.0 doesn’t appear to provide an API for accessing the phone book.

The Good News: Motorola provides an extension API that does.

This could actually happen.

 Posted by at 6:14 am