Per library settings for hierarchy and partitioning

[BetterRed]

Would it be possible to add Per Library tweaks for two Look & Feel->Tag browser settings:

• Categories not to partition:
• Categories with hierarchical items:

Ideally, they would be check boxes in the column definitions but that would presumably mean changes to table definitions in the database schema Ψ³

BR

[chaley]

Originally Posted by BetterRed

Would it be possible to add Per Library tweaks for two Look & Feel->Tag browser settings:

• Categories not to partition:
• Categories with hierarchical items:

Ideally, they would be check boxes in the column definitions but that would presumably mean changes to table definitions in the database schema Ψ³

BR

Hierarchy is already per library. Earlier this week I submitted changed to Kovid to make partition settings per library, and to set them both with check boxes.

[BetterRed]

Originally Posted by chaley

Hierarchy is already per library. Earlier this week I submitted changed to Kovid to make partition settings per library, and to set them both with check boxes.

Must have been some inter-galactic mind-reading going on.

Has Hierarchy always been per library, I somehow ended up with custom column names in that list for Library A that have never existed in Library A.

be good to have a visual clue to differentiates global and per library settings - e.g underline per library field labels - might be hard to enforce though.

BR

[chaley]

Originally Posted by BetterRed

Must have been some inter-galactic mind-reading going on.

Has Hierarchy always been per library, I somehow ended up with custom column names in that list for Library A that have never existed in Library A.

be good to have a visual clue to differentiates global and per library settings - e.g underline per library field labels - might be hard to enforce though.

BR

Moderator Notice
Moved to its own thread https://www.mobileread.com/forums/sh...d.php?t=348763

[chaley]

Originally Posted by BetterRed

Must have been some inter-galactic mind-reading going on.

The changes were related to an @ownedbycats enhancement request -- use checkboxes in look&feel to set category order. Hierarchy and categorization followed naturally

Has Hierarchy always been per library, I somehow ended up with custom column names in that list for Library A that have never existed in Library A.

Yes, but because it was a manually typed list you could put anything you wanted there. Columns in the list but not in the library were ignored.

be good to have a visual clue to differentiates global and per library settings - e.g underline per library field labels - might be hard to enforce though.

BR

The goal is to eventually move anything that references columns (usually via lookup names) or other specific library data to a per-library setting (a db setting). Things that are "general" UI settings, for example line spacing, remain as user-level settings. And yes, I recognize that the choice of where to put a setting is sometimes not obvious.

Also yes, marking db vs user settings would be a can of worms. First problem is figuring out which is what. Second problem would be maintaining the UI as the settings migrate. I don't want to go there.

[ownedbycats]

Originally Posted by BetterRed

be good to have a visual clue to differentiates global and per library settings - e.g underline per library field labels - might be hard to enforce though.

BR

Perhaps tooltips?

[chaley]

Originally Posted by ownedbycats

Perhaps tooltips?

Same problems: determining which does what and then maintaining them. As I said, I don't want to go there.

[BetterRed]

Originally Posted by chaley

. . .
Yes, but because it was a manually typed list you could put anything you wanted there. Columns in the list but not in the library were ignored.
. . .

That explains it, and gives me comfort that at least a few neurons are still functioning.

Originally Posted by chaley

Same problems: determining which does what and then maintaining them. As I said, I don't want to go there.

Having been confronted with something similar in the long ago past I suspected you mightn't.

BR