Bug 192340 - Show config assistant after first login
Summary: Show config assistant after first login
Status: RESOLVED DUPLICATE of bug 211144
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-11 16:53 UTC by Vincent Petry
Modified: 2009-10-22 00:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Petry 2009-05-11 16:53:30 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    SuSE RPMs

After the first login of a new user, it would be a good idea to present a configuration assistant to help configuring the basic settings for this user. As far as I remember, KDE 3 used to have that before.

For example:
1. Does the user want to use single click or double click when selecting files ? (I prefer double click)
2. Which shortcut preset to use ? (I like the one with the windows key)
3. Does the user want to enable desktop effects ?
4. Region and language
5. Personal information ? (about me)
6. etc...

Any other basic configuration could be put here.

This might be useful for beginners, because they will maybe need some time at the beginning to figure out how to change these basic settings from the control panel. This welcome screen would offer them a chance to do that at the beginning.

Of course there should be a "skip" button for experienced users to be able to directly jump to the desktop.

Personally I think that the single click (default choice) is not very convenient/confortable, but I still have to use it to click through the config icons until I can change it. That's why I think it would be nice to be able to change it from the beginning.

Any other suggestions ?
Comment 1 Dario Andres 2009-10-22 00:41:03 UTC
Merging with bug 211144. Thanks

*** This bug has been marked as a duplicate of bug 211144 ***