Quote:
Originally Posted by kovidgoyal
Hmm, this will require some careful thought. I'm a little too busy at the moment with the 0.7 beta process, so please open a ticket and attach your javascript to it. I will look into integrating/improving it as soon as the 0.7 beta process is done.
|
I know that this is already a bit old thread, sorry, I was out of the net for some days.
Anyway, I do not think that it was worth opening a ticket for a feature that nearly no one uses. Besides that, as I said before, I can not write python, but I can read it (sort of). Looking at the code makes me think that this is not such a trivial thing to implement. The most important point are the limitations of the WebKit concerning the implementation of the CSS3 Multi-Column Module. Irrespective of what’s on the docs, I can categorically say that the “Column breaks” do not work and therefore, to implement in the viewer a smooth two-facing-pages mode will require a lot of coding.
Definitively, the developers’ time is better employed in something else.
However I can try to improve the scripted solution a bit more. Maybe Kovid can answer a couple more questions?
-does the viewer accept cookies?
-why when I set the overflow on the user style (either "overflow":'auto'; or ( "overflow-x":'auto' and "overflow-y":'auto' )
the viewer show two sets of scroll bars, but not so if I set the overflow to ‘scroll’? Moreover the scroll distance allowed by the more external of the two horizontal bars is not always correct, whereas the one of the inner one is.
-can you explain the structure of the bookmarks:
(lp1
(S'calibre_current_page_bookmark'
S'21#body|0.000000'
tp2
a.
(lp1
(S'calibre_current_page_bookmark'
S'21# > *:eq(0) > *:eq(1) > *:eq(35) |1'
tp2
a.
-does the viewer exports a function like “go_nex” or “go_prev”?
Thanks a lot