So it becomes preferable to store everything in PNG and source things from disk in the exact same way as 1Password 3, and only contact the icon-server as a fallback for items that completely lack icons. From that, we can observe that the user's local app icons, pulled straight from the applications on disk, are always going to be more reliable than the icon-server fallback. This means that for the 6 or so icons it did have, about half are wrong. For OmniFocus it contains some older icon, etc. ![]() For BetterTouchTool it contains a very old version of the icon. For instance, for Xee3, the icon-server contains the Xee2 icon. For the handful of icons that it did have, it had older versions of the application icons. The icon server is still best thought of as a fallback. We're talking about 1-2 megabytes of PNGs for my 109 app icons. As if that wasn't enough, there's another great win: The icons will be guaranteed to look gorgeous everywhere.Īnd remember: The slight extra size of the PNG icons doesn't matter broadband and WiFi is fast these days, and they only need to be transferred on the first sync. It then also becomes trivial to do two-way syncing with the folder-sync AgileKeychain format (which uses PNG), so that all icons stay in sync across all versions and installations of 1Password. Thus preserving every custom icon the user may have (and augmenting things by pulling in icon-server icons wherever the user lacked icons). If a universal upgrade back to PNG quality was done, it would then become trivial to import all 1Password 3 PNG app icons upon first opening an old AgileKeychain in 1Password 4. My suggestion is to completely do away with the JPG fallback (it doesn't save any meaningful space, it loses all transparency, and it just leads to blurry icons as seen above), and instead save all custom icons as PNG - just like in 1Password 3. What's not clear from the changelog if is the PNG size ceiling was raised, or if the JPG fallback quality was increased, or both. So the "Improved the quality of the custom items icons" has obviously tweaked the above formula in some way. If PNG filesize > 28KB, compress as JPEG instead with 32% quality.Convert input icon to lossless PNG with alpha transparency.So it's still not doing any import/export to/from the agilekeychain (folder sync) format.Īs for the improved quality mentioned above, 1Password 4 currently works/worked like this: I erased ~/Library/Application Support/1Password 4 and did a fresh import of the 1Password 3 agilekeychain file. Improved the quality of the custom items icons. It looks like a decision was made long ago to migrate all customers over to the icon-server, but such a one-size-fits-all approach defeats the beauty, simplicity and flexibility of 1Password and just leads to the kind of desolate landscape seen in the video. :) What a shame for what's otherwise an awesome upgrade. This is the only reason I am not switching yet, and if things carry on like this then I never will. I bought 1Password 4 on October 21st, over two months ago, and I am still using 1Password 3. Especially when we are talking about microscopically tiny filesizes to add PNG icons back and achieve perfect custom icon sync between all versions and all operating systems, along with preserving the kind of sharp, clear, non-blurry graphics quality that made 1Password 3 look so good. It's completely ridiculous that I have to choose between icons or the latest version. Sounds like the best choice to me, especially when when you also consider that the app icon. This would ensure that the same custom icons are visible on Mac, Windows, iOS and all versions of 1Password and that they always stay in sync. agilekeychain format whenever it's doing folder sync, since they will use the exact same file format. It then becomes trivial for 1Password 4 to import / export all custom. PNGs for all custom icons, it achieves 1:1 feature parity and compatibility with 1Password 3's data format. So if 1Password 4 switches back to using. The 1Password 3.agilekeychain format uses. Wouldn't the simplest and best solution to both the import/export problem and the quality+transparency problem be to always use PNG for custom app icons? It only takes a few seconds over WiFi or about a minute over the air, for an initial sync that preserves all icons. I don't give a rat's ass if my 109 PNG app icons at 10-20 kilobytes per icon means 1 to 2 megabytes of more data to transfer on the first sync to my mobile device. The fact that this is a frequently asked question should be a hint to you: Every time there's been an 1Password 4 update, I check the changelog, and am disappointed over and over again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |