To run the code as a midlet, one new class would need to be
written. I suspect any compotent Java developer could get
something working in a few days. The main problem is
performance. For example, when I run the code as an applet on
my PDA which has a 400MHz processor it takes about 45
seconds to display a black and white page. (Color takes
longer.) Scrolling takes about 10 seconds. Since most
documents require horizontal scrolling to read, it makes the
applet fairly useless for all but the most patient users. A midlet
would have the same performance...
A JVM that does JIT processing could be up to 5 times faster on
the same hardware. I also expect with further optimizing the
code could be made 50% faster. Also, CPU speeds double ever
one and a half years. If I were to buy my PDA today, it would
run at 633MHz for the same price. So, performance is not a
perminent problem but it is a temporary bottleneck.
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=290784
To run the code as a midlet, one new class would need to be
written. I suspect any compotent Java developer could get
something working in a few days. The main problem is
performance. For example, when I run the code as an applet on
my PDA which has a 400MHz processor it takes about 45
seconds to display a black and white page. (Color takes
longer.) Scrolling takes about 10 seconds. Since most
documents require horizontal scrolling to read, it makes the
applet fairly useless for all but the most patient users. A midlet
would have the same performance...
A JVM that does JIT processing could be up to 5 times faster on
the same hardware. I also expect with further optimizing the
code could be made 50% faster. Also, CPU speeds double ever
one and a half years. If I were to buy my PDA today, it would
run at 633MHz for the same price. So, performance is not a
perminent problem but it is a temporary bottleneck.
Bill