| |||||||||||||
Sobotka: Why GIMP is inadequateSobotka: Why GIMP is inadequatePosted Jan 13, 2011 16:26 UTC (Thu) by n8willis (editor, #43041)In reply to: Sobotka: Why GIMP is inadequate by nye Parent article: Sobotka: Why GIMP is inadequate
The fact that one can memorize Blender's UI in no way equates to its being well-designed. Humans can memorize anything -- people even memorize thousands of digits of pi for sport, and it is mathematically the most random sequence of numbers known. But Blender still doesn't ask you if you want to save your work when you quit.
Whatever (unspecified) awful-ness you assert there is in the GIMP UI, at least it gets that -- and plenty of other basic HCI -- right.
Nate
(Log in to post comments)
Sobotka: Why GIMP is inadequate Posted Jan 13, 2011 20:32 UTC (Thu) by jthill (guest, #56558) [Link] As I recall Blender _always_ saves your work when you quit. If you meant to save it, pop back in (it starts _fast_) and save the blend you quit on to the original file. It's even dead easy to get it to always start where you left off.
Sobotka: Why GIMP is inadequate Posted Jan 14, 2011 19:58 UTC (Fri) by n8willis (editor, #43041) [Link]
Sobotka: Why GIMP is inadequate Posted Jan 15, 2011 3:59 UTC (Sat) by jthill (guest, #56558) [Link] From that link:Other File Open Options [...] I must be missing something; it seems to me that's exactly what I described.
Sobotka: Why GIMP is inadequate Posted Jan 21, 2011 22:13 UTC (Fri) by n8willis (editor, #43041) [Link]
Actually, it's not. Taken by itself that snippet implies that Blender auto-saves changes made to open files. In fact, quit.blend is just the contents of the *last* file touched -- meaning, for example, if you are working on one file, then open another, you lose everything, and quit.blend will have stored the unmodified last-opened-file. Plus you still get no warning/confirmation-interrupt that the file-open-operation is also destructive. The proper way to do auto-saving is the way Inkscape does it (per-file). And even if it did proper autosaves, it still doesn't make up for lacking confirmation-on-close/quit-with-unsaved changes, which is the root problem. Autosaves are supposed to be for crash recovery.
Nate
Sobotka: Why GIMP is inadequate Posted Jan 22, 2011 2:15 UTC (Sat) by jthill (guest, #56558) [Link] that snippet implies that Blender auto-saves changes made to open filesblender does auto-save, in exactly the way you say is proper. The "Vitals" section of the manual says so, and it's hard to miss the big "Auto Save" button on the preferences panel. It defaults to every five minutes, per file.
if you are working on one file, then open another File-open? Ok, we can change the subject, but you never mentioned this before. Blender does save every time you quit. More: manually saving takes a backup, and if you want lots of those you can tell it how many right there on the same auto-save preference pane. So acquiring the habit of hitting ^W whenever you hit a nice spot, before moving on to the next thing to do, because you can casually recover from doing that by mistake too, seems like a no-brainer to me. More: hit F1, double-click the filename, ... nothing happens. You have to hit Open File or use the keyboard. Just a little syncopation to remind you, like it asking for confirmation when you quit -- which it does. The file-open behavior description is at least accurate, but that behavior doesn't seem to be a problem in actual practice - for reasons which are apparent to anyone who actually uses it.
Sobotka: Why GIMP is inadequate Posted Feb 2, 2011 22:21 UTC (Wed) by n8willis (editor, #43041) [Link]
You clearly have a radically different idea about what constitutes "proper" behavior in this use case. I stand by what I linked to, by the absurdity of placing the onus on the user to do the saving, and the differences between Inkscape and Blender are quite clear, so I'm declaring this a John-Henry point. Have a nice day....
Nate
|
|||||||||||||