-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6.10.2004, space aliens observed Sune Foldager saying:
Good, argumentative reasons for it, please! :-).
For me, it went something like this:
"OK, now I want to change the background color of this window. That must be in Preferences. Uhm. No preferences in the app menu. Must be burried somewhere. Probably in Edit. Nope. Maybe in Window? Nah. Okay, so I'll go through each menu. Oh, Color Settings. Okay, but that only works with syntax highlighting disabled. That must mean that there are more settings somewhere else. I guess I just missed the Preferences. They *must* be in the app menu. Argh. Okay, "TextMate Help". What, you mean I can't change this?"
Had all settings been inside a Preferences dialog, it would have been clear what the user can change and what he can't right from the beginning.
Having preferences inside the menu has additional problems. It clutters the menu with things you use seldomly, which makes things you use more often (like actual commands) harder to find. And it makes it harder to find preferences, because it's often not clear where a given preference should go, and if you can't find it, you can't be sure whether you just missed it or whether it simply doesn't exist at all. A preferences window also gives you room for additional information about settings.
BTW, what the heck is "Freehanded edit"?
lucas
- -- "Afer all, who needs courage when you have a gun?" -- Prof Hubert Farnsworth
On Thu, 7 Oct 2004, Lucas K. Mathis wrote:
BTW, what the heck is "Freehanded edit"?
It is an editing mode in which the caret is free to go anywhere in the display i.e. it is not limited horizontally by newlines. Kind of like in really old-style editors. It is quite convenient if you are making some kind of ASCII drawing.
An example could be an illustration of a hierarchy in your code such as:
Superclass / \ / \ Subclass Subclass
This is much easier to handle in "Freehanded edit". Note that often it makes sense to combine this with the overwrite mode.