Download it now!
Bug 130083 - Redesign LibreOffice Options Start Page
Summary: Redesign LibreOffice Options Start Page
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
: 128722 (view as bug list)
Depends on:
Blocks: Options-Dialog
  Show dependency treegraph
 
Reported: 2020-01-19 22:19 UTC by andreas_k
Modified: 2020-03-01 08:29 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
mockup of an landing page (75.36 KB, image/png)
2020-01-19 22:19 UTC, andreas_k
Details
Benjamin landing page (155.50 KB, application/vnd.oasis.opendocument.graphics)
2020-01-19 22:21 UTC, andreas_k
Details
Mockup (54.96 KB, image/png)
2020-01-20 08:47 UTC, Heiko Tietze
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andreas_k 2020-01-19 22:19:18 UTC
Created attachment 157257 [details]
mockup of an landing page

The actual LibreOffice options start page (landing page) show Address stuff and Cryptography stuff.

There is an long discussion about make an simple and advanced option section. As the discussion didn't result in an change I would say the result is no result and no result mean no change.

Anyway I like the idea of an simple and advanced section but I don't think an complete rewrite of the UI is needed. There is an user survey which options the different user groups use and the user how we design the UI didn't use that much options, so why we want add this view options to an new landing page and that's it. So everything is available as it is now (for all our existing users) but in addition the most used options are available it the first page in addition.
Comment 1 andreas_k 2020-01-19 22:21:21 UTC
Created attachment 157258 [details]
Benjamin landing page

This are the options Benjamin need. fyi we don't have to discuss which configuration is needed and not, cause this was already done. 

The question is only, do we want an landing page for Configure in addition to the existing stuff.
Comment 2 Heiko Tietze 2020-01-20 08:28:24 UTC
> we don't have to discuss which configuration is needed and not
> cause this was already done. 

Really, where?

> The question is only, do we want an landing page for Configure in addition
> to the existing stuff.

The "landing" page usually provides information how to use the other pages. It tells the user what she can do here. The mockup duplicates some options but gives no hint about what's possible.
Comment 3 Heiko Tietze 2020-01-20 08:47:01 UTC
Created attachment 157261 [details]
Mockup

Mockup for a comprehensive overview with access to the respective options. I'm aware that we cannot list everything and may easily exceed the available space meaning we have to ignore some potentially important information.

There is the request to bring together all modules (bug 101609) and we should clean the hierarchy (eg. personalization could be with view).
Comment 4 Thomas Lendo 2020-01-21 22:50:50 UTC
Hm. I think additional text and pages makes it more complex for normal users than it's now. Who should read it and why not the 'real/full' page?

