This is not a bug, just a wishlist entry. LibrOffice needs at least 6 skins available during its installation: 3 types of 'native' basic skins: - default, - all controls as a side panel (for wide monitors), - netbook (show just document content, just the very basic controls are shown at a small panel), and some additional ones: - OpenOffice-like skin, - MS Office 2003 skin, - MS Office 2007-like skin. The last 3 ones will be helpful for making LibrOffice more popular: familliar interfaces will favour user migration to. -- P.S. I am sorry, if it is a wrong place for such entry, unfortunately, I didn't find anything like LibrOffice wishlist.
May be you want to vote on our new Voting page? <http://wiki.documentfoundation.org/Vote_for_Enhancement>
Calling it "our" voting page is an exaggeration. It has absolutely no "official" meaning.
Seeing that many more personal users would like to use it, but don't like the look or don't like that they can't change it. Colors and Views could help in this matter?
Can I cross-reference this idea to https://issues.apache.org/ooo/show_bug.cgi?id=18829 Which would have had the advantage of separating UI and product development, and perhaps allowed a completely separate 'skins' ecosystem as happened with other products, including windows XP itself and the various Linux desktops.
Adjusting summary title for clarity. Also amending open vote entry https://wiki.documentfoundation.org/Vote_for_Enhancement
What you call “skin” is named, more clearly, “workspace” (cf. Photoshop).
*** Bug 101075 has been marked as a duplicate of this bug. ***
*** Bug 88902 has been marked as a duplicate of this bug. ***
Many features may be considered to relate to workspaces. Added some that I think may be relevant to "see also" list - tabs, sidebars (I haven't gone hunting for these bugs yet), various bugs related to UI navigation aids, full screen and small screen optimizations, and plenty more I have not found yet too I'm sure.
Also note re documentation of this feature to clearly distinguish "LO layout workspaces" from "unix desktop workspaces" - see for example bug #95630 (new calc document opens in wrong [unix] workspace).
I believe this is a duplicate of bug 101249, where we have 4 different UI arrangements - default, single toolbar, sidebar, notebookbar.
(In reply to Yousuf Philips (jay) from comment #11) > I believe this is a duplicate of bug 101249, where we have 4 different UI > arrangements - default, single toolbar, sidebar, notebookbar. Well only partially. So while bug 101249 provides a framework and addresses the first part of comment 0 If you review the list of "See also" and the duplicates, we do nothing yet for "themeing" or "workspace" configuration(s) to adjust LibreOffice UI to resemble other Office applications. But there is at least one more major piece of framework preventing this--and that is some ability to handle import/export & backup of user UI customization bug 52387 bug 59493 bug 64439 Until we can offer a means for injecting UI customization from an external configuration file the rest of this enhancement can not be implemented. And of course it would be more appealing for folks to test/use if we also include a backup and restore capability (other that the current "save a copy" of the user profile, and paste it back).
I don't understand what you mean by theming... Creating a MSO 07 like skin would probably infringe on design patents. the Notebookbar covers a similar UI already. And if you want familiarity for Windows users, then offer LO by default with Notebookbar turned on with Breeze icon set. Offering a way to allow knock-offs of Microsoft Office would just diminish the uniqueness of LO. There's already plenty of chinese Microsoft Office clones. Why lead LO in that direction, when the work of the design team is leading LO into a unique direction that actually is working out great?
I personally don't care about themeing or workspace to "resemble" another application--but that could be fertile ground from "extension/template" mavens. Rather--realize that UI customizations currently are transient, clear the profile and they are gone. So having the ability to assert multiple customizations (of Toolbar, Sidebar, module placement & state) as well .UI based reconfiguration of dialogs/toolbars/sidebar decks, or even the new MUFFIN experimental Notebook bar from a single transportable "UI package" is the crux of this enhancement. The ability to bundle ones configurations and export them as a personalized "UI package" that could be applied on another installation would be a real step forward. Sure we can do similar now by copying our individual user profile and restoring it to another system--but this takes it a step further and would allow UI configuration to be done in a consistent (non-individualized) fashion and applied to the profiles of other users. Apply the package--they get a set of customizations.
As there are more than one issue in this enhancement it should be broken up into different bugs to focus on their individual issues. The issue of themeing has been presented as a GSoC project and the newly created bug should link to the wiki entry. https://wiki.documentfoundation.org/Development/GSoC/Ideas#Application_Themes The issue of import/export of workspaces (user configured UI arrangement) should be an easyhack of extracting/inserting the necessary entries from/to the user profile's registrymodifications.xcu. Likely something to add into the options dialog, as we already have a request to backup and restore the entire user profile (bug 64439).
We now have - Standard - Single Line - Sidebar - Tabbedbar - Groupedbar compact and in experimental some other layouts, so from my point of view enough layouts.
*** Bug 129047 has been marked as a duplicate of this bug. ***