On Apr 21, 2006, at 10:17 AM, Chris Thomas wrote:
I didn't want to suggest that myself, but it makes sense. Ideally I think the way to go would be to integrate it with the existing Subversion bundle and check an environment variable (created by the user) to determine whether to use diff or FileMerge.
Actually, I was thinking of them as more options in the list. I have good use for both and I'd want to choose each time.
There are likely to be additional diff utilities in the future, so that might not scale. I think the environment variable is a better overall solution. (I'd also prefer not to clutter the list with duplicate diff entries if we can avoid it. It's already pretty big, even though it's still missing a number of commands.)
However, at least for now, the diff commands could perhaps check to see whether a particular modifier key is held down and do the opposite of the environment variable setting.
Currently, you can activate a command by 1) selecting it from the menu, 2) the gear menu, 3) a shortcut key, 4) a shortcut key list or 5) a tab selector.
I don't think the solution for scaling is to hide commands behind a preference setting or a second hidden shortcut.
I think the solution is the bundle editor. To be able to enable or disable the commands that you want or don't through a gui in the application. And the shortcut key list, if there are too many commands with the same activation method, choose you one you want.
I agree that we shouldn't clutter up the shortcut key lists, but for activating similar commands, that's the only current standard.
Are there currently any commands that are only available once you set an environment variable? I'd like to use them if there are. How would I find out about them?
I know there are a few commands that require you to set up your password or some other random environment variable to be able to run. But I've never heard of any that aren't even in the list until you set one, or any that change their behavior if you hold down keys while it's running or about to run.
For the sake of UI design, let's stick with the existing 5 activation methods until Allan gives us more.
It's difficult to balance discoverability, customization and allow for seamless scaling.
thomas Aylott—subtleGradient—oblivious@subtleGradient.com