Eclipse-session 02

April 5th, 2009

I’ve decided to find the ppl responsible for Eclipse and render unplesanties upon them. To press build or run you have to press tre buttons, and then you have to move over to the mouse and choose the android setting.

Eclipse and the little program that talks to the emulator has once created zombie processes on this here os x machine, and once CRASHED/FREEZED this here apple laptop. How the fuck do they manage to do something that bad?

There has been some progress in all the suffering though. Threads are as easy as always in Java, I’ve updated the UI a little. A little more functionality has been made. But the thread cant update the UI yet and I have not been able to test it on an actual device.

That was to little progress for the time I’ve spent on it. Sometimes free software is not without cost.

Eclipse-session 01

April 2nd, 2009

So I began with the Android version tonight. Boy do I feel like punching someone in the face. Usability-wise there are so many faults I noticed tonight I wont even begin to list them all, I’ll only list a few.

First though, I’ve created a GUI for the application. you can now press buttons and watch text on the screen. There are still the tread to do, moving graphics, and better layout.

Now to the bitching:

  • Why cant you start your android project in the android emulator by default?
  • Why oh why does the emulator have to take 20% of my macbook’s CPU and start the fan?
  • Why have a wysiwyg editor if it doesent show what you are doing correctly? I was trying to change the size of a text, and the text did not change in size. but when I launched the application in the emulator. seriosly why cant that work?
  • The visual properties, navigating through them is the suck.  You cant go to them by typing (say for example “text”). Instead you start changing the current property. what the hell. Then when scrolling with mouse wheel or similar, don’t have your pointer in the left area, because the tool tips pop up, and then you’re not scrolling anymore.
  • Auto-completion-correction has a timer of what feels like an eternity before it pops up.

This has all made me in a foul mood. I’m going to solder something together and take a shower. Tomorrow I’ll read up on tutorials now that I know more where the trouble lay.

Prototyping in mobile processing

March 30th, 2009

This was a nice experience. Actually I reused something I created a while back, the embryo for this application. I no longer own a J2ME phone so it will be a bit hard to test, but I can probably borrow my wife’s phone.

Well it only took me the a few hours to do the embryo, and a little while to get a ball bouncing left and right  in speed of the metronome. It does need some designer love though.

A few drawbacks though, no debugging on device. Not that much in form of API’s. No animated gif loading. I dont really trust the threading to be exact, and there are a lot of devices to test on. which I wont do, of course.

But my stomache hurts and I’m tired.

Finding a vibrate function in the documentation.

March 28th, 2009

First I need to se if there is the possibility to access the vibrator, so I look in the documentation of the 3 development environments.

Mobile Processing, easey as pie,  documentation is really easy to navigate. Could be there arent much to document. The Emulator does not show vibration though.

iPhone, pretty easy, searching for vibrate gave the information that led me to finding what I needed. The Emulator does not show vibration either.

Android, why does eclipse take so long to start? It’s stupid. Did not find any link to the documentation, and it was a bit to hard to search in the html-documentation that I donwloaded. Google to the rescue. took a little longer to get it up and running then the other two, but the API-call seems to be able to do more. I had to add stuff in a manifest file to be allowed to use the vibrator. The program would crahs otherwise. Emulator does not show vibration either.

Installing and or updating

March 28th, 2009

So first steps are to get the SDK’s up and running.

Since I already have Xcode I had to update that, pretty easy, download from apple’s developer pages, and install the update. A pretty hefty download, but the process from there was smooth as silk.

Mobile processing for J2ME, I know this is a little like cheating but I want to go into coding as fast as possible and that is exactly what all the processing derivatives are for. Ease as pie, download, unzip and you’re up and running. You need to download and install a WTK as well, that also was painless.

Eclipse and the Android SDK then, well, it was a hefty download, and a few manual steps to reinstall. Honestly, what would be so wrong with making a proper installer?

Winner: iPhone SDK and Mobile Processing. Looser: Android SDK and Eclipse.

The mission

March 27th, 2009

I’m going to code and distributing a vibronome application on iPhone, Android and J2ME and document my learning experience for all aspect’s I’m going to hit. Like installation of enviroments, testing, distributing and if the revenue streams are the same.

So to the MasterBeater 2000, yes it’s a corny name, but a friend suggested it and it kind of stuck. I want it to be able to vibrate on every beat, like a metronome but without sound and instead vibrations.  I shall be possible to play/pause and change BPM. A visual representation prefferably in the shape of a ball smashed against sides.

That’s it for now. Next I’m going to install the SDK’s and document the differences.