Revision [3701]
This is an old revision of UserSettingsPanel made by JavaWoman on 2004-12-26 21:06:31.
UserSettings Panel
Some preliminary ideas for an improved UserSettings panel.
Feel free to add content/suggestions.
The issues I'd like to address in this page are the following:
- What options should be user-configurable?
- For each option, how should Wikka store it?
- cookie parameter
- session parameter
- user_table field
- other
User table field(s) or maybe a separate user table that stores only the settings that are not default. Decision would depend on efficiency; would require some analysis... --JavaWoman
- How should user options be arranged/grouped/displayed in the UserSettings page?
I also propose that we keep the login/logout interface separate from the user settings page.
1. Preliminary list of user-configurable options
- User related
- Email address [string]
- Password [string]
- Date/Time
- Time zone [list]
- Date format [list]
- Layout
- Default skin [list] (beta - see TestSkin)
- Custom skin [link] (beta - see TestSkin)
- Custom menus [link] (forthcoming?)
- Show comments by default [boolean]
- Editing
- Doubleclick Editing [boolean]
- WikiEdit GUI [boolean]
- Changes & revisions
- RecentChanges display limit [integer]
- Page revisions list limit [integer]
- Comments
- Paged comments limit [integer] (beta)
- Comments start page [list] (forthcoming?)
- ...
2. How to store each option
Forthcoming :)3. UserSettings panel design
After you've added your suggestions in the list above, please edit accordingly the source of this sample HTML formI don't think having the links for skin and menus within the form is a good idea - you'd effectively be leaving the form - and how do you get back? You may even forget...
Maybe have menus just a separate page, and in user settings form below have just a checkbox to create a user-skin IF it doesn't exist already (i.e., don't even show that checkbox when the file exists). And even that might be overkill - just having that on a separate page, too might be better.
Also don't forget that a non-registered user should be able to choose a skin as well - only have that choice stored in the session rather than the database; i.e., no personal default. So it's easier to just have a single page for everyone that just behaves a little differently for registered and non-registered users. --JavaWoman
User Settings
CategoryDevelopment
