On Mon, 2005-10-03 at 08:03 -0500, Joe Lapp wrote: > >From: Redeeman <redeeman@xxxxxxxxxxx> > > i dislike this, instead you should just write what is required, so if > > its either minor edit, or summary, it will write that with small read > > text - or perhaps.. > > I can imagine that your approach would be better for some scenarios. It > doesn't apply to mine, though, as I am the only editor of my site and I don't > need to see summaries for minor edits. > > I do wonder whether always requiring summaries, even for minor edits, would > make requiresums so painful that no one would turn it on. And if it were on, > I'd probably just put 'x' in for minor edit, or some such -- just so I didn't > have to say "changed spelling of 'teh' to 'the'" or even just "fixed > spelling." > > > what if the submit button just wasnt active untill either requirements > > were met? isnt this possible through javascript? > > That is FANTASTIC idea. The button should be de-highlighted until pressed. > Form buttons do have a 'disabled' property that we should be able to take > advantage of. This certainly beats a dialog box. > > It appears that there are three levels of minor edit button on the table: > > - No minor edit button > - Either minor edit or summary required > - Summary always required to come back to a proposal i sent earlier, which i do believe to be the best solution allaround. ---- minor edit button only comes to logged in users. if $conf['requiresums'] == 0: sums are never required, but optional (for both minor and normal edits) if $conf['requiresums'] == 1: sums are required for normal edits if $conf['requiresums'] == 2: sums are required for minor and normal edits. ---- and then in "corrospondance" to the requiresums option, with javascript, the submit button will only be enabled if the condititions requiresums specifies are met. > > Should this be a level configuration variable of some sort? Or is this > getting out of hand? > > ~joe -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist