@Maxime:You appear to consider a narrow tab very important. Why do you think those 5mm you gain more important than improved usability? Or is it that you don't think it would make the UI more usable (for the Haiku target group, not justyourself)? What about people with smaller screen or those who need to use lower resolution because of reduced eye-sight (scalable GUIs would be a better solution, but until we have that..)?
Think with Stack&Tile in mind.It makes sense to close a single window from a stacked group, and to resize all of them. For this you need a "maximize to content" button in each of the windows, maximizing to the content of this one window, and resizing all the windows of the stack to the same size.
It makes no sense to hide/minimize only one of the windows, you want all of them to go. So you don't want one separate minimize button on each tab.
B) To hide windows that are only occasionally required, for example a music player or an IM conversation. Maybe this be solved in some better way too?
Close the window, the application can run without windows opened. Double click a playlist in tracker, it replace the current one and start playing. Why would you need a window for your music player ? :) Same apply for IM with the IMKit, it's just integrated into tracker and windows are opened only when you are chatting. No need for windows when the application should be running in the background of other things :)
And this led me to some other thoughts.. No complete ideas, just brainstorming with you :) From a pure user point of view, is there really such a big difference between a hidden application and a non-running application? Would it be possible to eliminate this difference, and could it benefit the users? Ifyou look at opening a document in an editor, then closing and hiding would be identical if the system instantly saved all changes and the undo history.Modern web browsers are capable of saving open pages on exit thus making close and hide virtually the same. Of course starting an application and restoring for example web pages takes more time than unhiding while thelatter uses more memory. However, I feel that this is because of limitationsin software and hardware rather than in concept. Would a system thatinstantly restores any application be considered "ideal", and how close tothis could we get in reality?
An opened window is like a working sheet where you can make changes without saving for trying out things. When you try to close it, the program asks you if you want to save your changes. Also, keep in mind that the program<>window link is not (or at least should not be 1:1. You can have multiple window in a program. You may want to close some or all of them, but the program will still be running. Look at tracker : each folder remember its window size and position, so it opens back at the same place next time. You may occasionally want to hide/minimize a window because you want to see something below, but know you'll want to use these files again. But you can also close it and when you want to reopen it, you have to browse trough the filesystem, for example using the "X-Ray" menus.
It's the only proper use case I see for minimizing a window, so it's almost already somewhat a shortcut for powerusers :) If you want to do multiple different things, it makes more sense to use workspaces instead.
-- Adrien Destugues / PulkoMandy http://pulkomandy.ath.cx