Permalink
Browse files

Updated Readme and Chanelog.

  • Loading branch information...
David Marmor
David Marmor committed Nov 3, 2016
1 parent a2965f0 commit 8cd0d76a18ad94edae40dfbd18200ae08b6813b5
Showing with 13 additions and 4 deletions.
  1. +6 −4 README.md
  2. +7 −0 app/CHANGELOG.md
View
@@ -1,6 +1,6 @@
# Epichrome 2.1.15
# Epichrome 2.1.16
###If you've been using version 2.1.13 or below, please see [important note](#important-note-on-updating) below!
###If you've been using version 2.1.13 or earlier, please see [important note](#important-note-on-updating) below!
**Epichrome** is made up of two parts: an AppleScript-based Mac application (*Epichrome.app*) and a companion Chrome extension (*Epichrome Helper*). *Epichrome.app* creates Chrome-based site-specific browsers (SSBs) for Mac OSX (Chrome must be installed in order to run them, but they are full Mac apps, each with its own separate Chrome profile).
@@ -26,15 +26,17 @@ See [CHANGELOG.md](https://github.com/dmarmor/epichrome/blob/master/app/CHANGELO
*Note: In general, it's a good idea to keep a backup of your Epichrome apps in case updates do break them. The epichrome_fix.sh script now included in the DMG is the easiest way to do this. Otherwise, you can just right-click on each app in the Finder and select Compress. Then if anything goes wrong, you can always delete the app and double-click the zip archive to recreate it intact.*
## New in version 2.1.15.
## New in version 2.1.16.
*Note: I'm currently only addressing bugs at the moment. My day job has gotten very busy, so I probably won't have time to work on new features or major updates for the foreseeable future.*
Version 2.1.14 changes the way Epichrome apps update themselves. They now attempt to update to the latest Epichrome engine _before_ updating themselves to the latest version of Chrome. Doing it the other way around was causing problems if people had installed a current version of Epichrome but hadn't updated their apps before a new version of Chrome was installed. Thanks to [gnyrd](https://github.com/gnyrd "gnyrd") and everyone else who noticed and helped diagnose this problem.
2.1.14 also has brand-new icon-creation code, now able to handle JPG, GIF and other input file formats with indexed color or without alpha channels. And as a bonus, it also creates custom document icons based on the custom app icon. Thanks to [io41](https://github.com/io41 "io41") and [freewind](https://github.com/freewind "freewind") for identifying the shortcomings with the old icon code.
And finally, in 2.1.15 the code that checks github for new versions will no longer insist that there's a new version on github even though the app just been updated to that new version.
In 2.1.15 the code that checks github for new versions will no longer insist that there's a new version on github even though the app just been updated to that new version.
Finally, 2.1.16 finally squashes the bug that caused those failed Chrome updates to destroy the entire app. From now on, even if a Chrome update fails, the app should stay intact.
See [CHANGELOG.md](https://github.com/dmarmor/epichrome/blob/master/app/CHANGELOG.md "CHANGELOG") for more details.
View
@@ -1,10 +1,17 @@
# Epichrome.app Change Log
This project adheres to [Semantic Versioning](http://semver.org/).
## [2.1.16] - 2016-11-03
### Fixed
- Finally squashed the bug that caused those failed Chrome updates to destroy the entire app. From now on, even if a Chrome update fails, the app should stay intact.
## [2.1.15] - 2016-11-01
### Fixed
- Fixed a small bug in the code that checks github for new versions. Apps will no longer insist that there's a new version on github even though they've just been updated to that new version.
## [2.1.14] - 2016-11-01
### Changed
- Epichrome apps now attempt to update themselves to the latest Epichrome engine _before_ updating themselves to the latest version of Chrome. Doing it the other way around was causing problems if people had installed a current version of Epichrome but hadn't updated their apps before a new version of Chrome was installed. Thanks to [gnyrd](https://github.com/gnyrd "gnyrd") and everyone else who noticed and helped diagnose this problem.

0 comments on commit 8cd0d76

Please sign in to comment.