jhrothjr wrote: > Phlip makes an interesting distinction between > programming and authoring. I don't think he's > brought that distinction up in this thread, but > he's made it in a number of other threads, and > it makes perfect sense to me.
That distinction adds risk here. Some reviewers thought "authoring" meant "usability tuning". I use "authoring" to mean essentially "screw test-first". For example, nobody is going to test-first the pixel location of a Cancel button. But sometimes you feel like implementing "drag-and-drop" by copying some www.codeproject.com code and pasting it into your program. If your program does not drag or drop some weird complex entities, then skipping the research required to test-first boilerplate code is mostly harmless. > GUI design is different enough that it takes > a substantially different skill set. This is usability. > I think that this explains why we have such > a hard problem with testing them. Their wizards and form painters tempt us. Then, they work and have no bugs, so we have no incentive to make our test rigs more attractive and useful than wizards or form painters. ===== Phlip http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/extremeprogramming/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
