MobileRead Forums - View Single Post

chaley · 02-11-2016, 05:15 AM

CC V5.0.0.1 has been released on the CC alpha channel.

It is moderately difficult to write the change log for this release because so much has been changed. What follows is a summary in no particular order:

Dropped support for Gingerbread and Honeycomb (Android 2 and 3)
Changed to newest Google tools and libraries. This change touches most of CC's user interface, usually is subtle ways, because the new tools try to enforce some "Material Design" guidelines. For example, the action bar is a bit different, dialog buttons have moved around a bit, and some animations have come or gone. It is this change that introduces the most risk that I broke something.
Use Android's Storage Access Framework (SAF) when CC is running on Android 5 (Lollipop) or higher. This permits storing your library in arbitrary folders on the SD card. When you go to Settings / Formats and Folders and tap an extension or the default line, CC opens an Android folder chooser instead of the existing one. Note that I have no control at all over that chooser dialog.

The app-private-folder hack is now only necessary on Android 4.4 (Kitkat).

The tools and library changes were necessary to make this work.
E-ink corrections now work somewhat differently, although as far as I can tell they still work.
The settings screeen(s) have reverted back to the "standard" for the android theme.
Add a transition animation from the book list to book details. Don't do the animation if e-ink corrections are enabled. Add an option in Settings / Book details to disable the animation.
Move the cloud connection database cache out of the library, instead storing it in the app private folder on the SD card if there is one, otherwise in main memory. This was required because of the change to use the SAF. As far as I can tell one cannot put a database in a folder managed by SAF.
Handle Android 6 asking for permissions at run time instead of install time.
Add an option in Settings / File names to remove accents (diacritical marks) on characters used in path names. This does not "ascii-fy" the path. It just removes accents. Exactly what is an accent is defined by the ICU (International Components for Unicode) consortium.
Add Android 6 auto-backup support. I have no idea if it works at all. It doesn't on my Nexus 5. There is a lot of chatter saying that one must do a system reinit after an upgrade to make it work and I am unwilling to do that on my "production" phone.

If it works then it will backup CC's settings. The database is too large.

FWIW: I think a better solution is to use CC's backup, saving the file to a folder that is auto-synced to some cloud provider.
Changes to strings to (I hope) make the Onesky translation tools work better.
Updated languages: French, Russian, Spanish. Some, perhaps all, of these updates were triggered by the changes I made to strings.
[BUG FIX]Make CC really able to open azw3 files with FBReader

@Translators: I will upload the new strings once I get some feedback on this version.

Re dropping support for Android 2 and 3: CC version 4 will remain on Google Play and will be offered to the these devices. Android 4 and higher will automatically be offered CC version 5. I don't intend to continue development of V4, but I will fix egregious bugs.

02-11-2016, 05:15 AM	#1
chaley Grand Sorcerer Posts: 12,471 Karma: 8025600 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	V5.0.0 alpha channel release CC V5.0.0.1 has been released on the CC alpha channel. It is moderately difficult to write the change log for this release because so much has been changed. What follows is a summary in no particular order: Dropped support for Gingerbread and Honeycomb (Android 2 and 3) Changed to newest Google tools and libraries. This change touches most of CC's user interface, usually is subtle ways, because the new tools try to enforce some "Material Design" guidelines. For example, the action bar is a bit different, dialog buttons have moved around a bit, and some animations have come or gone. It is this change that introduces the most risk that I broke something. Use Android's Storage Access Framework (SAF) when CC is running on Android 5 (Lollipop) or higher. This permits storing your library in arbitrary folders on the SD card. When you go to Settings / Formats and Folders and tap an extension or the default line, CC opens an Android folder chooser instead of the existing one. Note that I have no control at all over that chooser dialog. The app-private-folder hack is now only necessary on Android 4.4 (Kitkat). The tools and library changes were necessary to make this work. E-ink corrections now work somewhat differently, although as far as I can tell they still work. The settings screeen(s) have reverted back to the "standard" for the android theme. Add a transition animation from the book list to book details. Don't do the animation if e-ink corrections are enabled. Add an option in Settings / Book details to disable the animation. Move the cloud connection database cache out of the library, instead storing it in the app private folder on the SD card if there is one, otherwise in main memory. This was required because of the change to use the SAF. As far as I can tell one cannot put a database in a folder managed by SAF. Handle Android 6 asking for permissions at run time instead of install time. Add an option in Settings / File names to remove accents (diacritical marks) on characters used in path names. This does not "ascii-fy" the path. It just removes accents. Exactly what is an accent is defined by the ICU (International Components for Unicode) consortium. Add Android 6 auto-backup support. I have no idea if it works at all. It doesn't on my Nexus 5. There is a lot of chatter saying that one must do a system reinit after an upgrade to make it work and I am unwilling to do that on my "production" phone. If it works then it will backup CC's settings. The database is too large. FWIW: I think a better solution is to use CC's backup, saving the file to a folder that is auto-synced to some cloud provider. Changes to strings to (I hope) make the Onesky translation tools work better. Updated languages: French, Russian, Spanish. Some, perhaps all, of these updates were triggered by the changes I made to strings. [BUG FIX]Make CC really able to open azw3 files with FBReader @Translators: I will upload the new strings once I get some feedback on this version. Re dropping support for Android 2 and 3: CC version 4 will remain on Google Play and will be offered to the these devices. Android 4 and higher will automatically be offered CC version 5. I don't intend to continue development of V4, but I will fix egregious bugs.