The Artima Developer Community
Articles | News | Weblogs | Books | Forums
Artima Forums | Articles | Weblogs | Java Answers | News
Sponsored Link •

Java Buzz Forum
J2mE Optimizations II

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Fred Grott

Posts: 4361
Nickname: shareme
Registered: Jan, 2003

Fred Grott is Lead Developer-CEO of ShareMe Technologies LLC -The Mobile Future
J2mE Optimizations II Posted: Dec 7, 2006 8:02 AM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Fred Grott.
Original Post: J2mE Optimizations II
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology. 		Latest Java Buzz Posts
Latest Java Buzz Posts by Fred Grott
Latest Posts From ShareMe Technologies LLC-The Mobile Future

Advertisement
I have been re-reading the Kronos-CLEF document. There is a common lite profile using fixed point math and that is hardware based in OpenGL ES 1.0(?) and of course we have full floating point support in OpenGL ES 1.1 and beyond.

So what does hard based mean in our J2me context even though we do not have exposure of the OpenGL ES apis in J2me except on jsr 184? Hardware based in this context referrers to using such techniques as shits for ES. In MIDP 2.0 we have a mixture of device both having jsr 184 and not having cldc 1.1 floating point and not.

That means by using javaolution to modify how collections and strings are used and certain fixed point math techniques yo can target the largest amount of the MIDP 2.0 handset audience with any mobile operator with a low level 3d game. On the non jsr 184 MIDP 2.0 handsets we gain speed from using modified collection classes(javaolution) and fixed point(shift operations). On jsr 184 MIDP 2.0 devices we gain further speed increases without using the complex stuff as from jsr 184 as of yet.

Interesting..as we do not have to worry about the optional apis too much we can target most MIDP 2.0 device..

Read: J2mE Optimizations II

Topic: [Dec 4, 2006 07:19 PST] 14 Links Previous Topic   Next Topic Topic: PeopleOverProcess.com: IBM SWG: Social Software
Sponsored Links


Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use