View Single Post
Old 09-20-2007, 04:08 PM   #18
delphidb96
Wizard
delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.
 
Posts: 2,999
Karma: 300001
Join Date: Jan 2007
Location: Citrus Heights, California
Device: TWO Kindle 2s, one each Bookeen Cybook Gen3, Sony PRS-500, Axim X51V
Someone should tell Bookeen that Mobipocket is JAVA based - of course I wasn't expecting that someone do an EXACT port of Iliad's version, just *some* port of Mobipocket functionality. And as others have pointed out, there's no reason one *needs* a mouse or TS-screen, just make the jogwheel/compass function in its place. After all, it 'could' be read as 'move cursor right/left/up/down'... Something to think about.

Derek

Quote:
Originally Posted by HarryT View Post
Sadly, neither would be straightforward.

FBReader is "icon" driven and needs a mouse or a touch sensitive screen to drive it. You'd need to completely re-design the user interface for a machine like the Reader which doesn't have a touch screen.

The iLiad Mobipocket Reader would be even harder, because it's Java-based, and the Reader doesn't have a JVM.

Sorry to be the bearer of bad tidings .
delphidb96 is offline   Reply With Quote