Community
Participate
Working Groups
If the {Outline, Properties, or Palette (GEF-only)} view does not have a page to display, and it is detached floating on top of the active editor, it should be able to hide itself so that it is not wasting space on the screen for editors that don't use that view. To indicate that the view is actually open, so that the user doesn't reopen it, it could appear in the fastviews toolbar. If the user forces it to be displayed, it could be displayed in its inactive state, and then once the part is no longer active, it is hidden again.
Created attachment 51686 [details] Use Case Here is a scenario where I am editing graphical diagrams and text files. When I'm editing a text file, I don't want the palette and outline to cover up the editor.
Hmmmm, what should we do if there are multiple views stacked in the same detacked widnow? We can't just hide it. If we do this we should make it work the same for all 'container' views (i.e. ones whose interior -may be- supplied based on context). The result would be an option that closes a 'container view' if there are no contents for the current context. Personally I think that many users would hate this... BTW, what happens if you hide/close the outline view yourself?
> Hmmmm, what should we do if there are multiple views stacked in the same > detacked widnow? We can't just hide it. In the attached image, both views (outline + palette) are unused at that time, so the entire stack should disappear. If part of the stack were still "active", you would probably show the MRU active tab, and optionally hide the inactive tabs. > If we do this we should make it work the same for all 'container' views (i.e. > ones whose interior -may be- supplied based on context). The result would be an Do you mean all PageBookViews? > option that closes a 'container view' if there are no contents for the current > context. > Personally I think that many users would hate this... Because....they would miss the blank window on top of their editor?? > BTW, what happens if you hide/close the outline view yourself? What do you mean? If the user hides the view, or if I (developer of the editor) programatically close it when my editor is no longer active?
Aha, yup 'PageBookVeiws' is what I meant. Generally speaking most users prefer a stable environment rather than one heavily optimized to save screen real-estate. So having a stack continually appear/disappear as they click on different editors whould annoy more people that it would please (IMO). If I have the time I'd likely rather spend it enhancing the DW support to allow for a full PartSashContainer rather than an individual stack since folks are clamoring for this (mostly multi-monitor users).
> Generally speaking most users prefer > a stable environment rather than How are you defining stable? When I switch from one editor type to another, the outline changes from a white tree with data, to a gray rectangle with nothing in it. There is no stability in either scenario, all of the pixels are going to flash to some other color. I could define stability another way. When I'm using editor type A, I want to see the outline view, when I use editor type B, I don't want to see it. Those are two different "modes" of use, and I want stability across each mode, but not in the transition between modes.
*** This bug has been marked as a duplicate of bug 120910 ***
