J2ME distribution, WTH

April 26th, 2009

I can not find a good “market/iTunes-shop” equivalent for J2ME.

Guess I’m gonna go give it away at the mobileprocessing showcase website.
And upload it here masterbeater2000-midlet-source and the jar file for download onto your computer directly!

And here is the executable jar file for download on your phone : Download

Ofcourse I will have no stats on this!

Status of the Android Install three days later.

April 25th, 2009

The developer console on android marketplace lets you se how many ppl have downloaded and installed you program and how many that still have it installed. You can also se how many stars the program has got and how many comments you have.

so far there are 20 votes (or comments, I dont know)
2218 downloads and 1107 are still installed (making it 49%)

Pretty OK I think.

Submitted to the Android market-place

April 23rd, 2009

I’ve submitted to the Android-marketplace. Or I hope so, I did not get any confirmation. Anyways here is the “marketing”-text i wrote

“Master Beater 2000 is a vibronome. A vibronome is a vibrating metronome, instead of audible clicks like a normal metronome a vibronome vibrates. This will make you feel the rhythm better and it is more stealthy. For more information please surf to http://www.shuriken.se/masterbeater2000/”

Updates

April 23rd, 2009

I know I’ve been quite on the blog-front, sorry.

My graphics-savvy friend created graphics for me.  I intend to use them for another project, they where way too good for this. So I’ve created an icon and in-metronome graphics myself.

I’ve made a few updates to the Andriod version.
* Added a scrollbar
* Made it remember your BPM when switching screenmodes
* Changed the icon
* Signed it for publishing on android market.
* Almost made my G1 talk to my mac again…. almost.

For the iPhone version I’ve gotten all the things I need to test it on device, but both me and my friend that has an iPhone have been bisy on opposite times.  So no testing on device. I plan to make the same adjustments on the iPhone application as on the Android application though, tonight or tomorrow, so that when we’ve tested it on device all you have to do is to upload it to iTunes.

As for the j2me version, a little graphical updates, that is all that is left.

Oh yeah, one more bad thing with android developement. When signing appications you need the JDK, but everything else you can use the JSR for. 115MB additional download. Ohh, and the documentation on how to preserve data when changing screenmode (Android kills the program and start’s it again) was way to hard to find. And one last thing why do you have to press Ctrl-F11 to switch screenmodes in the emulator? Maybe that’s why so many program’s crash when you flip your keyboard out.

iPhone 03

April 16th, 2009

Yeah, ah-ha, that went smooth. A thread that controls the left to right bopping image is done. Very easy. Now all that has to be done is to test it on device.

iPhone 02

April 16th, 2009

Sorry for not posting here for a while. I have been busy with easter (putting LED’s in egg’s) and back at my day-job we’ve had our freedom day’s.
Freedom is a fun thing we do, where we can do (almost) what we want for a few day’s between the dot releases of our product.

Apologies aside. I have had some progress, all that is left on the iPhone side is to test on hardware and make the thread that vibrates and moves the visual aid (the one I could not get to work on Android) and test it on hardware.

I have also asked a friend with better graphical skills then me to create that previously named graphical asset and an icon for the program on the different platforms.

After that “all” I have to do is write the manual and start distributing the program. I have a tendency to only blog about shit that doesn’t work or annoys me. I’m thinking that that this part of the project will spawn a few more blog-posts then the rather pleasant Mobile Processing and Xcode development phase!

iPhone 01

April 11th, 2009

I’ve been using Xcode a few years now, mainly for compiling vst programs on os x, also some small commandline utilitie but no cocoa. And iPhone development is Cocoa, so I’ve been watching me some video tutorials, and so far I’ve done the exact same UI It took me oh so long to create in eclipse.

I dont think I will create a landscape mode though, seems to be a bit overkill.

When I on eclipse was fighting with the development enviroment, I’m here more fighting with myself learning objective-c. It is good fighting.

Eclipse 05 (the one with a screenshot)

April 8th, 2009

Threads on Android are very shaky. I could not get a steady update so that graphics could be shown in sync with the vibrating, thus I removed all moving graphics.

I made an inventory of other metronome applications on the Android and they suffer from not being exact. But the vibrating is proper (unless you go to landscape from portrait)

Anyway’s I’ve promised a screenshot, so here it is:

Screenshot of MasterBeater2000 on Android

Eclipse session 04

April 8th, 2009

The end is near!

There is no synchronizing visuality and a thread. At least not in the emulator. The Threads seem to be wanting to go at a different speed.

I’ll try some more and on device before I call it quits.

Eclipse-session 03a and 03b

April 6th, 2009

I’ve tried to get the mac to accpet the android dev phone again. to no avail. Seems like one of the crashes made OS X blacklist the phone. I’ve must have spent 3 hours on this atleast. So short of reinstalling OS X I cant se any solution to that particular problem. And I’m not eager to reinstall the whole OS right now.

I’ve also tried Eclipse on my work-pc, just to se if it sucked as hard there. It did not! Perhaps I’m more tolerant to bad programs in a windows enviroment or the fact that I had a phone to debug on made the whole difference.

Programming-wise I’ve managed to get the vibrator to work as it should, the synchronisation between vibrator and UI will probably be hard or impossible to obtain. The vibrator API has 2 functions for starting the vibrator. The first one makes one able to call with a specified ms value of how long the vibrator should vibrate. This function does not work especially good if you want to call it regularly which is why I guess they have made the vibrate(pattern,loop) function.  This works a lot better (the vibrator doesent freak out) but it does not start right away, and when moving from portrait to landscape there is a distinct pause. Not something you would like to do live.

As for the graphics, seems like I have to create a custom view or widget to get it to update with any sort of reliability.

Soon there will be a video!