[MonoDevelop] Extended notebook widget

Todd Berman tberman@sevenl.net
Sat, 01 May 2004 03:55:39 -0400

On Sat, 2004-01-05 at 13:26 +0900, Ian MacLean wrote:
> Todd Berman wrote:
> >The code looks good, however I am not sure if we want to use this for
> >MonoDevelop.
> >
> >I have yet to hear for a convincing case in putting functionality on a
> >right click menu accessed by clicking on a tab. Stuff like 'Oh, but you
> >put close and save menu items there' doesnt really cut it for me. We
> >have a whole button for close, and save isnt something that needs to be
> >duplicated there.
> >  
> >
> sure there is a close button but thats not the point. With a context 
> menu you can pop it up and select close right away. With the close 
> button you need to select the tab and then mouse across to the button - 
> which is  a very small target - making the whole operation take that 
> much longer.

huh, im talking about the close button *on* the tab. surely a single
mouse click is faster than a right click, find menu item, click again.

and you dont need to select the tab to close it, you just click close
and it works. (with the close button on the tab)

> I don't see duplication as a problem either. Context menus almost always 
> duplicate functionality available elsewhere - the context menu for files 
> in nautilus for example - the point is that you get to the operation 
> directly after selecting the object you are working with rather than 
> having to mouse somewhere else to get it.
> The other argument is user expectation. Visual studio, mozilla firefox 
> and other commonly used apps have the context menus on tabs so there 
> will be some expectation for MonoDevelop to do the same.

Hmm, i see your point here, but i still dunno. To me, having a tab
control with re-arrangable tabs is far more important than one with a
context menu on the tab itself.