Beta testers for calibre 9 needed

[JimmXinu]

Originally Posted by un_pogaz

Ah, yep don't work like that.
The template require a decimal value bettwen 0.0 to 1.0 (min/max), so put it a raw field dosn't work. {pages} work because Calibre detect it as a special field and do a transform behind.

It does what?

It is, IMO, unreasonable to assume the user will figure out that template should be 0.1 to 1.0 when the default is just "{pages}". Yes, there's a tooltip. In my experience, many users don't read them.

Either do that processing for every numeric template, or provide the full version you just posted as the default. I'd remove the edit template box and require using the full template editor for that.


This is a lot of drama for the 'cute vision effect' of proportional book thickness on an optional display view.

I would just use the existing size column. You already made it a configurable template, so people who want to use pages instead could do so with a custom column and Count Pages. People have opinions about page counts.

[Dal Bhat]

This is a lot of drama for the 'cute vision effect' of proportional book thickness on an optional display view.

I would just use the existing size column.

This.

[Terisa de morgan]

Originally Posted by JimmXinu

People have opinions about page counts.

A LOT

[un_pogaz]

Originally Posted by ownedbycats

Suggestion: For covers, maybe option for additional blur if not bad performance? It may look better.

Originally Posted by JimmXinu

It does what?

It is, IMO, unreasonable to assume the user will figure out that template should be 0.1 to 1.0 when the default is just "{pages}". Yes, there's a tooltip. In my experience, many users don't read them.

Either do that processing for every numeric template, or provide the full version you just posted as the default. I'd remove the edit template box and require using the full template editor for that.

@ownedbycats you mean for the thumbnail?

@JimmXinu that a point. So their is a big button marked "Use a custom column", but I see how the use of {page} as a special template is not a intuitive example to edit the template. And I agree that tooltip are not very read.
Maybe show the tooltip text into a label, so that it could easly view.

In both case, is not to me to decide such thing, but Kovid.

[DNSB]

Originally Posted by fogice

Ah well, and I was looking forward to seeing what a 12,487 page book would do to my bookshelf.

Originally Posted by fogice

(Honestly, I plan to turn this feature on, play with it for 5 minutes, then turn it off. I hope the feature is greatly enjoyed and appreciated by other people.)

Much the same here. I much prefer the text display but am playing with the bookshelf view just for fun and to see if I can find any real issues with it. I do know some people who use cover grid view and would love the bookshelf view.

[JSWolf]

Actually, I just had a good idea to make the new bookshelf view better.

1. Get rid of cover grid view
2. Use the cover grid icons in the bookshelf view
3. Remove the new {pages} column
3. DONE!

This way we see the covers, but they are in a bookshelf type view.

[DNSB]

So you want a bookshelf view showing the front cover of the book instead of the spine? This would take even more space than the current cover grid view to be able to draw the shelves. Not to mention, how many people store their physical books in a bookshelf with the front covers on view?

We might also want to consider the limitations on the number of books visible in cover grid view. On my system with 3 shelves visible, I get 78-86 books on screen. With the default view, I get 30 books visible with a lot more information visible. With cover grid, I get 21 cover fully visible plus 7 that are about 50% visible.

So my vote on your suggestion:

[JimmXinu]

Originally Posted by un_pogaz

@JimmXinu that a point. So their is a big button marked "Use a custom column", but I see how the use of {page} as a special template is not a intuitive example to edit the template. And I agree that tooltip are not very read.
Maybe show the tooltip text into a label, so that it could easly view.

In both case, is not to me to decide such thing, but Kovid.

I didn't see / remember that button. It's a significant help.

OTOH, the dialog dropdown after that clicking "Use a custom column" shows all the standard columns first, then the custom columns...?

[JSWolf]

I just found a nice bug. It happens when I am in the bookshelf view and I use the pg dn key to scroll.

calibre, version 8.99.4
ERROR: Unhandled exception: <b>AttributeError</b>:'BookCase' object has no attribute 'num_shelves'

