GNOME Bugzilla – Bug 634906
Re-enable splash screen preference option
Last modified: 2018-06-29 22:47:23 UTC
I recently removed the preference option to enable/disable the splash screen at startup in an effort to simplify the GUI. Apparently some users do like to disable the splash screen (mostly for development reasons). So this bug proposes to add this option on the command line, similar to what the Gimp does. That would allow command line users to disable the splash screen.
Hi Geert, I dislike the removing of the preference. The situation of business users: On the start of your session you open mostly automaticly a bunch of programs like OOO, GC, a mail client, a chat client, a few browser windows, ... and all the splash screens hide the dialog of your passwort manager - so most programms are waiting until this damned splash screens disapper and you can enter your master password. The command line option is much less user friendly, as the normal user will start the programs by the menu and is not willing to learn the menu editor to add command line options. She has no time, fears to break the system, ... while a preference is a simple thing. In my eyes the preference was a small detail of the kind, which makes a program friendly. So I would opt, to give us the preference back. Just my 2¢.
Ok, several reasons have been given by now to keep the Splash screen preference option (none of which were given when I first proposed to remove the option unfortunately). I intend to restore the option, but am now facing a dilemma: * With the option being removed, the translatable option string has been removed from the po files as well. Several translators have already submitted new translations in po files that don't have this string anymore. * If I now re-add the option, I re-introduce a string that used to be translated, but isn't anymore. What is the proper way to deal with this ?
Committed in r19828.
Sorry Geert, I was too busy the last two month to follow the discussion close to realtime. Thanks. :-)
No worries, I wasn't pointing fingers at anyone. I just wanted to clarify how we ended up in this situation in the first place.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=634906. Please update any external references or bookmarks.