 | | Re: Creating Lugent Rating Criteria —Larry Pieniazek
|
| | | (...) the (...) reason (...) Easy fix... Different views, different UI. In the list or tree view, use radio buttons and a single submit. In the single article view, use multisubmit. ++Lar (25 years ago, 23-Apr-00, to lugnet.admin.general)
|
| | | |
| | | | | Re: Creating Lugent Rating Criteria —Matthew Miller
|
| | | | | (...) I think the UI should stay as consistant as possible.... (25 years ago, 23-Apr-00, to lugnet.admin.general)
|
| | | | | |
| | | | | Re: Creating Lugent Rating Criteria —Todd Lehman
|
| | | | | (...) Tradeoffs of that nature (increased speed in exchange for decreased consistency) can certainly be an improvement from an HCI POV when the UI item in question is or should be used frequently. But that's not the case here. --Todd (25 years ago, 23-Apr-00, to lugnet.admin.general)
|
| | | | | |
| | | | | Re: Creating Lugent Rating Criteria —Larry Pieniazek
|
| | | | (...) You're right. Now that we're only using one watered down dimension with a meaning such that only 1 in 10 articles deserves highlighting and one in 100 deserves spotlighting, you're absolutely right, "recommending" won't be used all that (...) (25 years ago, 23-Apr-00, to lugnet.admin.general)
|
| | | | |
