[dokuwiki] Re: plugin and config mgrs

Chris Smith wrote: 
Anika Henke wrote:


2. 'Reference to non-existent ID "config__disableactions"', meaning


I guess in staying true to the "intent" of the html spec, the "label" for this particular setting should not be a <label> but a <span class="somethign">. or is it reasonable to use a <label> without it being associated with an individual form control?

Yes, omitting the <label> would be more semantic. But exchanging it with <span> or adding any class is not needed -- just omit it.

"The LABEL element associates a label with exactly one form control."
This specific label does not label one form control, it "feels" like labelling a group of several form controls, but labels indeed nothing.


Other things I noticed about that "Disable DokuWiki actions" section:
The info on whether or not any of the checkboxes show the default or protected value does not seem to work. And the "Other actions" will turn white when a checkbox is checked ...

Hmm ... Something that could solve many "problems" there could be a multiple select!?

Not really. Two controls would still be needed, as there needs to be some way to handle "other". I am not so keen on multiple selects, I think ticked boxes are clearer. 

Those remaining two controls could be divided into "Disable DokuWiki
core actions" and "Disable other actions" ...
But I am not keen on multiple selects, either. I mainly dislike that you
unintuitively have to hold Ctrl while choosing more than one option, and
if you forget that, you'll "loose" all other before chosen ones ...
Checkboxes are far more intuitive.


Given the settings class has complete control of the html required to display the setting, its possible to work something out that will better follow the style of the rest of the page.

How's about:
- label shown on blue/white/pink if checkbox value is default/not-default/protected
- other input box shown with blue/white/pink background if value is default/not-default/protected. 

As long as the the same rule is applied to each element ...


BTW - what was the ideal solution for indicating the enabled/disabled status of individual plugins & the button/link to toggle that status?

Hmm, things have only been half-decided ...
First I suggested a fourth button, then you wanted to keep a checkbox, but agreed on having it labelled. Another suggestion you made was "using an image button, with say a tick for an active plugin, a cross (or some other symbol) for a disabled plugin", which I think is the best compromise. (And as I wrote before: With an image button you wouldn't need the save button anymore.)

And what about making the info button a link on the plugin title instead?


Anika

--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Other related posts: