Comments on: Five too many ways to save! http://www.altogetherdigital.com/20061201/five-too-many-choices/ Thu, 04 Dec 2008 23:23:45 +0000 http://wordpress.org/?v=2.2.1 By: mjs http://www.altogetherdigital.com/20061201/five-too-many-choices/#comment-249 mjs Fri, 08 Dec 2006 10:24:13 +0000 http://www.altogetherdigital.com/20061201/five-too-many-choices/#comment-249 Given that e.g. Wikipedia can manage with "Save", "Preview" plus a "minor revision" toggle, AND our internal wiki "power users" don't know what all of the options do, I don't agree that all six save combinations need to be available in the UI. (This also isn't a case where you need to make a rarely-used function highly visible and accessible, as is the case with e.g. the emergency stop button on an escalator.) A few days ago I changed the buttons on the edit page to "Save" and "Preview" only, and on the preview page to "Save" only. I take your and Ade's point about cancel releasing the lock (I'd forgotten about this), but if two people edit a page at the same time the second gets a message allowing them to break the lock if they choose, which is sufficient for our purposes at least. (Also, even with a cancel button in place, you can't guarantee that people will hit it when they're supposed to.) Given that e.g. Wikipedia can manage with “Save”, “Preview” plus a “minor revision” toggle, AND our internal wiki “power users” don’t know what all of the options do, I don’t agree that all six save combinations need to be available in the UI. (This also isn’t a case where you need to make a rarely-used function highly visible and accessible, as is the case with e.g. the emergency stop button on an escalator.)

A few days ago I changed the buttons on the edit page to “Save” and “Preview” only, and on the preview page to “Save” only. I take your and Ade’s point about cancel releasing the lock (I’d forgotten about this), but if two people edit a page at the same time the second gets a message allowing them to break the lock if they choose, which is sufficient for our purposes at least. (Also, even with a cancel button in place, you can’t guarantee that people will hit it when they’re supposed to.)

]]> By: mzeecedric http://www.altogetherdigital.com/20061201/five-too-many-choices/#comment-240 mzeecedric Thu, 07 Dec 2006 23:07:58 +0000 http://www.altogetherdigital.com/20061201/five-too-many-choices/#comment-240 well I dont agree. For a twiki poweruser all buttons definetly make sense! The only button that I could go without is maybe Quiet save. But in case those buttons disturb, just change the template and remove them. Save makes sense. Force new revision is a great help in case you make some large changes you are not sure about within your editing period. Checkpoint will make sense because i sometimes keep editing one page a whole day long and just want to be sure things are beeing saved once in a while. A automated autosave might be the better instead. Cancel is important as Ace mentioned before. Quiet save needs explanation, otherwise users won't understand what it is about... well I dont agree. For a twiki poweruser all buttons definetly make sense! The only button that I could go without is maybe Quiet save. But in case those buttons disturb, just change the template and remove them.

Save makes sense.

Force new revision is a great help in case you make some large changes you are not sure about within your editing period.

Checkpoint will make sense because i sometimes keep editing one page a whole day long and just want to be sure things are beeing saved once in a while. A automated autosave might be the better instead.

Cancel is important as Ace mentioned before.

Quiet save needs explanation, otherwise users won’t understand what it is about…

]]> By: Ade http://www.altogetherdigital.com/20061201/five-too-many-choices/#comment-203 Ade Fri, 01 Dec 2006 11:35:49 +0000 http://www.altogetherdigital.com/20061201/five-too-many-choices/#comment-203 Agree it's way too much. Trouble is that <i>Cancel</i> releases the lock, so should always be used instead of 'back' etc. But <i>Quiet save</i> and <i>Checkpoint</i> seem unnecessary 99.9% of the time, as does <i>Force new revision</i>. Agree it’s way too much.

Trouble is that Cancel releases the lock, so should always be used instead of ‘back’ etc. But Quiet save and Checkpoint seem unnecessary 99.9% of the time, as does Force new revision.

]]>