MobileRead Forums - View Single Post - Hands-on with the iRex iLiad

Henrycat · 04-29-2006, 06:27 PM

Sorry for the delay but my internet provider is messing around with the internet connection

It worked ok yesterday, but today it's acting up again...

Right now i'm using a laptop from a friend of mine that is "borrowing" a wireless connection

Anyway time for some answers, but first you have to consider some points:

- My Iliad has the final hardware, but not the final software. This is important because right now i'm more of a beta tester than a final user.

According to Alex Henzen, most of the problems, like the power managment are alredy fixed. My device doesn't have the last version because it's still being tested, but when it is released next week i just have to update the device.

I decided to write things like i have found them, but a few days from now they will be diferent. I could have waited a few days and then write something up, but somehow i thought you would prefer if i didn't wait

Please keep this in mind when you read everything i write

I hoped not to create negative publicity when i decided to write about the device has it is.

Questions

- Online viewer?
The iliad was never meant to be an online viewer, but since it has been talked about a lot, iRex is considering some sort of web capture. Basicaly there would be a web server catching the user requests, and creating/sending an offline page.

It isn't final that it will be created, but it is planned to begin the study of it's implementation around the end of the year. It's not first priority, because anything that would require constant wireless will be a major power drain.

- Power management

Like i already said the power management isn't working yet, but that gives a good idea of how the device would behave in max settings let's say.

I seriously doubt anyone will be using the reader at full processor speed, writing with the stilus, reading CF and SD cards, and connecting through the wireless.

The page count given by iRex was made using the xhtml reader constantly fliping pages. The page number is actually higher if you would consider only reading. But they had to also consider casual wireless use, CF SD use, and ocasional annotation.

The page count will have to be updated for the "final" OS version, and i was told it will probably be higher because of all the optimizations.

When they mention time instead of pages, they are considering you are writing on screen, using heavily the processor and CF SD cards.

Has you can see it's two very different things.

- Navigation bar
I will have to show pictures, but this laptop doesn't have a card reader

so it will have to wait maybe tomorrow my connection will be ok.
Also, any picture that i show of the menus will be temporary because they are being updated for the "final" version.

I can already input the page number using the screen keyboard, and in the "final" OS version use character recognition.

They have also arranged an ingenuous way for the problem of page numbering in various zooms. Basically you have a "fixed" numbering. When you zoom in/out the program breaks the page in various sub pages.

You can still say go to page 244. if it is zoomed you start at the first part of the page, and you can go to the following parts, and the following "page".
The reader shows an icon representation when a page is broken in subpages.

- Annotation
Annotation will create an image file that is "anchored" in the text. Although i can write onscreen but i can't save it yet (one of things working already on the final version).

It will depend on the viewer it the images are seperate or encapsulated. if i remenber correctly only the apabi reader will encapsulate the notes in the book.

Since the device uses independent viewers it is possible annotation will vary in other readers.

- Screen quality
I can see a big diference when reading on the Iliad. It has much better contrast between the black and white. It is also quicker changing pages (after the caching delay).

This is because the Iliad and Sony reader use the "second version" of eink screens. I don't know about Jinke, but it probably also uses the same.

Any other questions? Lets hope tomorrow i will have the internet working ok

04-29-2006, 06:27 PM	#11
Henrycat Zealot Posts: 149 Karma: 1146 Join Date: Oct 2005 Location: Pernes. A small village in Portugal. Device: Kindle Voyage	Sorry for the delay but my internet provider is messing around with the internet connection It worked ok yesterday, but today it's acting up again... Right now i'm using a laptop from a friend of mine that is "borrowing" a wireless connection Anyway time for some answers, but first you have to consider some points: - My Iliad has the final hardware, but not the final software. This is important because right now i'm more of a beta tester than a final user. According to Alex Henzen, most of the problems, like the power managment are alredy fixed. My device doesn't have the last version because it's still being tested, but when it is released next week i just have to update the device. I decided to write things like i have found them, but a few days from now they will be diferent. I could have waited a few days and then write something up, but somehow i thought you would prefer if i didn't wait Please keep this in mind when you read everything i write I hoped not to create negative publicity when i decided to write about the device has it is. Questions - Online viewer? The iliad was never meant to be an online viewer, but since it has been talked about a lot, iRex is considering some sort of web capture. Basicaly there would be a web server catching the user requests, and creating/sending an offline page. It isn't final that it will be created, but it is planned to begin the study of it's implementation around the end of the year. It's not first priority, because anything that would require constant wireless will be a major power drain. - Power management Like i already said the power management isn't working yet, but that gives a good idea of how the device would behave in max settings let's say. I seriously doubt anyone will be using the reader at full processor speed, writing with the stilus, reading CF and SD cards, and connecting through the wireless. The page count given by iRex was made using the xhtml reader constantly fliping pages. The page number is actually higher if you would consider only reading. But they had to also consider casual wireless use, CF SD use, and ocasional annotation. The page count will have to be updated for the "final" OS version, and i was told it will probably be higher because of all the optimizations. When they mention time instead of pages, they are considering you are writing on screen, using heavily the processor and CF SD cards. Has you can see it's two very different things. - Navigation bar I will have to show pictures, but this laptop doesn't have a card reader so it will have to wait maybe tomorrow my connection will be ok. Also, any picture that i show of the menus will be temporary because they are being updated for the "final" version. I can already input the page number using the screen keyboard, and in the "final" OS version use character recognition. They have also arranged an ingenuous way for the problem of page numbering in various zooms. Basically you have a "fixed" numbering. When you zoom in/out the program breaks the page in various sub pages. You can still say go to page 244. if it is zoomed you start at the first part of the page, and you can go to the following parts, and the following "page". The reader shows an icon representation when a page is broken in subpages. - Annotation Annotation will create an image file that is "anchored" in the text. Although i can write onscreen but i can't save it yet (one of things working already on the final version). It will depend on the viewer it the images are seperate or encapsulated. if i remenber correctly only the apabi reader will encapsulate the notes in the book. Since the device uses independent viewers it is possible annotation will vary in other readers. - Screen quality I can see a big diference when reading on the Iliad. It has much better contrast between the black and white. It is also quicker changing pages (after the caching delay). This is because the Iliad and Sony reader use the "second version" of eink screens. I don't know about Jinke, but it probably also uses the same. Any other questions? Lets hope tomorrow i will have the internet working ok