calibre 8.99.4 Portable embedded-python: True
Windows-11-10.0.26200-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '11', '10.0.26200')
Python 3.14.2
Windows: ('11', '10.0.26200', 'SP0', 'Multiprocessor Free')
Interface language: None
EXE path: C:\Calibre Portable\Calibre\calibre.exe
Successfully initialized third party plugins: DeACSM (0, 0, 16) && Gather KFX-ZIP (from KFX Input) (2, 28, 0) && DeDRM (10, 0, 15) && Package KFX (from KFX Input) (2, 28, 0) && Annotations (1, 17, 13) && Apple Books covers (1, 1, 0) && Backup Configuration Folder (1, 1, 2) && Barnes & Noble (1, 5, 7) && BookFusion Plugin (0, 8, 1) && Count Pages (1, 14, 4) && Diaps Editing Toolbag (0, 5, 0) && EpubCheck (0, 2, 6) && EpubMerge (3, 2, 0) && EpubSplit (3, 12, 0) && Favourites Menu (1, 3, 1) && Find Duplicates (1, 10, 9) && Hyphenate This! (0, 1, 4) && KFX metadata reader (from KFX Input) (2, 28, 0) && From KFX (2, 28, 0) && KFX Input (2, 28, 0) && Set KFX metadata (from KFX Output) (2, 18, 0) && KFX Output (2, 18, 0) && Kindle hi-res covers (0, 5, 1) && KindleUnpack - The Plugin (0, 83, 8) && Kobo Metadata (1, 12, 0) && Kobo Utilities (2, 25, 0) && Modify ePub (1, 8, 8) && Quality Check (1, 14, 6) && Reading Goal (2, 0, 7) && Reading List (1, 15, 6) && ScrambleEbook (0, 6, 0) && StoryGraph (2, 0, 7) && TextDiff (1, 3, 1)
Traceback (most recent call last):
  File "calibre\gui2\library\bookshelf_view.py", line 2115, in keyPressEvent
  File "calibre\gui2\library\bookshelf_view.py", line 1167, in book_in_column_of
AttributeError: 'BookCase' object has no attribute 'num_shelves'

[ownedbycats]

Not to do with bookshelves, but notice coumns MDE not equal height and looks odd

It also affects series number and published and date

[BetterRed]

Selecting books:

Multiple adjacent books can be selected with Shift+right/left arrow OR Ctrl+right/left arrow OR Ctrl+Shift+right/left arrow. How do I select multiple non-adjacent books?

In vertical lists (List view, Book Editor File browser etc) Shift+up/down arrows is used to select adjacent items and Ctrl+up/down arrows,Space is used to select non adjacent items.

Group by

Now the Group by button has been moved from the Context menu to the Search bar could it have a keyboard shortcut… no need for a default.

In dark mode, the Group by dividers are a rather indistinct, suggest they be off-white with dark grey text, full height of shelf with text top justified

Spine widths

Rather than the fraction in the spine width template, add a Fixed width spine checkbox. If checked activate a slider widget and let the user use it to set the width visually, and deactivate (grey out) the Spine width template widgets. Vice versa if it's not checked.

If a library uses this option there should be no need to calculate and maintain the 'pages' cache or interpret a spine width template.

BR

[un_pogaz]

Kovid just do a change to ensure that is not a incorect template for the spine width (show a waring and confirmation dialog)
https://github.com/kovidgoyal/calibr...1ce1aec313e9d9

@JimmXinu, the same commit enfore a alphabetical order when choosing column. I appreciate your idea, but I think it kind of reponse of it.

@BetterRed
Group by: I note for the color issue. But with do you mean by "full height of shelf with text top justified"? (I'm a visual guy, a Paint drawing will be good, thanks)

Spine widths: 1) something could be done, nut it a bit overcomplicated for not that much. I will do a proposal, but not sure if Kovid will valid it.

2) No, because "maintain the 'pages' cache" for every books added is not a issue. Calibre Pages is fast, do in background, and so their is no cost to keep it up to date when a change is detected. The only moment when the pending queue is a bit annoying is for library that prexiste before Calibre 9 or if a all recount is asked by the user. But once that the all library is perform, or for new library, this done in a transparent manner.
Take a bit of time, for sure, but nothing that require that.
Also, maintain the 'pages' cache for every books avoid to have invalid value if a user want to use the Calibre Pages in a template else where, but use it on a book that was not scanned.
It's a dilemma "Do you want solve the issue now, or report it and risk others stranger issue later?" Choice a was made to now.

[un_pogaz]

Bug report: When using the "All action menu", popup submenu of the requested action fail to show:

qt.qpa.wayland: Failed to create grabbing popup. Ensure popup  QWidgetWindow(0x561171f1b840, name="QMenuClassWindow") has a transientParent set and that parent window has received input.

Arch Linux.

[JSWolf]

If we just have a fixed width for all the books, we can do away with the new Pages column.

[kovidgoyal]

Originally Posted by un_pogaz

Bug report: When using the "All action menu", popup submenu of the requested action fail to show:

qt.qpa.wayland: Failed to create grabbing popup. Ensure popup  QWidgetWindow(0x561171f1b840, name="QMenuClassWindow") has a transientParent set and that parent window has received input.

Arch Linux.

QT_QPA_PLATFORM=xcb