https://bugs.documentfoundation.org/show_bug.cgi?id=137931

--- Comment #30 from Eyal Rozenberg <eyalr...@gmx.com> ---
(In reply to V Stuart Foote from comment #28)
> Nope! Doers decide,

That's only very partially true. Doers don't decide policy - the community
decides, via the TDF, the ESC and so on, taking into account the opinions of
developers and other stake-holders. Of course doers need to be willing to go
along with such decisions as otherwise they don't get implemented.

Now, in some contexts, it is a norm that doers decide, and in others it is
explicitly agreed by relevant "non-doer" bodies that doers will decide some
specific matter. ... but this is not one of these contexts. It's a matter of
usability, convenience, the question of attracting new users, user "education"
and so on. And developers are not equipped to make such a decision better than
other community members.

> and this was decided/implemented as for bug 117463 with
> https://wiki.documentfoundation.org/Documentation -- that remains sufficient
> in all cases.

1. Bug 117463 was resolved in 2021. But the main discussion about the choice of
default UI and how to settle the conflicting opinions and considerations was
conducted mostly on bug 135501, and continued into 2022, also with this bug. 

2. On bug 117463, Heiko said that "We had a controversial discussion how to
implement this" - but it's not clear who had this discussion and whether it was
about whether to go through a TotD or about how to implement the TotD approach.

3. Documentation is never a way to resolve a problem with the app or the UI; it
is ever only a secondary mechanism. (Ok, that's my personal view of things, I
don't know that this is project policy, although it really should be.)

> Discussion(s) of exposing the 'User Interface...' dialog as here, or of now
> expanding somehow into a "Welcome" dialog on first launch (bug 154593) still
> promote an ill-conceived "need" for user UI configuration on first launch!

It's a fair compromise - IMHO - with the proponents as the tabbed UI as the
default. Granted, one could argue that doing this before at least some of the
140 open bugs
(https://bugs.documentfoundation.org/showdependencytree.cgi?id=102062&hide_resolved=1)
against the notebookbar are resolved is premature/irrelevant, but when it's
mature enough, then I believe that most people see this as the fair compromise.
But maybe I should speak for others less and let more people opine on that
point (so far on this bug, this is the position of Telesto, John Mills, myself,
Pedro, haevalencia, andreas_k; and Heiko seems to be neutral about it?).

> It is not required and it would not improve the UX for first time users, nor
> at user profile reset. Rather it would just get in the way and be
> superfluous for the vast majority of users. 

How would it get in the way more than a Tip of the Day?

> There are better and less intrusive ways of conveying "Getting started"
> guidance than with a pop-open "configure before proceeding" style dialog.

But the conscious, almost-explicit, user choice of UI is the compromise between
"current UI as default and that's that" and "Let's make the tabbed UI the
default". And the UI selection dialog is already biased in "our" favor, since
the default selection is menu+toolbars. How would you get close to an explicit
user choice between UI types otherwise?

(In reply to John Mills from comment #29)
> Your position is certainly untenable in the longer term etc.

To be perfectly honest - in the long run, I hope the fad of tabbed interfaces
will go away, and everyone will wonder why people had done this to
themselves... But that can hardly happen if the tabbed UI is not given a "fair
shake": Its proponents are making the valid point that LO is tilting the scales
too far in favor of the menus+toolbar interface. So my reason for asking Stuart
to agree with displaying the dialog itself is actually my _disdain_ for the
tabbed interface :-P  (plus the allowance for the possibility that I may be
wrong.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to