-
Notifications
You must be signed in to change notification settings - Fork 175
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create Rule “what-the-user-experience-should-be-like/rule”
- Loading branch information
Showing
9 changed files
with
42 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+59.2 KB
rules/what-the-user-experience-should-be-like/checkforupdate_snagit.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+23.5 KB
rules/what-the-user-experience-should-be-like/diagnosticsupdater01.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+29.3 KB
rules/what-the-user-experience-should-be-like/diagnosticsupdater02.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+40.9 KB
rules/what-the-user-experience-should-be-like/diagnosticsupdater03.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+32.9 KB
rules/what-the-user-experience-should-be-like/diagnosticsupdater04.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+36.9 KB
rules/what-the-user-experience-should-be-like/diagnosticsupdater05.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
--- | ||
type: rule | ||
title: Do you know what the user experience should be like? | ||
uri: what-the-user-experience-should-be-like | ||
authors: | ||
- title: Adam Cogan | ||
url: https://ssw.com.au/people/adam-cogan/ | ||
created: 2014-03-14T02:39:00.000Z | ||
archivedreason: outdated | ||
guid: 24f2a833-2d72-40d7-aeb0-3acea67bfc7f | ||
--- | ||
As per the rule [Do you know there should be a standard menu item "Check for Updates"?](RulesToBetterWindowsForms.aspx#CheckForUpdates) on Rules to Better Windows UI, you should have a standard menu item "Check for Updates" in the Help menu. | ||
|
||
<!--endintro--> | ||
|
||
Here are a couple of examples of Check for Updates results: | ||
|
||
::: bad | ||
![Figure: Bad Example - Skype does a good job, with a green tick and simple message. The actual version number would have made it more complete.](checkforupdate_skype.png) | ||
::: | ||
|
||
::: bad | ||
![Figure: Bad Example - Snagit has horrible UI (red text when it is not an error and Hyperlinks without underlines), however the link to the latest features is not bad](checkforupdate_snagit.png) | ||
::: | ||
|
||
::: good | ||
![Figure: Good Example - SSW Code Auditor has a great UI (using the freely available component in .NET Toolkit)](codeauditorupdater.png) | ||
::: | ||
|
||
More Information: | ||
|
||
If you implement this code from the SSW Toolkit, you will get this UI. | ||
|
||
![Figure 1: Help | Check for Updates opens the Updater form.](diagnosticsupdater01.jpg) | ||
|
||
![Figure 2: Confirmation that they already have the latest version.](diagnosticsupdater02.jpg) | ||
|
||
![Figure 3: The simple prompt to upgrade when a new version is available.](diagnosticsupdater03.jpg) | ||
|
||
![Figure 4: Showing the upgrading progress.](diagnosticsupdater04.jpg) | ||
|
||
![Figure 5: Restarting the application is required because the new version will not take affect until quit and launch the app again.](diagnosticsupdater05.jpg) |