Monday September 15, 2008 Fast 3D Graphics with Java ME technology
|
A lot of developers don't realize how fast you can get 3-D graphics to blaze on a cell phone using Java ME technology. The frames-per-second on some devices, like Sony Ericsson phones, are pretty impressive. See: Fast Frames-Per-Second with Java ME When thinking of programming the next cool mobile 3-D app, think of programming it in Java ME technology if you want something fast and portable. |
Hinkmond
Post a Comment:
Comments are closed for this entry.
Theme originally based on design by Bryan Bell
There is no 3D in this game at all, it's just standard 2D plane collision.
Android supports OpenGL, though, and the SDK shows some pretty impressive demos.
Posted by Lars on September 17, 2008 at 10:57 AM PDT #
Hi Lars,
If you play the YouTube video, you'll note that at timestamp 0:20 to 0:23 the developer mentions JSR 184 is being used for their flexible graphics engine of the app being demo'd. JSR 184 is the Mobile 3D Graphics API for Java ME.
So, this is 3D graphics in the YouTube video.
Android SDK shows pretty impressive demos on a desktop or laptop PC. If an actual Android cell phone does come out in October (slipped their dates multiple times now), it will not be as impressive as on their SDK on a PC.
Hinkmond
Posted by Hinkmond Wong on September 17, 2008 at 12:55 PM PDT #
Actually no, Android never slipped and has always been targetted for 2008 (it was rumored for 2009 several times actually).
Fair point about Android on emulators, we'll see.
Still, I'm puzzled by your hostility toward Android.
Granted, it's not Java ME, but it's Java. And on top of that, your CEO publicly endorsed and congratulated the project a few months ago on his blog, so Sun is very supportive of Android.
Why are you disagreeing so strongly with your employer on this subject?
Posted by Stefan on September 17, 2008 at 08:16 PM PDT #
Hi Stefan,
Oh, I'm just kidding around! :-) I'm just pushing some buttons here. When anyone complains about Java ME technology, it's easy to blame Java ME technology itself (for fragmentation, differences from device to device, ease of distribution of 3rd party apps, etc.) But, in reality, it's not that simple to blame Java ME itself and say that something like iPhone or Android can do better.
The Wireless Industry including carriers, OEMs, and software vendors is a complicated system with problems that have no easy answers. Sometimes it's easy to think it all can be solved with this new thing or that new thing or by just waving our hands. Hype around that is bad for the average mobile software developer who might not be seeing past the marketing and the hype. Introducing a dose of reality is always a good thing to see a complex issue from all perspectives, not just the hype side.
So, take what I say with a grain of salt (since, don't forget that I do work in the Java ME technology group specifically here at Sun)--my full disclosure that I never hide.
And, I do support the idea that if we all evolve Java ME technology, instead of trying to supplant it with something else, it solves the issues of software development for the Wireless Industry more efficiently, directly, and with less hyperbole from the great "savior" technologies out there (I like that part especially :) ).
Hinkmond
Posted by Hinkmond Wong on September 18, 2008 at 09:12 AM PDT #