DR800 I ENABLED CONTINUOUS PAGE MODE ON DR 800

[Iñigo]

yep.

Originally Posted by CoolDragon

I am annoyed by this 2 columns icon view too, so I switched to list view. Maybe there is something we can do in CTB to fix this.

EDIT: ok, solved. Edit /usr/share/ctb/ctb.rc and change lines 57 and 58:

    erGtkIconView::item-width       = 195
    erGtkIconView::item-height      = 195

to:

    erGtkIconView::item-width       = 175
    erGtkIconView::item-height      = 175

Maybe a higher value is better, maybe 185...

Originally Posted by CoolDragon

Maybe something related to popupmenu.

popupmenu/src/dialog.c file, lines 53-81.

Take a look at https://inigo.katxi.org/ereader/dr80...8c_source.html

[CoolDragon]

Also the beginning of splash.c

[Iñigo]

Originally Posted by CoolDragon

Also the beginning of splash.c

I think that file is only a test.

Btw, I propose you a treat: I provide you a solution for the 3 columns issue for a new compilation of popupmenu with this fixed

ok, ok, look at my previous message, I've edited it and added the solution

[repods]

Originally Posted by CoolDragon

Why don't you post what you have found out? You said something "legal" and wanted to write an application to enable continuous/page flow but you never said what you are trying to do.

Anyway, someone, after trying out my hacking way, found out that "page flow" and "full screen" can be achieved with the DR800's original uds. All you need to do is setting the property in the SQLite database.

ok .. you reached the real stuff..
this is what I mean..
luckily for us in irex design fullscreen and page flow continuous are attributes of the single books, just like last page read, zoom level and scribbles..
and are stored in metadata.db under the books directory in the sd card
so all you need to do to test full screen and the like, is simply to open that file with any sqlite3 manager app, update the right filelds and save it back..
you don't even need to touch the original firmware at all..

this is moreover the only right way.. infact to use the dr1000 uds is good to set easily those fields, but it's not good to actually show the documents on dr800, infact it's slower, most likely it's not optimizated for dr800 cpu and cache, has some screen sincronization problems (double refresh) and doesn't show things exactly how they should be shown..
instead the original uds performs very well...

so the next right thing for us to do is to write an app for dr800 to set easily those fields on a per book basis.. or to modifiy some open source part of the dr800 firmware.. the first solution should not be very difficult considering that in dr800 we already have a libermetadb to access metadata.db
obviously if irex guys could put all this inside uds, that would be the best solution..

beside this what I still would like to have is the flip bar working right in panning mode: I don't like at all continuous mode in portrait mode.. and there is still the double refresh issue.. but obtaining this is a bit more difficult and requires more study and time..

[repods]

Originally Posted by Shaggy

Comparing relative sizes of two binaries doesn't mean a whole lot.

.

most likely it means that full screen and continuous page mode features are already built in dr800 firmware

[repods]

Originally Posted by CoolDragon

Also the beginning of splash.c

btw guys ..
in your development consider that the original uds after some page reads (about 10) write again on metadata.db for some reasons and reset the fullscreen and continuous fields..

[CoolDragon]

ok .. you reached the real stuff..
this is what I mean..
luckily for us in irex design fullscreen and page flow continuous are attributes of the single books, just like last page read, zoom level and scribbles..
and are stored in metadata.db under the books directory in the sd card
so all you need to do to test full screen and the like, is simply to open that file with any sqlite3 manager app, update the right filelds and save it back..
you don't even need to touch the original firmware at all..

I have already reported this in a previous post. Writing an app on DR800 should be super easy, but not my interest for now. And this is not an assumption, see http://www.hi-pda.com/forum/viewthre...extra=page%3D1. Someone has already modified the CTB to control these properties for PDF files. But uds seems to read the cached properties so you have to reboot to somehow force re-indexing to make the new property work.

this is moreover the only right way.. infact to use the dr1000 uds is good to set easily those fields, but it's not good to actually show the documents on dr800, infact it's slower, most likely it's not optimizated for dr800 cpu and cache, has some screen sincronization problems (double refresh) and doesn't show things exactly how they should be shown..
instead the original uds performs very well...

Other than double refresh, I haven't noticed any other problems. They both use the same CPU and RAM amount, so it should be very close. Not to mention the much better power management of dr800.

beside this what I still would like to have is the flip bar working right in panning mode: I don't like at all continuous mode in portrait mode.. and there is still the double refresh issue.. but obtaining this is a bit more difficult and requires more study and time..

This would be hard, since event is handled by uds which is not open sourced, unless you modify the binary.

btw guys ..
in your development consider that the original uds after some page reads (about 10) write again on metadata.db for some reasons and reset the fullscreen and continuous fields..

Interesting.

[CoolDragon]

OK, updated popupmenu, minor tweaks:
1. Icon view 3 column (thanks Inigo, 185 works!, copy ctb.rc to /usr/share/ctb/)
2. Text position when booting and connected to PC
3. Status bar icon selection, I like the "close" button
4. Menu bar, removed sensor lock and eject sd card
5. "Folder" -> "Explorer" in taskbar/tab

[yacoob]

CoolDragon, perhaps it would be useful if you could also publish your changes to the code (either as set of changed files or diff). Or perhaps just set up a github repository, so in case something breaks, we can easily compare the changes?

[CoolDragon]

Originally Posted by yacoob

CoolDragon, perhaps it would be useful if you could also publish your changes to the code (either as set of changed files or diff). Or perhaps just set up a github repository, so in case something breaks, we can easily compare the changes?

Sure and I should actually (according to GPL). Somebody can set up a github repository? Haven't used it personally.

[yacoob]

Is there a thread that discusses this fiddling in more detail? I found some promising entries in application_data sqlite3 database ("uds_page_flow" and "uds_full_screen" in application_data), but setting those to '1' resulted in irex emulator saying that "unexpected error has occured".

Also, the entries in this db seem to be created after one opens a file for the first time - so flipping those bit from the device might be a bit unwieldy (open a new book, flip the bits, go back to book...).

Disclaimer: The only thing I've played with was the emulator - I don't have a device handy to test things.

[Iñigo]

Originally Posted by yacoob

Is there a thread that discusses this fiddling in more detail? I found some promising entries in application_data sqlite3 database ("uds_page_flow" and "uds_full_screen" in application_data), but setting those to '1' resulted in irex emulator saying that "unexpected error has occured".

Also, the entries in this db seem to be created after one opens a file for the first time - so flipping those bit from the device might be a bit unwieldy (open a new book, flip the bits, go back to book...).

Disclaimer: The only thing I've played with was the emulator - I don't have a device handy to test things.

There is a link in CoolDragon's message #52 to a Chinese forum.
It's quite interesting. Googlechrome translation is good enough.

[yacoob]

I've poked around, but I cannot get metadata.db to be populated with data. Apparently some r/w cache sits inbetween, and isn't that eager to dump the state. The file got updated after I've added some content to the reader and ran '/etc/init.d/xserver-nodm restart' (obviously), but afterwards, no updates. both file_metadata and application_data tables remain empty.

And answering your earlier question, Iñigo, strace is there

[Shaggy]

Originally Posted by repods

most likely it means that full screen and continuous page mode features are already built in dr800 firmware

They probably are, but file sizes are not a good way to tell. Drawing conclusions from that alone is probably not the best habit to get in.

[repods]

Originally Posted by Shaggy

They probably are, but file sizes are not a good way to tell. Drawing conclusions from that alone is probably not the best habit to get in.

I would like to dissent..