View Single Post
Old 03-28-2010, 06:46 AM   #19
rfog
Guru
rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.rfog ought to be getting tired of karma fortunes by now.
 
Posts: 696
Karma: 2383012
Join Date: Aug 2007
Location: Schiedam (The Netherlands)
Device: Lots of eInk devices and iOS stuff
Quote:
Originally Posted by ondabeach View Post
Hi rfog, if you check out the the first post you'll see that the main focus of this thread is screen size and speed. I developed ZR with a HTC Touch Diamond as test device and it has vga (640 x 480) res and has pretty snappy performance.

I am actually rewriting the decode and render engines entirely to address the performance issue from two fronts. This is neccessary because the JE's are built for battery life as opposed to performance.

Once these two critical issues have been addressed then I will be actively seeking ideas and suggestions on other ways to improve ZR such as the formatting options you mentioned.

Cheers,

Steve.
Steve, ZE is a promising program. :-)

To solve rendering speed problems most common techniques are double buffering (you can direct enable by reflection in .NET -at least in PC, I do not know if it works in CE) and background screen composing: you compose in background the next screens and brings to front via blt copy and double buffering.

The other things are less important. Other future improvement could be columns support.

I will stay tunned to test all your improvements. :-)
rfog is offline   Reply With Quote