Question for the prerelease community

[Purple Lady]

Originally Posted by chaley

My intention would be to make intermediate releases to the alpha group once I have new functions/change that are internally tested. These releases might happen once a week, faster if comments call for it, slower if I am feeling lazy or traveling.

The beta group would get releases a week or two before I intend to make a general release, which generally happen every three months or so. The hope is that the beta releases are very close to production, and because of that I will be much less willing either to add new functionality at that point or to change them for anything that isn't a bug. Of course, the definition of "bug" is mutable.

a_daley's comment about backups is a good one. There is no guarantee that one can revert to an older release without doing a total uninstall. Reasons: releases change both the database structure and the meaning of settings, and reverting won't revert those changes. In general, doing a CC settings backup before upgrading will suffice unless there is also a database upgrade, but I can't guarantee this. And it is worth noting that this has always been true for prereleases. Having an alpha group won't change that.

If you use Titanium Backup it can restore even db changes if you restore app + data. I would do the alpha group if you have one. I do weekly backups so I wouldn't lose a lot even if I did revert.

[chaley]

Originally Posted by PatNY

To veer a little off topic, I was just wondering how much of the future enhancements/changes in CC will be dependent on having Calibre 2.0 or higher. I have avoided updating Calibre because I read 2.0 is incompatible with XP, and I am still on XP on multiple computers. I am happy with Calibre 1.40 and don't feel the need to update that, but if it prevents me from enjoying new CC features in the future, then I may rethink things.

--Pat

I just realized that XP is a bigger problem than I had thought. Calibre 2.1 includes changes to send information to CC about what custom columns are defined. CC (now) uses this information to generate pick lists for columns to group on and columns for is-read syncing. I had carefully removed the old text-base code, thinking that it shouldn't ever be used. However, XP users cannot run that update and therefore cannot use the new pick lists. I will need to keep the old code as a fall back.

In addition, the feature I will add to change what is displayed on the book list will use the same pick lists. I won't develop a text-based interface for that because I am not taking away something the user already had. Instead they won't get access to the new feature. There are likely to be other cases like this, although I can't think of one at the moment.

[jackie_w]

To your original question re: frequency - I have no strong feelings either way. I'm happy with whatever you'd prefer yourself.

Regarding alpha vs beta. In principle I'm happy to be in an alpha group if all I need to worry about is backing up CC's settings before I start. If I need to be rooted and do full system backups to protect my other Android apps, then I'll need to stick with the beta group. Low-level Android tinkering is outside my comfort zone.

[PatNY]

Originally Posted by chaley

I just realized that XP is a bigger problem than I had thought. Calibre 2.1 includes changes to send information to CC about what custom columns are defined. CC (now) uses this information to generate pick lists for columns to group on and columns for is-read syncing. I had carefully removed the old text-base code, thinking that it shouldn't ever be used. However, XP users cannot run that update and therefore cannot use the new pick lists. I will need to keep the old code as a fall back.

In addition, the feature I will add to change what is displayed on the book list will use the same pick lists. I won't develop a text-based interface for that because I am not taking away something the user already had. Instead they won't get access to the new feature. There are likely to be other cases like this, although I can't think of one at the moment.

I am not sure I understand the current limitations in CC of not being on Calibre 2.x. So far are they limited to this? ...

1 - can't group on custom columns
2 - can't sync "read" field
3 - can't change what is displayed in book list view
4 - can't use the "wireless device template ... " option implemented in last update

And are you saying you will put back #1 and #2 into the next CC release?

I have never used list view in CC, don't group on custom columns, and always use the author-title for filenames. So the only item that appears to impact me is #2, but if you put it back in, then it won't matter that I am not on Calibre 2.x. Is that correct??

I have two more almost finished, auto-sync changed books (the book file itself) and temp-mark books that have had read information synced. Compatibility with USB connections may require calibre changes.

Ahhh, ok. Now the ability to auto-sync changed books is something I would really really like. For that I will have to re-think moving to another version of Windows. Do you have an ETA for that feature in CC? Not for testing but for being fully implemented?

I don't anticipate ever using USB connections and I don't understand what "temp-mark books that have had read information synced" means for CC. Is that important?

This is another argument for two communities, alpha and beta. Having both alpha and beta groups is supported by google so I could do that.

I'd like to keep having input when it comes to GUI options and features. So I assume I can sign up for the alpha group and just not download them unless there is a GUI-related issue I am interested in? I would download mostly the betas. I have Titanium Backup (root) so I would be sure to back up everything before downloading any alpha release.

--Pat

[chaley]

Originally Posted by jackie_w

