Calibre Viewer problem

[BetterRed]

Originally Posted by erketre

Besides I would like to have a vertical scrollbar in the viewer.

In 4.1: check Preferences->Scrolling behaviour->Show a scroll bar.

BR

[kovidgoyal]

Originally Posted by trcm

$ brew install calibre

Update bre to run from master and re-install calibre or use the official calibre dmg and you will be fine.

[kovidgoyal]

Originally Posted by erketre

Please render new chapters/pages before actually showing it to the User on the screen. I see font size/family glitches for a fraction of second when new chapter is being loaded. I use a custom font (Bookerly). Similar glitches occur when resizing the viewer's window.

That's what the viewer used to do and then in the beta process I got feedback saying people dont like loading screens, shrug.

[DarkRookie2]

1. Menu
a. The layout is still a mess
b. Still doesn't open each time. Seems to be positioning thing. Doesn't seem to work on the top or the bottom of the window.
c. No option to create a toolbar. Would like quick option for text size and ToC since I click on those a lot.
d. Can't keep increasing/decreasing text size with a button. I get 6 options or I got to type something in.

2. Reading
a. Cannot copy text with right client
b. Cannot copy images with right click
c. Cannot view images with right click
d. The header and footer take away from the reading space. Not noticeable at first, but once I did it started really bugging me.
e. Scroll bar is not native
f. Cannot paste location after coping them
g. Estimated time left still isn't updating.

It still honestly feels like you took the reader mode from a major browser and left it as is. It feel unsatisfying compared to the old version. I will try again in 4.2 and keep an old copy around. (Which it seems like I am doing for a lot of software and not just this.)

[theducks]

Originally Posted by DarkRookie2

1. Menu
a. The layout is still a mess
b. Still doesn't open each time. Seems to be positioning thing. Doesn't seem to work on the top or the bottom of the window.
c. No option to create a toolbar. Would like quick option for text size and ToC since I click on those a lot.
d. Can't keep increasing/decreasing text size with a button. I get 6 options or I got to type something in.

2. Reading
a. Cannot copy text with right client
b. Cannot copy images with right click
c. Cannot view images with right click
d. The header and footer take away from the reading space. Not noticeable at first, but once I did it started really bugging me.
e. Scroll bar is not native
f. Cannot paste location after coping them
g. Estimated time left still isn't updating.

It still honestly feels like you took the reader mode from a major browser and left it as is. It feel unsatisfying compared to the old version. I will try again in 4.2 and keep an old copy around. (Which it seems like I am doing for a lot of software and not just this.)

Wow! You can't deal with a different way of getting there?
Now it is 2 clicks required (1 right, 1 normal)

OTOH I probably copied images from the previous viewer (since I started using Calibre in 2010) about 2 times.
I do use the Editor and I have used the Unpack tool to Bulk copy/process images.
You do know that Calibre is Free and Open Source? Roll your own

[DarkRookie2]

1. It use to be only one click
2. I view them more than copy, but still sucks I have neither of those options any longer.
3. Let get right on that with my lack of Python knowledge. I took a look at the code and had no idea what was going on or where to even start to try and change this.

[kovidgoyal]

Originally Posted by DarkRookie2

1. Menu
a. The layout is still a mess\

Whatever that means

b. Still doesn't open each time. Seems to be positioning thing. Doesn't seem to work on the top or the bottom of the window.

Yes it does. The exception being right clicking in the margins. Which is anyway fixed in the next release.

c. No option to create a toolbar. Would like quick option for text size and ToC since I click on those a lot.
d. Can't keep increasing/decreasing text size with a button. I get 6 options or I got to type something in.

Yes you can using ctrl++ and ctrl+- or ctrl+mouse wheel

2. Reading
a. Cannot copy text with right client
b. Cannot copy images with right click
c. Cannot view images with right click

yes you can

d. The header and footer take away from the reading space. Not noticeable at first, but once I did it started really bugging me.

That is what a header and footer is. All headers and footers anywhere and everywhere take away from reading space.

e. Scroll bar is not native

So?

f. Cannot paste location after coping them

yes you can

g. Estimated time left still isn't updating.

yes it does. And if it it doesn't, since this feature is not even present in the old viewer, I dont see how it matters.

It still honestly feels like you took the reader mode from a major browser and left it as is. It feel unsatisfying compared to the old version. I will try again in 4.2 and keep an old copy around. (Which it seems like I am doing for a lot of software and not just this.)

It honestly feels to me like you've decided to dislike it because you hate change and are now inventing reasons. But hey, feel free to keep around the old version if it floats your boat.

[erketre]

Originally Posted by kovidgoyal

That's what the viewer used to do and then in the beta process I got feedback saying people dont like loading screens, shrug.

The rule is: first render then show. You do not see broken web page before CSS is applied in any Web Browser. Than would be a mess.

Yes, loading screen might be a bit.. smaller. Something like the dots in a circle when Windows 10 is booting. That would look nice

[DoctorOhh]

Originally Posted by DarkRookie2

1. Menu
a. The layout is still a mess

My opinion but I see the layout as different, but consistent. Certainly not a mess.

Originally Posted by DarkRookie2

b. Still doesn't open each time. Seems to be positioning thing. Doesn't seem to work on the top or the bottom of the window.

Since you seem to be having trouble operating this new interface my advice to you is to right click in the center of the page you are reading to bring up the preferences.

Originally Posted by DarkRookie2

c. No option to create a toolbar. Would like quick option for text size and ToC since I click on those a lot.

If you like having the TOC available then simply leave it open when you close a book. It will appear every time you open a book and you never have to select it again.