And it will add more content for localization, discussions about what should be shown and what not, etc.
Comment 5 jackandmixers 2020-01-22 02:16:04 UTC
(In reply to Thomas Lendo from comment #4)
> Hm. I think additional text and pages makes it more complex for normal users
> than it's now.

I wonder if it's even possible to pare down what's already there, given I don't currently have access to user feedback. (Survey? Interviews?)

Users probably aren't using many of the options that already exist- perhaps we can figure out which ones to eliminate?
Comment 6 Cor Nouws 2020-01-22 20:06:52 UTC
(In reply to Thomas Lendo from comment #4)
> Hm. I think additional text and pages makes it more complex for normal users
> than it's now. Who should read it and why not the 'real/full' page?
One page to start with, including MostUsedSettings, doesn't sound as a bad plan to me, though.
Comment 7 andreas_k 2020-01-23 10:15:27 UTC
*** Bug 128722 has been marked as a duplicate of this bug. ***
Comment 8 andreas_k 2020-01-23 10:22:35 UTC
(In reply to Heiko Tietze from comment #2)
> > we don't have to discuss which configuration is needed and not
> > cause this was already done. 
> 
> Really, where?

https://nextcloud.documentfoundation.org/s/cPGtpCTJKTLRNBF
Comment 9 andreas_k 2020-01-23 10:31:42 UTC
> https://nextcloud.documentfoundation.org/s/cPGtpCTJKTLRNBF

Benjamin and Eve Options:
=========================

LibreOffice
- User Data (Address)
- View (Icon style and size + antialiasing)
- Path (paths)
- Personalization (Firefox Themes) unmaintained so I would not have it there

Language
- Languages (UI, lcale, decimale separator, currency, date)

Writer
- General (Units, Tab stop)
- View (Helpline while moving, Images, Tables, Rulers, Smooth scroll)
- Formatting Aids (Paragraph end, Soft hyphen,...
- Mail Merge E-Mail

Calc
- General (Units)
- View (Formula, zero values, grid lines, color, page break, headers, scrollbars, sheet tabs, ...)
- Grid

Draw/Impress
- General (copy when moving, cache, units)
- Grid
- Start with Template Section (impress)

that's not to much options from my point of view for Benjamin (ordinary user) AND EVE (advanced user)
Comment 10 Heiko Tietze 2020-01-23 15:16:06 UTC
(In reply to andreas_k from comment #8)
> https://nextcloud.documentfoundation.org/s/cPGtpCTJKTLRNBF

Ouos, did that myself ;-) (but it's a singular opinion nothing we discussed in detail)
Comment 11 andreas_k 2020-01-23 16:21:46 UTC
In comment 9 you see the settings for Benjamin and Eve and it can fit on one page only admin options wasn't shown.
Comment 12 Thomas Lendo 2020-01-23 21:18:16 UTC
(In reply to jackandmixers from comment #5)
> Users probably aren't using many of the options that already exist- perhaps
> we can figure out which ones to eliminate?
Current settings in the options dialog were carefully and well discussed implemented/rearranged/removed/added. For limited range of the options, a bug can created and discussed. Nothing is perfect and needs can change. But not for the whole thing at once which would a massive overhaul changing hundrets of details. Not all parties that have to bring in their thoughts will take part of the discussion in a bug. And it's confusing to discuss so many changes at once.

But to come back to this request:
I still don't understand the benefit to have a third options configuration (options dialog for average users, expert configuration for advanced users and third and new: one or several overviews for beginners). Options dialogs always are not designed for beginners. That's the inherent reason for it. A program should be designed to fulfill beginners' needs. Options are fore fine tuning extended needs. So, the request counteracts to the sense of options. IMHO.
Comment 13 andreas_k 2020-01-23 21:40:16 UTC
(In reply to Thomas Lendo from comment #12)
> I still don't understand the benefit to have a third options configuration
> (options dialog for average users, expert configuration for advanced users
> and third and new: one or several overviews for beginners). Options dialogs
> always are not designed for beginners. That's the inherent reason for it. A
> program should be designed to fulfill beginners' needs. Options are fore
> fine tuning extended needs. So, the request counteracts to the sense of
> options. IMHO.

I start this request for exact that reason I don't see an benefit to have an simple/advanced options dialog (Bug 90989) AND to reinvest the wheel. There are a lot of users out there and I don't want to implement the options dialog cause it could maybe an advantage.

But I also think that the User Data Options page is not the perfect first place to start with options, cause the Address blog has so much private content and the Cryptography is nothing an user can setup without an administrator.

So this it the idea of use the existing system and extend it with one additional tab where you get an overview what you can configure with LibO so something like KDE did https://kde.org/announcements/plasma-5.11/system-settings.png

That's the reason I like the mockup from Heiko where you can't edit stuff on the main page, but you can see the settings and jump to the settings correct page, without to know where the option is located.
https://bug-attachments.documentfoundation.org/attachment.cgi?id=157261

So the main goal is to use the existing system and improve it for better navigation without reinvest the wheel.
Comment 14 Heiko Tietze 2020-01-30 07:18:35 UTC
We should also take into account that root nodes don't have a content. Meaning: if you are on User Data and click Language Settings, the shown tab doesn't change. Same happens when on Languages clicking at the first node. An option could be to show the first entry below this node - or we create special tabs.
Comment 15 Thomas Lendo 2020-03-01 08:29:18 UTC
(In reply to andreas_k from comment #13)
> So this it the idea of use the existing system and extend it with one
> additional tab where you get an overview what you can configure with LibO so
> something like KDE did
> https://kde.org/announcements/plasma-5.11/system-settings.png
> 
> That's the reason I like the mockup from Heiko where you can't edit stuff on
> the main page, but you can see the settings and jump to the settings correct
> page, without to know where the option is located.
> https://bug-attachments.documentfoundation.org/attachment.cgi?id=157261
> 
> So the main goal is to use the existing system and improve it for better
> navigation without reinvest the wheel.
If it's only to _show_ existing settings without the possibility to change it (also) here, then I have no objections.