From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,3d76796391769899 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx02.iad01.newshosting.com!newshosting.com!83.128.0.12.MISMATCH!news-out2.kabelfoon.nl!newsfeed.kabelfoon.nl!xindi.nntp.kabelfoon.nl!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Mon, 14 Jun 2010 17:59:49 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Improving the first contact with Ada References: <41d3829e-286d-4894-9140-31343bfa75ac@o12g2000vba.googlegroups.com> <82y6fgxncs.fsf@stephe-leake.org> <82aarux3g3.fsf@stephe-leake.org> <2da7ba0b-0c45-4c7b-a523-b3438e43212a@j27g2000vbp.googlegroups.com> <87k4qsapgr.fsf_-_@ludovic-brenta.org> <096e5f19-ed4d-4c02-b889-88856ac0d5c7@5g2000yqz.googlegroups.com> <87y6eiohup.fsf@ludovic-brenta.org> <472c5f8a-111f-429f-acf5-b50b76079241@3g2000vbg.googlegroups.com> <87typ6ocf4.fsf@ludovic-brenta.org> <5b782537-f2cb-4568-9e59-7441269372f1@z10g2000yqb.googlegroups.com> <4c1606e8$0$7666$9b4e6d93@newsspool1.arcor-online.net> <4c162962$0$7653$9b4e6d93@newsspool1.arcor-online.net> <1ghjss4zhtoze$.d3n0uvh0m3d6.dlg@40tude.net> In-Reply-To: <1ghjss4zhtoze$.d3n0uvh0m3d6.dlg@40tude.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4c1651f6$0$7662$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 14 Jun 2010 17:59:50 CEST NNTP-Posting-Host: 03a1990b.newsspool1.arcor-online.net X-Trace: DXC=jUK`O3YNWZQ=>bdbdS?M0Yic==]BZ:af^4Fo<]lROoRQ<`=YMgDjhgRdVcF>55@P_Qnc\616M64>ZLh>_cHTX3j]b0dmfJTo^@P X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:11713 Date: 2010-06-14T17:59:50+02:00 List-Id: > What about an operator continuing repeating the same sequence of actions > ignoring popping up message dialogs crying that it FAILED. (See below) The idea is that as an application interface designer, you provide a GAI, not a GUI. That is, a Graphical Application Interface that is somewhat like a scripting interface. This obliges the GAI (sic) programmer to provide rock solid GAIs that can not mess things up yet will provide all possibilities to operators with suitable knowledge. No damage, many degrees of freedom. > Record the time between window creation and the cancel button press. If the > delay is too short, give another warning. After tree warnings the operator > receives one point. Three points are mailed to his superior. (:-)) Credit point systems won't work here, though repeated pop ups could create more work heat throughout the organization. Case in question: an operator sees a dialog window and has a healthy attitude towards dialog windows. That is, he/she presses ENTER after ignoring both any text and, quite naturally, the consequences of dismissing the dialog which is actually a rescue dialog. Using a big red button instead of a standard gray OK did not change behavior. (Some handbags are red, too, after all...) The dialog said, in attempt to get the operator's attention, "If you press ENTER, you will get fired!" Guess what? This message has no effect on the operators' attitude towards dialog windows. The dialogs look exactly like at home where they get in the way (and out of the way!) without noticeable consequence. Like blowflies on the screen. He/she won't get fired, either. Reasons: - Firing requires work in superior organizational units, and recruiting efforts. - There isn't a massive threat from the insurance company in case of not so massive consequences of dialog dismissal. - Effects on others (clients, passengers, ...) overall are such that they do not affect superiors' standing, hence provide no incentive to request effort and/or money for a solution. Therefore, occasional itching (error dialogs) can be safely ignored. Solution? Ignorance is not so easily employed when there is nothing to ignore! Therefore, a strategy might be to disable all interface functions after dialog dismissal and require attention: Print in bold letters: "You Lose!" This creates ... panic, cynicism, lies? But! There is attention, at last! And ... a need for work, making phone calls, experts sent for etc. Work that nobody wanted to know about in the first place, right? :-)