On Fri, Aug 25, 2006 at 11:16:44PM +1000, Tim Starling wrote:
If it's too much then don't type it. If you
think the feature won't be used
at all, then I think you have another thing coming.
Ken Jennings says that's "another think coming". :-)
Dunno about
everyone else, but my usual editing sequence goes
something like this:
1. Make a change
2. Type an edit summary and set the watch/minor checkboxes
3. Preview
4. Save or go back to 1.
Yes, so does everyone's, that's because we don't have an interactive message
box to type into. Behaviour will change according to features.
Sometimes. You hope. :-)
Let me also say this: if your typical editing
behaviour is to open the edit
box, change some little thing, and save it immediately, then you're one of
the culprits of the edit conflict problem. You're the kind of user that the
"please don't edit this" message is aimed at. Some users want to spend
longer editing and reviewing a change, and they shouldn't be penalised for
their extra dedication to correctness.
No, but they person fixing one thing shouldn't be penalized, neither,
should they? Making them *both* happy was, I thought, your target here.
Enough chit chat, where's my Person 1? I want
concrete features and I want
them now. The feature is a simple one, if we can assemble the right skills,
just a few hours' work each. But to get us started, someone needs to make
that UI mockup.
Alas, it's not me. I'll shut up now.
Cheers,
-- jra
--
Jay R. Ashworth jra(a)baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA
http://baylink.pitas.com +1 727 647 1274
The Internet: We paved paradise, and put up a snarking lot.