View Single Post
Old 04-03-2009, 12:40 PM   #73
Abelturd
Little Fuzzy Soldier
Abelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toysAbelturd shares his or her toys
 
Abelturd's Avatar
 
Posts: 580
Karma: 5711
Join Date: Sep 2008
Location: Nowhere in particular.
Device: cybook gen3, htc hero, ipaq 214
Quote:
Originally Posted by igorsk View Post
Mobipocket distributes their SDK as pre-compiler (and obfuscated) set of Java classes, not in source code. Bookeen only implemented device-specific things like input and rendering; they cannot add support for features not implemented by Mobipocket.
That's too bad. But I can't wrap my mind around one thing. Why choose as a primary reader software you cannot later add features to and which makes you completely dependant on support from someone else (mobipocket in this case)?

It's funny how there seem to be these repulsive forces between me and mobipocket reader. On PPC it made me switch to Haali reader and on cybook it made me switch to custom pdfs. We're simply incompatible.
Abelturd is offline   Reply With Quote