Beta testers for calibre 9 needed

[Ebookus]

is version 9 dropping support for any OSs?

[kovidgoyal]

Originally Posted by DNSB

Just updated to the latest source and adding the author to the spine has some issues. In the bookshelf preferences, the author template editor does not seem to be working. In the bookshelf view, quite a few books seem to be too narrow so the author is not displaying.

The first has been fixed, the second is not something that anything can be done about. You can increase spine height which will increase minimum spine width automatically, but otherwise thin books will not be able to display a second line.

[kovidgoyal]

Originally Posted by Ebookus

is version 9 dropping support for any OSs?

Not unless Qt has some issues with them, which as far as I know, it doesnt, but that's what the beta is for.

[kovidgoyal]

Originally Posted by nqk

I did another recount in debug mode and it went through, I don't know in how many hours, then I returned to the normal mode, added a random book. This book shows -2 pages.

And if you right click on book details and trigger a recount of that book does it work?

And another issue: the viewer is all black. And the preview panel in editor is also all black. Content Server viewer is alright

That's a Qt WebEngine compat issue. Update graphics drivers and try turning off hardware acceleration for qt webengine, as described here: https://doc.qt.io/qt-6/qtwebengine-debugging.html

[kovidgoyal]

Originally Posted by Comfy.n

I found an issue with icon themes. Where are all the others? lol.

Unrelated to the beta and fixed.

[Comfy.n]

Originally Posted by kovidgoyal

Unrelated to the beta and fixed.

confirmed fixed

[nqk]

Originally Posted by kovidgoyal

And if you right click on book details and trigger a recount of that book does it work?





That's a Qt WebEngine compat issue. Update graphics drivers and try turning off hardware acceleration for qt webengine, as described here: https://doc.qt.io/qt-6/qtwebengine-debugging.html

1) Relating to the count: I saw in the log a failure to load the Goodsread more tag.... This plugin was removed longtime ago, but the zip still stayed. I manually removed ít, and now the count works. I hope.

2) Thế black screen: Hope you can solve ít.

3) Is there a way to distinguish books with built-in page numbers and those without? Say the page count of those with publisher pagination are marked with the ℗. For example 345 ℗?

[kovidgoyal]

@nqk: No there is no record about how a count is generated from a particular file.

[kovidgoyal]

New beta published 8.99.2 with the following changes:

* Make bookshelf spine height configurable
* Make bookshelf spine text direction configurable
* Allow adding a second line to bookshelf spine via template
* Fix bug in page counting causing incorrect page counts for italic tags
* Add a log of page counting failures, accessible from Preference->Look & feel->Bookshelf
* Turn off GPU acceleration in Qt WebEngine to hopefully fix issues with older windows systems
* Change highlighting of current book in bookshelf to gray when it isnt selected
* Various misc minor bug fixes

I believe this addresses almost all feedback received on the initial beta so
far.

The remaining questions are:
1) Should the default for the cover animation be shift or above?

2) Should the default cover thumbnail on spine be cropped or full

3) Should the minimum spine width be increased when there are two lines on
the spine? This has the downside of reducing width variation between books
and not indicating that a book is very thin. Increasing both minimum and
maximum is another option, however this has the downside of invalidating the
thumbnail cache since it depends on maximum spine width and the two lines
setting is per library not global.

Thanks to everyone for all the testing/bug reports. Phew

[nqk]

Dear Kovid, thank you for your work. My issues so far have been all resolved.

I think the spine widths are not really corresponding to the page count.

I set the spine text to {pages} and it is more obvious to compare. The 1433 doesnt look like it is 10 time "thicker" than the 130-paged one. (the height is the same). In my mind, I think we can set the width of the thickest book as max, then all other books will be scaled accordingly, assuming they have the same height. Or it can be the area of the spine, then with the variable heights, the thin books should be much shorter...

[kovidgoyal]

No no it's not a direct correspondence at all. Ther's a minimum width and maximum width. All books larger than IIRC 1500 pages are max width rest of the books have their widths distributed in the range using IIRC a log function but you should ask @un_pogaz about that.

Dont use {pages} directly, the template has to return a number between 0 an 1 for it to work.

[un_pogaz]

Inded, the pages number transformation to spine width use a logarithmic growth curve, wich mean that pages addition has a bigger impact on the width at lowerst value than the same pages addition for bigger value

100 pages = 24px
200 page = 30px
1000 page = 53px
1100 page = 54px

You see that go 100 to 200 increase the width of 6px, when 1000 to 1100 only add 1px for the same pages addition.

This curve exist because the input range of 1-1500 set the median/in-betwen value to 750 pages, wich is twice above of the very common average book size of 300 pages and will lead that the majority of books would be quite narrow (and only few book with a confortable width)
With this curve the average book of 300 page is 35px width instead of 24px (and remind that the min is 15px, max 60px). So yes, the size is not strictly propotional, but it render better by keeping common book size to confortable size, and still keeping a sens of scall.

[theducks]

99.2 editor now works on my (not W11 qualified i7)
While I will probably not use the shelf view, IMPRESIVE on what was done.

[JSWolf]

Originally Posted by kovidgoyal

New beta published 8.99.2 with the following changes:

* Turn off GPU acceleration in Qt WebEngine to hopefully fix issues with older windows systems

Can you please make this an option? I would like to use the GPU.

[JSWolf]

Originally Posted by nqk

Dear Kovid, thank you for your work. My issues so far have been all resolved.

I think the spine widths are not really corresponding to the page count.

I set the spine text to {pages} and it is more obvious to compare. The 1433 doesnt look like it is 10 time "thicker" than the 130-paged one. (the height is the same). In my mind, I think we can set the width of the thickest book as max, then all other books will be scaled accordingly, assuming they have the same height. Or it can be the area of the spine, then with the variable heights, the thin books should be much shorter...

Please attach your image. That way it will always be here is anyone wants to see it and it won't automatically open another tab. Thanks.