CC V5.0.1 beta channel release

[theducks]

Originally Posted by chaley

Regarding this change to CC

• Change the default template to {title} - {authors} ({id}) to ensure that books cannot overwrite each other in the rare case that two books have the same title and author. This is also calibre's default template. The default template is used by the content server and cloud connections if no options are checked in Settings / File names.

I am wondering whether this change is a good idea. Although it does solve a very rare problem, it is also arguably a "change for change sake" because the problem happens almost never (if ever).

The problem: the change could break CC file names for people who changed the file template in the wireless driver to be the same as the (old) default CC template ({title} - {authors}) because the change makes the content server and cloud connections use different names.

Does anyone think that the change is a good thing and that I should leave it there?

IMHO a poor idea (that I used on my PEz, which used filenames only, until it bit me)
{id} assumes that the calibre Library does not change (frozen)
Any number of activities will result in what is thought simply as 'My Library' (as in, I only have one) to get renumbered, thus many dupes if {id} is the official tie breaker.
I don't have a good idea around this UUID is internal to the book and not a simple template tool

[chaley]

Originally Posted by Purple Lady

Can you leave it so someone can still navigate up from main memory? This way rooted users would still be able to store to the external SD. When a rooted device has the SDfix applied storage works like it used to before Kitkat with no changes needed to CC. I always wondered what the changes you made in CC for rooted users did since I never had it checked and was still able to use the external SD card.

The option controls the folder navigation in formats and folders. Before V5 you would have had to check it if you changed the folder on a kitkat-or-later device. It never had any effect on backups.

The fact that one could navigate out of main memory when making backups was a bug. That said, I will continue to allow it. The worst that happens on unrooted devices is that the backup fails.

[chaley]

Originally Posted by Purple Lady

I would say since the change could break things you shouldn't do it.

Originally Posted by theducks

IMHO a poor idea (that I used on my PEz, which used filenames only, until it bit me)
{id} assumes that the calibre Library does not change (frozen)
Any number of activities will result in what is thought simply as 'My Library' (as in, I only have one) to get renumbered, thus many dupes if {id} is the official tie breaker.
I don't have a good idea around this UUID is internal to the book and not a simple template tool

Both good points. I will back out the change.

@Translators: sorry about the extra work. I will fix (revert) the French and Spanish phrases.

[Purple Lady]

Originally Posted by chaley

The option controls the folder navigation in formats and folders. Before V5 you would have had to check it if you changed the folder on a kitkat-or-later device. It never had any effect on backups.

The fact that one could navigate out of main memory when making backups was a bug. That said, I will continue to allow it. The worst that happens on unrooted devices is that the backup fails.

I am on the latest prod version on my Tab S which is still Kitkat, and it allows me to choose SD card and pops up a message. I don't have the SD option checked currently, but may have in the past.

Thanks for leaving the navigation for backups.

[chaley]

Originally Posted by Purple Lady

I am on the latest prod version on my Tab S which is still Kitkat, and it allows me to choose SD card and pops up a message. I don't have the SD option checked currently, but may have in the past.

The option removes the "Use SD Card" button and eliminates that warning, provides a button that lets you navigate to the top (/), and then go anywhere from there.

On V5 the "Use SD card" button only appears on Kitkat. Lollipop and up use SAF, and Jellybean and down use the full navigator.

[chaley]

Change log:

• Clean path names when moving books between folders. Needed because older versions of CC allowed trailing periods in folder names, and these are illegal when using the "Storage Access Framework" with an SD card. The path is scanned and made "legal", then the book record is updated to use that new path.
• Back out the changes to the default template. It is now as it was in V4: {title} - {authors}

Given the lack of problems, this will likely be the last beta release.

I will probably release it to "production" near the end of next week. My thought is to use Google's "staged release" mechanism, where I get to choose what percentage of users are offered the upgrade. The goal is to avoid as much as possible unpleasant surprises that affect everyone.

@Translators: I am having a bit of a problem with Onesky. In some cases corrections to existing translations are not permitted. I hope that this will be resolved quickly.

[NSILMike]

I am installing now.
Connects wirelessly and to content server just fine, and syncs just fine in wireless device mode.

[Purple Lady]

I just downloaded a book using the Dropbox connection and it created a folder ending in a period.

[Purple Lady]

I just did another from Dropbox and this one stripped the period. This one was J. A. Konrath instead of just J. Konrath.

[chaley]

Originally Posted by Purple Lady

I just downloaded a book using the Dropbox connection and it created a folder ending in a period.
Attachment 146909

Yet another special case.

The result of the template exceeded the maximum path length. In that case each segment in the path is trimmed by a computed percentage so that the path length is less than or equal to the maximum. My problem: the trimmed segments are not re-verified to be sure that they are still legal. This is what allowed that folder to be created.

BTW: I think the folder ends in a space not a period, but that doesn't change anything.

[nqk]

Dear @chaley,

On cloud connection, let's say I'm in a Book Detail page and I tap on Author, for example, CC brings me to the list of books by that Author. However, is it not possible to go back quickly to the Book Detail page by using Back button?

[chaley]

Originally Posted by nqk

Dear @chaley,

On cloud connection, let's say I'm in a Book Detail page and I tap on Author, for example, CC brings me to the list of books by that Author. However, is it not possible to go back quickly to the Book Detail page by using Back button?

No. The back button in the cloud connection works like the back button in the main booklist, taking you up a level in the current grouping even if you arrived at that grouping by tapping something in book details.

Of course, we could have made the choice that the back button does something else, such as go back to wherever you were before. Each choice would have its partisans and detractors. I am going to stick with what we have.

[nqk]

Any other way to go back?

[chaley]

Originally Posted by nqk

Any other way to go back?

The book you came from is by definition shown in the list. Tap on it.

[chaley]

Change log:

• CC now collects non-personal usage statistics. The first time you start CC after the upgrade you will see a dialog mentioning this and explaining how to opt out (I hope you don't). See our Privacy Policy for more information.
• Add some space between the Read and Delete buttons in Book Details
• [BUG FIX]Fix possible generation of an illegal path if a path exceeds the length limits.
• [BUG FIX]Really fix the problem where cloud book details might not show all metadata.

The reason for the statistics (analytics): we are at the point where development choices must be better informed by how people really use CC. For example, there is discussion in this thread about how one might improve CC by fullyt integrating the cloud connection. One problem: we don't know with any certainty how many people actually use the cloud connection. We do know that less that 4% of CC users have connected to a library on Dropbox, which implies that usage of the cloud connection is quite low.

I have tried very hard not to collect personal information or even non-personal information that could be aggregated to become personal. I hope that people don't choose to opt out.