Difference between revisions of "DPL talk:Catlist"
From FollowTheScore
(comments) |
(more suggestions) |
||
| Line 1: | Line 1: | ||
| + | ==Suggestions== | ||
Nice. Thank you. Some suggestions: | Nice. Thank you. Some suggestions: | ||
| Line 5: | Line 6: | ||
* True/false select lists should be checkboxes | * True/false select lists should be checkboxes | ||
* <tt>linksto</tt> (+!) should automatically pull in all articles (or give an option to pull them in, only for various categories, etc) | * <tt>linksto</tt> (+!) should automatically pull in all articles (or give an option to pull them in, only for various categories, etc) | ||
| − | --[[User:Eep²|Eep²]] | + | * <tt>addeditdate</tt> and <tt>addpagetoucheddate</tt> should be a radio button pair to prevent this error: "%DPL-1.2.8-ERROR: You cannot add more than one type of date at a time!" Radio button pairs should be used for other either-or parameter combinations, if any. |
| + | * Make use of the "disable" HTML form option and Javascript/CSS in order to hide parameters that aren't necessary/usable relative to existing parameter selection. | ||
| + | * Make use of CSS and mouseover/hover effects to provide brief descriptions of parameters for easy reference. Also, since the parameter name (i.e. "notuses") is within the form, there's no need to expose that esoteric (and improper grammar/spelled) name when "does not use" is semantically correct. | ||
| + | -[[User:Eep²|Eep²]] 14:03, 26 July 2007 (CEST) | ||
Revision as of 14:03, 26 July 2007
Suggestions
Nice. Thank you. Some suggestions:
- Could use columns/table
- Need support for multi-select listboxes (Simple Forms limitation?)
- True/false select lists should be checkboxes
- linksto (+!) should automatically pull in all articles (or give an option to pull them in, only for various categories, etc)
- addeditdate and addpagetoucheddate should be a radio button pair to prevent this error: "%DPL-1.2.8-ERROR: You cannot add more than one type of date at a time!" Radio button pairs should be used for other either-or parameter combinations, if any.
- Make use of the "disable" HTML form option and Javascript/CSS in order to hide parameters that aren't necessary/usable relative to existing parameter selection.
- Make use of CSS and mouseover/hover effects to provide brief descriptions of parameters for easy reference. Also, since the parameter name (i.e. "notuses") is within the form, there's no need to expose that esoteric (and improper grammar/spelled) name when "does not use" is semantically correct.
-Eep² 14:03, 26 July 2007 (CEST)
