[Bug 52520] VisualEditor: Create a design guideline to minimize clicks and key presses
https://bugzilla.wikimedia.org/show_bug.cgi?id=52520 Andre Klapper aklap...@wikimedia.org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Andre Klapper aklap...@wikimedia.org --- Again: This won't be handled in Bugzilla, however pointing to a better place where to discuss would be very good. Playing the I know it's the wrong place but still I want to discuss it here card isn't much better either though. :) Please don't reopen as a sign of disagreement. Thanks. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 52520] VisualEditor: Create a design guideline to minimize clicks and key presses
https://bugzilla.wikimedia.org/show_bug.cgi?id=52520 James Forrester jforres...@wikimedia.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID Summary|create a design guideline |VisualEditor: Create a |to minimize clicks and key |design guideline to |presses |minimize clicks and key ||presses --- Comment #3 from James Forrester jforres...@wikimedia.org --- Of course, this is already our intention. There is nothing to create. Bugzilla is not really the right place to suggest user experience improvements like this - though walk-through data like you've given is hugely valuable, and if you have more I would love for you to share it. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 52520] VisualEditor: Create a design guideline to minimize clicks and key presses
https://bugzilla.wikimedia.org/show_bug.cgi?id=52520 rupert.thur...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #4 from rupert.thur...@gmail.com --- james, let me reopen this one please. there is a big difference between it is our intention (whoever our is) and a crystal clear guideline having as primary target: * minimize clicks and key presses * response time 3 sec this would make it so much easier for new developers as well. and so much easier for testers to point out that something is against the goal. as i tried to point out above with examples, people were and still are allowed to increase key presses and mouse-clicks considerable compared to the existing solution. i tried to look for design documents or mail references on some tech list to find a justification for this, but could not find one. you as a software developer surely know that nothing is more expensive than fixing a design bug. and nothing is more expensive than finding a bug late. just to take an arbitrary url to support this: http://blog.bootstraptoday.com/2011/12/25/early-detection-of-bugs-can-save-up-to-22-billion-yearly/ so, please do not play the a good thing but not the right place card. which then ends up nowhere. you can close the ticket if you either create this guideline, or successfully have a (public verifyable) decision in whatever place you consider right for a decision like this. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
