Come on, RIM

Ok, last time (and the first time) I wrote that I want to start with programming for the playbook. It won’t be something serious but in the end there should be a program I can be proud of and other people want to use it.

For my idea I need a textfield. To be more precise: I need a multiline textfield and users should be able to enter and edit text. And here is the problem: There is no native multiline textfield for the AIR API, there is no multiline textfield for the native sdk and with WebWorks you have a textfield but it is not really native. So when you want to write a AIR application for the playbook you can use the original AIR textfield (then you have to hack around it so the user gets the keyboard) or you have to use a extern community library.

So my question is what is this RIM? Do you want to get some developer for your device?? If so, where is the support? Oh man, I hope they get the right directions in the future, till then I have to use the community library…. and I hope the next time I can write about my progress and don’t have to rant.

I want to start BB Playbook programming

Yes, finally i decided to start developing for another platform than Mac OS X. This will be my little diary to tell about my highs and lows.

I want to clarify why someone wants to write code for the Playbook. At first it is something new to learn and to discover. Exciting! Then it is not like the iOS platform with thousands of developer out there so it is easier to get some publicity. Also there are more problems which are not solved yet that means you don’t have to do work other people had done already.

Now, after telling my reasons I want to give you some more thoughts I had about the whole case:

To develop for the Playbook you can choose between 3 and 1/2 ways to do it. 

  • You can write a webapp with HTML5 and JavaScript. Problem: You don’t have a native look and feel.
  • Or you can use the Native SDK (NDK). Problem: There are no GUI elements supported yet, but you can do all your stuff with OpenGL ES, Cocos2d, Lua-Scripting, etc. blah blub
  • The third way is to use Adobe AIR. Here you have native GUI elements and if you have enough money you can buy Flash Builder for a faster development.
  • At last you can write a Android app and use the Android runtime, but honestly this is not really developing for the Playbook…

I want to go the third way. Adobe AIR and a native look and feel. I don’t have Flash Builder and because the SDK installer didn’t work on my Mac I use my Win7 installation, Notepad++ and cmd.exe. ActionScript serves as programming language.