PLEASE! DO an Update Installation Routine!
What is wrong with you guys? Why let you thousands of users do such an effort every time you release an update????
0
-
which effort? Downloading, doubleclickig, dragging, clicking "replace"? How could it be easier? 0 -
I don’t mean to speak on behalf of the OP, but I’m guessing they are probably asking why Phase One never seems to provide upgrade instructions. A simple “readme†file in the disk image is not an unrealistic expectation from a company that bills themselves as providing professional tools. Just something that states whether it’s OK to install over the top of an existing installation or whether we should uninstall/reinstall. Whether we should expect catalogs and sessions to update, etc…
If this was a “third decimal†update like 10.0.3 then I personally wouldn’t be so concerned. But this is the first major point update to a new version. How are we supposed to know what’s normal and expected under these circumstances? Part of being a “professional†developer is providing your user base with fundamental information.
I actually just upgraded form 8 to 10 last week and I found ZERO information about upgrading. I just played it conservative and followed the complete removal KB article prior to installing v10. Thankfully my environment is modest so this wasn't much of an effort. The fact that I had to guess and make assumptions about this, however, is pretty inexcusable.0 -
Well, when you open the .dmg it states : "Drag to install". Couldn't be simpler, could it?
Or is it /too/ simple and makes people wonder?0 -
[quote="Billiam29" wrote:
I don’t mean to speak on behalf of the OP, but I’m guessing they are probably asking why Phase One never seems to provide upgrade instructions. A simple “readme†file in the disk image is not an unrealistic expectation from a company that bills themselves as providing professional tools. Just something that states whether it’s OK to install over the top of an existing installation or whether we should uninstall/reinstall. Whether we should expect catalogs and sessions to update, etc…
If this was a “third decimal†update like 10.0.3 then I personally wouldn’t be so concerned. But this is the first major point update to a new version. How are we supposed to know what’s normal and expected under these circumstances? Part of being a “professional†developer is providing your user base with fundamental information.
I actually just upgraded form 8 to 10 last week and I found ZERO information about upgrading. I just played it conservative and followed the complete removal KB article prior to installing v10. Thankfully my environment is modest so this wasn't much of an effort. The fact that I had to guess and make assumptions about this, however, is pretty inexcusable.
We try to not overcomplicate the upgrade/installation process.
All things done during an update can be reverted:
- When upgrading a catalog or session, a backup of the original is created.
- The same goes for setting-files.
- If it was required to uninstall, we would have stated this clearly. However, replacing is just fine. This will also keep your current application settings.0 -
Other than flying over a tech guy to install the update I don't think it could be much easier! 0 -
What he is referring to is an in-app update functionality, like in many other apps that understand user experience and simplicity: - The user launches the app, it checks whether a new update is available and offers to download and install it.
- The user confirms that the update should be installed.
- Update downloads, installs, closes the old app and moves it into the Trash (in case you want to revert to the old version) and launches the new app.
- Done.
All the user has to do is to click on an OK button, everything else is automatic. This is a standard functionality offered in Apple's Dev Toolkit, so any Mac app can do this if the developer decides to implement it.0
投稿コメントは受け付けていません。
コメント
6件のコメント