Regarding alpha vs beta. In principle I'm happy to be in an alpha group if all I need to worry about is backing up CC's settings before I start. If I need to be rooted and do full system backups to protect my other Android apps, then I'll need to stick with the beta group. Low-level Android tinkering is outside my comfort zone.

In my two years of developing CC I have never had a case where I had to do a system restore. I also have never had a case where CC's database was destroyed.

What I have had happen:
- mistakes where I messed up migrating preferences to the point where regenerating them from scratch was easier than trying to fix them. A preferences backup will take care of that, and in any event I don't think it is likely that I would release something that did this.
- changes to the database that didn't work out. One deficiency of SQLite, the db used by Android and lots of other SW including calibre, is that there is no way to undo changes that added information to the db. The easiest way to fix these is to reinitialize (clear data). This has happened 3 or 4 times, and never in a prereleased CC.

My intention is to release features as I build them and after I have tested them instead of holding them in abeyance for the period just before the production release. The risk of corruption should be low. On the other hand, it could be that the community decided that the way I did it isn't optimal, and correcting it might be best done with a reload, although I think this would be extremely rare. Hasn't happened yet.

Waiting a few days for other masochists alpha testers report is not a silly idea. I think doing that reduces risks to more than acceptable levels. Of course, if *everybody* waits then it doesn't, but that won't happen.

[chaley]

Originally Posted by PatNY

I am not sure I understand the current limitations in CC of not being on Calibre 2.x. So far are they limited to this? ...

1 - can't group on custom columns
2 - can't sync "read" field
3 - can't change what is displayed in book list view
4 - can't use the "wireless device template ... " option implemented in last update

And are you saying you will put back #1 and #2 into the next CC release?

The only limitation in released CC V3.4.4 is number 4. Number 3 isn't released yet (isn't developed yet).

The problem presented by numbers 1 and 2 relate to defining the column for the feature, not using the feature. In the current release you must type by hand the lookup names of the keys. In the code I have finished you can pick the lookup names from a list, and I (in error) removed the ability to type the names. That is what I added back.

I have never used list view in CC, don't group on custom columns, and always use the author-title for filenames. So the only item that appears to impact me is #2, but if you put it back in, then it won't matter that I am not on Calibre 2.x. Is that correct??

Given those facts, yes.

Ahhh, ok. Now the ability to auto-sync changed books is something I would really really like. For that I will have to re-think moving to another version of Windows. Do you have an ETA for that feature in CC? Not for testing but for being fully implemented?

It is implemented and working now. However, the calibre side of the code didn't make it into this weeks release, so even if I made an alpha release today it would take a week before it could be used.

I don't anticipate ever using USB connections and I don't understand what "temp-mark books that have had read information synced" means for CC. Is that important?

The temp-mark feature is important for people who want to make metadata changes in calibre after they read a book. The common examples are to change the book's rating, add or remove tags, add or remove from an "I'm reading" list (however that is implemented), or in some cases even delete the book format.

The problem people face with the current implementation is that it could be weeks between when they finish a book and when they sync with calibre, and they don't remember which books might have changed since the last time they synced. Setting a temp-mark is purely an aide-memoire, telling the user that the marked books had their is-read information changed to what is in CC. You see a temp-mark as a pushpin next to the book. If you add "temporary marks" to calibre's interface somewhere (I prefer the context menu) then you can search for marked books, clear marks, add marks, etc. Marks are erased when you exit calibre, which is why they are called "temporary".

I'd like to keep having input when it comes to GUI options and features. So I assume I can sign up for the alpha group and just not download them unless there is a GUI-related issue I am interested in? I would download mostly the betas. I have Titanium Backup (root) so I would be sure to back up everything before downloading any alpha release.

--Pat

Fine with me. There is no reason someone needs to download a particular release if there is nothing there they want or if their interest isn't piqued by the discussion.

[chaley]

I have created the alpha group and added people who indicated they wanted to be on it. People in the alpha group are also in the beta group. You should have received an email to this effect. If you think you said you wanted to be in the group and did not receive a message saying you have been added to the calibre companion alphas group, send me a PM.

@PatNY: I didn't add you for two reasons. First, I wasn't sure if you wanted to be added. Second: I can't identify which email address is yours. If you want to be added then please send me a PM with your google email address.

@Everyone else: if you want to be in the alpha group please send me a PM.

[kaufman]

Chaley, do you know when you plan to release the next alpha? Some of us, (well at least me anyhow) are very excited to get it.

[chaley]

Originally Posted by kaufman

Chaley, do you know when you plan to release the next alpha? Some of us, (well at least me anyhow) are very excited to get it.

Today.