Bug 161209 - Remove/replace the inappropriate marketing dialog/wizard on first run (as implemented for bug 159573)
Summary: Remove/replace the inappropriate marketing dialog/wizard on first run (as imp...
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.8.0.0 alpha1+
Hardware: All All
: medium normal
Assignee: Heiko Tietze
URL:
Whiteboard: target:24.8.0
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-22 07:54 UTC by Eyal Rozenberg
Modified: 2024-05-31 13:08 UTC (History)
15 users (show)

See Also:
Crash report or crash signature:


Attachments
First use dialog screens (647.88 KB, application/zip)
2024-05-22 08:20 UTC, Eyal Rozenberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2024-05-22 07:54:46 UTC
Take a recent nightly, and run it in safe mode. You will see a dialog/wizard come up when you first start one of the LO modules.

This wizard, as it stands, needs to be either removed or replaced with something very different.

Why?

1. The wizard is "pure marketing": It doesn't provide actionable information for the new user; it tries to convince the user that LibreOffice is good. That is a ridiculous waste of time, as the user has _already chosen_ to use LibreOffice. 

2. The wizard is an obstacle for the user actually using LibreOffice - both literally, by covering the application UI and requiring interaction with the wizard, and conceptually: The user has gotten ready to take in the look and feel of the new application, and what we're insinuating is that they should expect modal dialogs with a lot of useless fluff.

3. The user has already seen the splash screen, so the function of "this is LibreOffice" is not strictly necessary (and if one wants to expand the messaging on the welcome screen with a few words, we could do that; open a separate bug)

4. WE NEED A WIZARD FOR SOMETHING ELSE (!) :  If we are to have any modal dialog/wizard on first startup, it is for something of critical importance, e.g. the choice of UI mode (menus+toolbars vs tab-bar). That has been the subject of much discussion; see:

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

it is as though whoever committed the new dialog/wizard just completely ignored this.
Comment 1 Heiko Tietze 2024-05-22 08:02:10 UTC
+1
Comment 2 Mike Saunders 2024-05-22 08:10:27 UTC
Added my thoughts on https://bugs.documentfoundation.org/show_bug.cgi?id=137931#c62
Comment 3 Eyal Rozenberg 2024-05-22 08:20:26 UTC
Created attachment 194267 [details]
First use dialog screens
Comment 4 Pedro 2024-05-22 08:31:21 UTC
I was going to provide some of the same arguments as Eyal. Since he already provided the bullet points with the drawbacks I will just say that I fully agree with him.first run dialogs should always provide something actionable. A UI selection wizard should be the priority.
Comment 5 Heiko Tietze 2024-05-22 08:33:53 UTC
The first-run-welcome mode is just a flavor of this WhatsNew dialog. I guess you want this to be gone as well?
Comment 6 John Mills 2024-05-22 09:00:39 UTC
I think a what's new dialog is helpful personally. If we move to an auto updating mechanism then a simple single dialog is useful. We see something similar with Mozilla Firefox.

But that is independent of the UI/Colour Mode selection.
Comment 7 V Stuart Foote 2024-05-22 11:27:53 UTC
-1, Nope Heiko worked up the framework for bug 159573, with the dummy screens noted.

We're waiting on Marketing to clean up the content for string freeze at 24.8, and going forward with MAR based autoupdates make this a very necessary 'on first launch' information delivery.

@Italo, Mike -- action to you...
Comment 8 Heiko Tietze 2024-05-22 11:38:03 UTC
Patch submitted that reverts the dialog. Release notes are fine for now.
Comment 9 Eyal Rozenberg 2024-05-22 12:21:46 UTC
(In reply to V Stuart Foote from comment #7)
> -1, Nope Heiko worked up the framework for bug 159573, with the dummy
> screens noted.

I'm sorry that I'm asking for a reversion of work Heiko (and others) has done. However - if the open bugs regarding the first-use dialog  had been notified with a comment or a 'related' marking - then these objections would have been voiced earlier.

> We're waiting on Marketing to clean up the content for string freeze at
> 24.8, and going forward with MAR based autoupdates make this a very
> necessary 'on first launch' information delivery.

Let's separate what happens when you update LO and when you launch it for the first time. The UI mode and light/dark mode choice is important on the first launch ever, and not undesirable on version updates.

(In reply to Heiko Tietze from comment #5)
> The first-run-welcome mode is just a flavor of this WhatsNew dialog. I guess
> you want this to be gone as well?

Actually, no, I don't :-)

I have a certain (semi-formed) opinion about presenting what's-new information after an update - but I would rather not even state it here, since this bug is _strictly_ about the first-use-ever.
Comment 10 Noel Grandin 2024-05-22 14:14:01 UTC
(In reply to Eyal Rozenberg from comment #0)
> 
> it is as though whoever committed the new dialog/wizard just completely
> ignored this.

This kind of comment is unnecessary. Everybody here works hard and mostly does this stuff transparently.

This feature in particular had __thirteen__ different sets of eyes on the bugzilla, and 4 reviewers on the relevant gerrit patch.
Comment 11 Commit Notification 2024-05-22 19:20:46 UTC
Heiko Tietze committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/1bd9747a126a3e82b6093c2b4af3b3a74774a3e9

tdf#161209 - Reverts WhatsNew/Welcome dialog

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.