Re: Split/dual pane view again (but this time with code)

[Brian Crockford <dosperm gmail com>]

>> Also, I don't like the "Side Pane" toplevel menu. Menu operations
>> should be arranged by what they do, not what application feature
>> enable them. So, file copy operations should be in edit just like
>> other such operations
>>
>> Generally we don't hide menu items that are not availible atm, we just
>> make them insensitive
>
> Now, this is indeed a dilemma. On the one hand I completely understand
> your reasoning. On the other hand, all this "extra" functionality
> should not bother the non-split-view user at all, and I don't think
> insensitive split-view menu items sprinkled all over the place are
> a good idea. As a non-user, I'd be annoyed.
>
> Maybe it can be seen as a different "mode". We have spatial mode, we
> have navigation mode, and this could be an "extended" navigation mode
> that can be toggled on and off on the fly.

It seems the menu's contents are not strictly necessary. The first two
items in the menu - copy and move - should theoretically function
identically to the normal copy|cut + paste commands, and the last can
be replicated with simple browsing (at which Nautilus already excels).
It might be prudent to keep the keyboard shortcuts, for those who need
that heavy lifting, but get rid of the menu items altogether.

In regards to the use of TAB, what Holger mentioned is what I was more
vaguely describing earlier: TAB would be expected to (eventually)
bring focus to the next pane. No more than that is needed.

Brian