I originally saw this mentioned on mobipocket's forums, but Karel (iRex Community Manager) in the iRex forum thread When will iRex's version of Mobipocket add features? (http://forum.irexnet.com/viewtopic.php?t=2500) said: There will be no new features introduced in the current Mobipocket viewer. The reason for this is because we are working on a viewer frame work. This viewer frame work will make it possible to easily add additional format support by both the community and iRex. In addition each feature developed for the viewer framework will be available to all supported formats.

This is bad news in the short term, since the iLiad MobiPocket reader is very feature poor, but iRex is probably right in the long term to ditch the entire thing and start again.

Is iRex really capable of generating a viewer framework from scratch? I think it would actually be easier, and technically superior, to start over using FBReader as the basis for all viewers. It already meets the "easy to add new formats" and "new features" applies to "all supported formats" criteria. Note that FBReader can now in principle support (licensed) MOBI DRM by distributing a binary only version with this included.

Guess more people will be buying Cybook instead of the Iliad.

I suspect the biggest challenge with their viewer framework app will be scribbles and how to handle it with text resizing. Since FBReader can't handle scribbles or PDF's, I don't know if that'd be the best choice.

A framework supporting the unique features of the iLiad would be absolutely fantastic. :2thumbsup

However, I'm a bit afraid that whipping this up will take a long time, perhaps longer than many potential buyers (or even owners) are willing to wait.

Not losing the Time to Market window is a bit of the essence here, I think...

Cheers,
- Don [:-], who can think of at least 100,000 Nice To Haves... :D

I think the framework is in fact the best solution. Though it'll take some time it is better than having several readers with basically the same purpose (mobipocket, iPDF, FB-Reader, minimo for html, ...) and every single one occupying in the sum more time than one big effort. I love mobi-pocket books for their dictionary support, but the menu bar and pages row sucks, if one knows how beautiful it can be with fullscreen-iPdf.
I'm spoiled from the Palm eReader ;) and it's options.

So I hope the best.

cheers,
Nergal

I like the "feature" where it suddenly jumps ahead like 20 pages (due to reformatting) and I have to click backwards.

I'm spoiled from the Palm eReader ;) and it's options.
Yeah, me too. :D

And quite frankly, spoiled from its sheer speed when it comes to looking up something...

Cheers,
- Don [:-]

Note that FBReader can now in principle support (licensed) MOBI DRM by distributing a binary only version with this included.

No, it can't. FBReader is GPL code, distributing a binary only copy of the FBReader is a violation of the GPL. It can't happen unless the FBReader authors change the licensing on their code. I do not believe this will be happening. In fact, I doubt it will ever happen.

I am biased, I have an iliad.

I am frankly disappointed with all the readers so far, and not just those available for the iliad. So starting from scratch is, in my books, a good way forward and I don't mind waiting.

I could make plenty of suggestions, one, if they are reading, is a CSS dropaway framework, a full implementation of CSS, forget the actual element tags, don't worry about what is a paragraph or not, or what is a title, but as the user increases the font size drop-off CSS layout features in a step by step and predictable way.

The principle is that the greater the relative display area (area of size in proportion to font size), the closer the ebook to the publisher's design (including pagation). Reduce the effective viewing area (ie increase the font relative to the actual screen), drop pagation, drop margins, drop heading decoration, drop "drop Caps", drop justifictation, change font, reduce spaces etc.

A collapsing bag in other words.

The point being, is that it is a mistake to rely on expecting particular elements in designing reading software.

No, it can't. FBReader is GPL code, distributing a binary only copy of the FBReader is a violation of the GPL. It can't happen unless the FBReader authors change the licensing on their code. As you say, it can only be done by the authors of the code. FBReader's authors are prepared to do this, but it does make accepting outside contributions to the standard version more difficult. See FBReader's GPL and Contribution Guidelenes (http://www.fbreader.org/docs/contributions.php).

I suspect the biggest challenge with their viewer framework app will be scribbles and how to handle it with text resizing. Since FBReader can't handle scribbles or PDF's, I don't know if that'd be the best choice. FBReader would need several enhancements including: a) dictionary, b) bookmarks/scribbles, c) style sheets. Note that FBReader already has dictionary support on a few platforms. The "framework" argument works for FBReader too, add dictionary support or scribbles and these are available for 12 ebook formats and counting. There is also the advantage that you don't have to develop on the iLiad.

