Created attachment 121168 [details]
various property dialogs
In Writer, we have single properties dialogs for tables, objects (chart, formula, etc), frames, and images, but shapes and textboxes have multiple dialogs to modify the Area (.uno:FormatArea), Line (.uno:FormatLine), Position & Size (.uno:TransformDialog), and Text (.uno:TextAttributes). In other apps, objects have these multiple property dialogs.
Combining these properties dialogs into a single dialog will allow easy access to modify properties that are currently spread across multiple dialogs within a single dialog, which will improve the user experience and save time.
The new combined dialog would combine the tabs found in the various dialogs, but exclude tabs for property customization like the Line Styles and Arrow Styles tabs in the Line dialog and the Colors, Gradients, Hatching, and Bitmap tabs of the Area dialog. In Writer, the Wrap tab found in the object dialog would also be included in the combined dialog.
There is an opposite to spread content: Stumbled recently over the cross-reference dialog that comprises of all types of fields. So yes to your idea, but perhaps we could also consider to have introduce some kind of "see-as-well" link - and simple dialogs in general.
Yes adding a combined tabbed properties GUI dialog to Shapes and Text Boxes in Writer is reasonable. But the requirement is also applicable to Impress, Calc, and Draw so needs to be done globally in the generic commands.
Migrating Whiteboard tags to Keywords: (needsDevEval, topicUI)
The dialog should also have fields to modify the name, title and description of the object (.uno:NameGroup, .uno:ObjectTitleDescription).
Also for images in non-writer modules, images options like brightness and contrast, etc. should have its own tab similar to what is being done for writer's image dialog (bug 103272).
having removed name and description buttons from defaults for context menu (bug 101193) implementing a comprehensive properties dialog for objects is both a UX and an a11y issue. Adding the accessibility keyword.
Please add keyword 'needsUXEval' and CC 'firstname.lastname@example.org' if input from UX is needed.