4 ms·
Newer versions of MS Office (with that ribbon) have the same problem. There is an About dialog, but getting to it is a process that I still can't remember after
by userbinator 7y ago
Newer versions of MS Office (with that ribbon) have the same problem. There is an About dialog, but getting to it is a process that I still can't remember after having to do it a few times. Yet Help->About is still in my mind after all these years, despite not using it all that much.
The idiotic full screen save menu that forces you to click a few more times to save on the computer instead of a cloud service (I'm sure that's some sort of dark pattern...) is even worse, however.
Edit: here's a good rant about that latter one: https://what.thedailywtf.com/topic/11058/save-me-from-shit-ui-you-can-t-be-saved https://what.thedailywtf.com/topic/11058/save-me-from-shit-u...
- poizan42 7y agoIt's at File->Account->About <program>. Because it totally makes sense to put the about box under Account... I should also mention that there isn't even a Help menu anymore, because nobody would have a need for help with anything in Microsoft Office, right? You can still get help if you know about F1 though.
- galangalalgol 7y agoOffice left all the keyboard shortcuts the same, at least in excel. Some of the combos hardwired into my fingers are based on menus that no longer exist, but they still work. I don't know if that was good design or not, but i like it.
- raxxorrax 7y agoYou should be glad that you still have any save menu, as they wanted to scrap that in favor of autosave. Everything coming out of MS the last 5 years has been thoroughly underwhelming, but the UI development and user infantilization takes the cake. Just image everyone in your company saves any document they opened automatically. How would these even look like after 1-2 weeks? The decision processes at Microsoft cannot be explained by cocaine alone anymore... Sorry for the rant, let's just say I understand your frustration...
- TuringTest 7y agoAutosave is a safe and recommended UI practice; it has been widely implemented and validated by mobile UIs, where whatever you're doing is recorded when you close the app without having to explicitly save the document (a half written Whatsapp message, a mail draft...) > Just image everyone in your company saves any document they opened automatically. How would these even look like after 1-2 weeks? The essence of using autosave is separating storing from sharing the information. In an office suite, autosave should save your changes locally, so that a power outage won't wipe your edits. This doesn't mean that other people will see those changes as soon as they're made; that's why you also create a "share" or "publish" command that will make them available. Developers got it and enjoy it in their version control systems, so why is it so difficult for them to understand that end users would benefit from the same safeguards? The first commandment of UI design is "treat all user input as sacred", yet so few developers respect it. [1] http://quoteitup.com/quote/beUH/jef-raskin-the-system-should-treat-all-user-input-as-sacred http://quoteitup.com/quote/beUH/jef-raskin-the-system-should...
- raxxorrax 7y agoAutosave is a good feature, not only since mobile UIs. But not the way it is currently implemented that any change in the document is immediately committed to the original file if you didn't preemptively made a copy. Totally different to any version control system. For example, we have a traveling expense document that is exported as pdf after people made their input. Since quite some time people can see what the last employee has been up to. Don't get me wrong, that can get quite funny. Possibly ad breach of confidential information, but meh... We have no backend to publish to for these documents. It is just the boring file server. There are certainly weaknesses in this particular workflow, but I would argue that it is quite common.
- TuringTest 7y agoCommitting instantly to the file is perfectly fine, as long as you have infinite undo (preferably with version history) and local drafts - i.e. exactly what VCS provide. A shared folder in a server doesn't separate saving from sharing, but that's a fault of shared folders, not autosave. The popular storage models for end users are utterly broken, but developers don't care because they don't need to endure it, they've got their superior tools that they keep to themselves.
- treypitt 7y agothanks for the link! completely agree. I strongly recommend libreoffice from a design perspective