The FBReader developers were originally opposed to adding PDF support, but they listened to their users and now their Electronic Book Formats (http://www.fbreader.org/docs/formats.php) page says: pdf This format is not supported. Files in this format may contain just text as well as image representation of pages. We plan to include PDF support in FBReader: first support for files that are using text only.

DonRobodroid's time to market point is also in favor of FBReader, particularly if it was originally released without PDF support.

However, I'm a bit afraid that whipping this up will take a long time, perhaps longer than many potential buyers (or even owners) are willing to wait.

Not losing the Time to Market window is a bit of the essence here, I think...


Although it was just reported on Mobileread recently, iRex has been talking about a common framework for the various viewers for a pretty long time. It's not like they're just starting to work on it now.

I started the original discussion of this on the iRex iLiad forum. But it should be noted that this reply from Mobipocket tech support somewhat contradicts what was said on the iRex forum. See this post on the Mobi forum:

http://www.mobipocket.com/forum/viewtopic.php?t=11136

in which Mobi_Vincent said on June 2, 2008:We are working with iRex for the new Mobipocket viewer for the Iliad. Be sure this second version will be better ! At the very least, this implies a role by Mobipocket programmers in helping create the new iRex viewer framework.

----------------
ROBERT J. SAWYER, Science Fiction Writer
Hugo Award winner for HOMINIDS
http://www.sfwriter.com * sawyer@sfwriter.com
----------------

It probably just means that Mobipocket is helping iRex integrate the mobipocket library into their new framework. They pretty much have to be involved, the mobipocket format isn't an open standard. The only way to parse/render a mobipocket file is with the library that mobipocket writes. They're not going to just turn over the full specs and let iRex create their own reader completely from scratch.

I don't think that contradicts anything iRex has said.

It's a shame to hear that the Mobi reader won't be updated on the iLiad. It has one "show-stopping" lack for me - no bookmarks. I absolutely require bookmarks for proof-reading the books I create, and their lack was the main reason I sold my iLiad and bought the CyBook. The iLiad is the only implementation of the Mobi Reader (AFAIK) which doesn't implement bookmarks.

It's a shame to hear that the Mobi reader won't be updated on the iLiad. It has one "show-stopping" lack for me - no bookmarks. I absolutely require bookmarks for proof-reading the books I create, and their lack was the main reason I sold my iLiad and bought the CyBook. The iLiad is the only implementation of the Mobi Reader (AFAIK) which doesn't implement bookmarks.

They're not updating it because they're basically re-writing it. ;)

Hopefully they'll put in more features this time. Personally, I'm hoping for better font support. I reformat most of my ebooks into PDFs just so that I can set the font.

I don't have much use for bookmarks, but lots of people have been asking them about it in the past, so hopefully that'll be in there too. I don't think we're going to know until they release it though. I tried to get them to drop a hint about whether the new framework will be part of the next software release, or if it's still going to be down the road a while, but didn't get a response.

Mobipocket is one of the big reasons that I chose iLiad, but the lookup function is so poor comparing with the version on my Nokia N70 :(

Guess more people will be buying Cybook instead of the Iliad.

Who cares about Mobipocket support ... :rofl:

Yes, absolutely true for sure, the lookup function IS poor. But the MAIN function of an ebook reading device (which still IS book reading) is light years ahead on an iLiad compared to cell phones, PDAs etc. (and even competing eInk devices)

So let's primarily be happy with the tremendous advantage of the iLiad (768x1024x16 on 8" !!!) and only secondarily grumpy with all the disadvantages that (easily, granted) come to mind... :)

Nonetheless iRex HAS to do something regarding the mobipocket functionality and the sooner the better! :rolleyes:

Cheers,
- Don [:-]

Who cares about Mobipocket support ... :rofl:
Hm, well, actually I do. :D

That is, I care about support for a format that offers contemporary literature in a legal way. And I don't mind if it's called mobipocket, ereader, PDF, whatnot - but my iLiad should be able to display current books in an easy-to-use, luxurious way. :)

Cheers,
- Don [:-]

iRex has been claiming they were working on some new "mother of all viewers" for over a year now. Frankly, I'll believe it when I see it. Meanwhile, I'm grateful for FBreader, because the built-in readers are not very usable IMHO.

Frankly, I'll believe it when I see it. Meanwhile, I'm grateful for FBreader, because the built-in readers are not very usable IMHO.
I´m using only the FBReader - primarially for CHM viewing.

Hm, well, actually I do. :D


So do I. It was primarily for Mobi support that I bought my iLiad, and the deficiencies in the implementation on the iLiad were the main factor that made me regretfully decide to sell it again.

It should be pointed out, however, that a lack of "search" facilities is not unique to the iLiad. The Mobi Reader on the CyBook Gen3, although hugely better than that of the iLiad, is also lacking a "search" capability.

I don't know if its aproperiate place to put it here, but I want a toolkit with which I can develop applications that will run well & look cool on the iLiad and the PC.