Created attachment 103674 [details]
MS Word dialog box
Native OS X apps include a drawer-style "Save Before Exit" dialog which slides down from the main toolbar/window bar. It would be cool for LO to include these instead the standalone dialog box model.
A valid enhancement request. These “sheet”-style dialogs are cool.
yes, please :)
See comment on
To sum up: Implementation is possible, but macOS do not support nested sheets (at least by style guide). There are many nested modal dialogs. These dialogs have to be redesigned only one level deep (but that is another topic which would increase usability too). UX eval is required.
(In reply to Thorsten Wagner from comment #4)
> UX eval is required.
Keywords += needsUXEval, CC += firstname.lastname@example.org,
You named the requirement: dialogs must not stack deeper than one level. While this sounds desirable in general it means to rework 75% of the UI, change most workflows, and adds a lot of effort for just a small improvement.
If we stop trying to mimic OS/DE look and feel and develop only one VCL much man power can be saved and users get a more polished UI.
I totaly agree. Dialogs should be designed in a way as simple as possible without violating any of the different OS/DE style guides.
As sheets are macOS specific, this is no general way to go. I see two possibilities:
(1) Drop the idea of using sheets
(2) Change the criterion for using sheets: Not for modal dialogs, but for simple dialogs, e.g. "Save Yes/No/Cancel" of "Tips" and things like that only. I would be possible to implement this by introducing a dialog attribute on a per dialog basis, which is ignored by non macOS backends.
BTW: However for new dialogs nesting should be avoided if possible, because nested dialogs are not very handy. There are currently some dialogs with tree nesting levels which are very hard to use.
BTW: Style guides for all backends (including macOS) should be taken into account prior to implementing new dialogs. For example, the new Area dialog with buttons inside to switch between pages causes poor code within VCL. Uncommon button states had to be introduced, which are not style guide compliant (at least for macOS, but probably for GTK, Qt, and Windows too).
My personal opinion: Keep it simple will create a polished UI best.
(In reply to Thorsten Wagner from comment #6)
> My personal opinion: Keep it simple will create a polished UI best.
Absolutely. And if #2 is easy to realize we should do this. Load/Save and confirmations will make users feel home.