[Libreoffice-ux-advise] [Bug 91820] Reorganization of the menu bar for Calc

[bugzilla-daemon at bugs.documentfoundation.org]

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

Joel Madero <jmadero.dev at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jmadero.dev at gmail.com

--- Comment #25 from Joel Madero <jmadero.dev at gmail.com> ---
As someone who frequently uses Spreadsheets I find the current organization to
be a *dramatic* change with little to gain and lots of confusion. I've found
myself annoyed often looking through the new menus and trying to figure out
where things were moved. There is *some* value in the status quo and this
approach of "logic trumps all" and *no weight* given to the status quo (i.e.,
where things are because people are used to that) is problematic.

To me I've been somewhat shocked at how these changes occur with almost no
consensus (basically jay pushing a ton of changes that he finds to be logical)
and they happen *in mass* so instead of gradual changes it's dramatic shifts
that can *significantly harm* workflows.

Furthermore, I've been surprised that when I suggest a change that seems to be
logical I *do* get the "status quo is valuable in and of itself minus PROOF
that there are gains from change" but then with toolbar changes it's kind of
just a mass change and a "users can deal with it" mentality. Proof is not
defined as "this makes sense on some philosophical level" - it means real
gains....as in .... were users confused about where these things were before?
Were people actively complaining? Was there some harm being done by the status
quo?

An example of this bug 96299 where there was push back on changing default
behavior for cross-references basically because there is no proof of a gain and
the status quo is valuable in and of itself.

I'm not interested (nor do I have time) to spend hours debating over the
merits. My points can be summarized as followed:
1) Status quo has some value - even if maybe some kind of logic would say move
things - thus a balanced approach would be nice;

2) Gradual changes over longer periods of times can leave users with less
interruptions to their workflow than mass changes

-- 
You are receiving this mail because:
You are on the CC list for the bug.