Originally Posted by DarkRookie2

d. Can't keep increasing/decreasing text size with a button. I get 6 options or I got to type something in.

It takes a second to hold down the Ctrl button and move the scroll wheel on the mouse or Ctrl + or - to adjust font size. Additionally you can set the minimum font size in the preferences and configure how large the steps are between the 6 choices you claim to be limited to.

Originally Posted by DarkRookie2

a. Cannot copy text with right client
b. Cannot copy images with right click
c. Cannot view images with right click

When you right click on an image or on selected text the option to copy, view the image or copy the selected text is right in front of you.

Originally Posted by DarkRookie2

d. The header and footer take away from the reading space. Not noticeable at first, but once I did it started really bugging me.

If you don't like the header and footer then simply go to preferences adjust the top and bottom margins to remove them. The option is yours.

Originally Posted by DarkRookie2

e. Scroll bar is not native

What's your point?

Originally Posted by DarkRookie2

It still honestly feels like you took the reader mode from a major browser and left it as is. It feel unsatisfying compared to the old version. I will try again in 4.2 and keep an old copy around. (Which it seems like I am doing for a lot of software and not just this.)

If your desire is to use the old viewer, search the treads here, it should be trivial to setup calibre 4.1 to use the calibre 3.48 viewer by default.

P.S. I hope those kids stay off of your lawn.

[kovidgoyal]

Originally Posted by erketre

The rule is: first render then show. You do not see broken web page before CSS is applied in any Web Browser. Than would be a mess.

Of course you do, just google FOST https://en.wikipedia.org/wiki/Flash_of_unstyled_content

Yes, loading screen might be a bit.. smaller. Something like the dots in a circle when Windows 10 is booting. That would look nice

This problem is anyway gone in the next release.

[erketre]

Originally Posted by kovidgoyal

Of course you do, just google FOST https://en.wikipedia.org/wiki/Flash_of_unstyled_content

So? From this link you gave we know it is a known problem. But again; I see no broken paragraphs when resizing browser's window, nor font jumping form default to customized (for a fraction of second), as I see in new Calibre viewer.

[kovidgoyal]

Originally Posted by erketre

So? From this link you gave we know it is a known problem. But again; I see no broken paragraphs when resizing browser's window, nor font jumping form default to customized (for a fraction of second), as I see in new Calibre viewer.

So, it happens all the time in browsers. It is unavoidable given that browsers load things asynchronously, as should be obvious to anyone that knows even a little bit about how browsers work. If you haven't seen it, it is because the sites you visit happen to have worked around it by hiding content till the asynchronous loading is complete, or the content is already in your browsers cache. Or you are blind.

Just as I already said I have worked around it in the calibre viewer as well, exactly by hiding content until loading is complete. And broken paragraphs when resizing windows happened in the old viewer as well and happen in any browser that is rendering multi-column content. Indeed, the viewer, both old and new is a goddamn browser.

[erketre]

Originally Posted by kovidgoyal

So, it happens all the time in browsers. It is unavoidable given that browsers load things asynchronously, as should be obvious to anyone that knows even a little bit about how browsers work. If you haven't seen it, it is because the sites you visit happen to have worked around it by hiding content till the asynchronous loading is complete, or the content is already in your browsers cache. Or you are blind.

Just as I already said I have worked around it in the calibre viewer as well, exactly by hiding content until loading is complete. And broken paragraphs when resizing windows happened in the old viewer as well and happen in any browser that is rendering multi-column content. Indeed, the viewer, both old and new is a goddamn browser.

Modern browsers do not show HTML without applying CSS. That would be a mess (I remember old browser sometimes did this). JavaScript is applied after page is fully loaded, that's true, but CSS not.

Your viewer is not as fast as modern browsers in rendering, so that's why loader is necessary until the page is fully rendered.

Try this: Set custom Unicode font (heavy font, I have Bookerly), take book with a lot of pure text (~200KB per chapter) and see youself what I'm talking about. I see garbled text/paragraphs for sometimes as much as 1 second.

[kovidgoyal]

Originally Posted by erketre

Modern browsers do not show HTML without applying CSS. That would be a mess (I remember old browser sometimes did this). JavaScript is applied after page is fully loaded, that's true, but CSS not.\

Bullshit. JavaScript execution can be either synchronous or asynchronous, depending on a attribute of the script tag. CSS loading only blocks rendering of content that appears after the <link> tag.

Your viewer is not as fast as modern browsers in rendering, so that's why loader is necessary until the page is fully rendered.

My viewer is a modern browser. Chrome, to be precise.

Try this: Set custom Unicode font (heavy font, I have Bookerly), take book with a lot of pure text (~200KB per chapter) and see youself what I'm talking about. I see garbled text/paragraphs for sometimes as much as 1 second.

As I have already said, twice before, you wont with the next release.

[DoctorOhh]

Originally Posted by erketre

Try this: Set custom Unicode font (heavy font, I have Bookerly), take book with a lot of pure text (~200KB per chapter) and see youself what I'm talking about. I see garbled text/paragraphs for sometimes as much as 1 second.

Since Kovid has repeatedly stated that the issue your going on about is fixed in the next release I don't understand your persistence. That said, I did exactly what you suggested and on my system I don't even see a flicker between html files. Most of my books are formatted one html file per chapter. When I cross between chapters (files) I don't notice a blip or delay indicating any font or other issues using Bookerly. I do however see what Kovid pointed out when resizing the window, but since I don't resize the window while reading I don't see how this could be an issue.

Again since Kovid says it is fixed you might just want to thank him and see how it performs in the next release.