Ubiquitous User Interfaces

Might be a weird question, but...

I want you to envision a simple user interface (like a simple Visual Basic form on a computer screen.) This form covers roughly 2/3rd of the screen, and contains a couple columns of variables that are communicated from some external device. Maybe 20 variables total.

The variables populate the VB text fields, and then, based on whatever data is in those columns, the User (that would be you), can click a button to either enable or disable that external device.

Now, my question to you is: If you saw a form like that for the very first time, do you think you would need elaborate instruction, or would you get the gist of it pretty much right away?

Note that I am not asking whether you would need help in interpreting the variables (so that you would know what action to take, if any). Just picture the form ONLY.

Reply to
mpm
Loading thread data ...

Sounds pretty straightforward to me. As long as it's text and not pictograms, meaning "ON" and "OFF" or "EN" and "DIS".

--
Regards, Joerg

http://www.analogconsultants.com/
 Click to see the full signature
Reply to
Joerg

I think it would be pretty clear, as long as the button was labeled clearly with "enable/disable retroencabulator" or whatever. It would probably help if the values in the boxes changed frequently enough that I could tell that they were being updated from some external source, rather than being fields I was expected to fill in before pressing the button.

Of course this depends on be being basically computer-literate enough to be familiar with the common GUI symbology of textfields and buttons --- I'm sure a millennia-frozen Piraha tribesman would have a harder time of it.

--
   Wim Lewis , Seattle, WA, USA. PGP keyID 27F772C1
  "We learn from history that we do not learn from history." -Hegel
Reply to
Wim Lewis

ly

p

at

it.

Thanks --

It's a little bit of an argument I'm having with a friend and engineering colleague (an MIT grad), but computer-wise, he's still in the stone ages. For example, I only recently turned him on to Windows XP, and USB devices, and he thinks they're the greatest thing ever. (Previously, he was using DOS and Windows 98). He also still drives a carbuerated clunker, with the factory 8-track (actually, it's kinda nice), and refuses to shoot digital, opting for color slide film (which they hardly even make, and/or process anymore...) He's older, so I get it. And generally, I would have to say, has a tack-sharp mind.

Anyway, you can see the problem.

I say any teenager could plop down, see that form, and know exactly what to do. My 10-year-old nephew could do it. I guarantee it. He claims, it's not obvious (but is this flavored because he's a DOS wielding dinosaur...) ??

BTW - This isn't for a product launch or anything. It's just a screenshot that I want to put in a report, and he doesn't for the reasons just mentioned. He claims the screenshot raises more questions than is answers (it doesn't). I say "a picture is worth a thousand words". Which, necessarily implies, a word is only worth 1/1000th of a picture.

Sure, we could say everything in text, but my experience leads me to believe the average person can "see" better than they can "read and comprehend". Put another way, you could describe a pretty lady in very exacting terms, but to fully appreciate same, most guys would rather just the photo.

-mpm

Reply to
mpm

Have you introduced the guy to tool tips? They're a good way to provide someone with more information that you really want cluttering up your main GUI, but less intrusive than forcing them to hit F1 to bring up an entire help file.

---Joel

Reply to
Joel Koltner

More than JUST un-labelled "values" in ?boxes? would be mandatory..so expand definition.

Reply to
Robert Baer

.so

The 20 or so variables are each proceeded by a descriptive label. The labels are terms that are in common use, both by the public, and by the intended audience. The variables are mostly numeric.

For example, one pair might read: "Device Status:" - "Powered ON". Stuff like that.

Reply to
mpm

"mpm" schreef in bericht news: snipped-for-privacy@f25g2000yqc.googlegroups.com... On Sep 7, 9:49 pm, snipped-for-privacy@underhill.hhhh.org (Wim Lewis) wrote:

|It's a little bit of an argument I'm having with a friend and |engineering colleague (an MIT grad), but computer-wise, he's still in |the stone ages. |For example, I only recently turned him on to Windows XP, and USB |devices, and he thinks they're the greatest thing ever. (Previously, |he was using DOS and Windows 98). He also still drives a carbuerated |clunker, with the factory 8-track (actually, it's kinda nice), and |refuses to shoot digital, opting for color slide film (which they |hardly even make, and/or process anymore...) He's older, so I get |it. And generally, I would have to say, has a tack-sharp mind. | |Anyway, you can see the problem. | |I say any teenager could plop down, see that form, and know exactly |what to do. |My 10-year-old nephew could do it. I guarantee it. |He claims, it's not obvious (but is this flavored because he's a DOS |wielding dinosaur...) ?? | |BTW - This isn't for a product launch or anything. |It's just a screenshot that I want to put in a report, and he doesn't |for the reasons just mentioned. |He claims the screenshot raises more questions than is answers (it |doesn't). |I say "a picture is worth a thousand words". Which, necessarily |implies, a word is only worth 1/1000th of a picture. | |Sure, we could say everything in text, but my experience leads me to |believe the average person can "see" better than they can "read and |comprehend". |Put another way, you could describe a pretty lady in very exacting |terms, but to fully appreciate same, most guys would rather just the |photo. | |-mpm | |

In a similar case I used an old DOS-based Turbo-C compiler and wrote a command line controlled program. Those character based window graphics are perfect for defining all kind of text fields holding values and menues. The latter can easily be programmed to be controlled by either a keyboard or a mouse. Works flawless using XP. The program that is. I run the compiler using an old W95 PC.

Another possibility is the even older GW-Basic. Still have some program running on an XP machine as there is no need to rewrite it. Do not use a mouse with it. Even don't know whether GW ever supported a mouse.

petrus bitbyter

Reply to
petrus bitbyter

Put a menu bar or legend at the top/bottom that makes the button/key function clear. Often, such a menu will have several modes and that menu will change depending on what mode the app is in.

Example: When scrolling through the list, the Up/Down buttons (PgUp/PgDn keys, etc) will scroll and there will be a 'Select' key. Once an entry has been selected, the Up/Down button functions will shift to changing the parameter value of that selection.

If the menu indicates these functions clearly, the interface is pretty intuitive. For 20 parameters, you could even use an 80x24 text terminal and do the menu with curses.

formatting link

There are many libraries for platforms like Java mobile or workstation that make building such interfaces easy.

--
Paul Hovnanian  paul@hovnanian.com
----------------------------------------------------------------------
 Click to see the full signature
Reply to
Paul Hovnanian P.E.

Put this: "The variables populate the VB text fields, and then, based on whatever data is in those columns, the User (that would be you), can click a button to either enable or disable that external device."

at the top of the form, maybe in a label box.

Cheers! Rich

Reply to
Rich Grise

Doth make it understandable..

Reply to
Robert Baer

QB never did. At least you could hack it with the interrupt directly (which is accessible in QuickB), or a library, or a splash of assembly. I don't even remember if GW supported external function calls like those. Maybe you'd have to read the serial (let alone PS/2!) port directly to do it. Drivers, who needs 'em!

Tim

--
Deep Friar: a very philosophical monk.
Website: http://webpages.charter.net/dawill/tmoranwms
Reply to
Tim Williams

Late at night, by candle light, mpm penned this immortal opus:

Dynamically label the buttons for whatever action they'll take when clicked. For example, if the fluxcapacitor is enabled the button is labeled DISABLE, disabling the FC changes the button text to ENABLE. A current status field might be nice if it fits.

- YD.

--
Remove HAT if replying by mail.
Reply to
YD

A comment on this particular use of dynamic buttons:

Consider the latency of the app when using one button to enable/disable some function. Together with the inevitable impatience of some users, this will result in the damned thing getting toggled on and off repeatedly as the button is pressed repeatedly.

Imagine a crosswalk signal that you could turn back off with the same button. Or an elevator.

--
Paul Hovnanian  paul@hovnanian.com
----------------------------------------------------------------------
 Click to see the full signature
Reply to
Paul Hovnanian P.E.
[snip]

Sounds useful ;-) ...Jim Thompson

--
| James E.Thompson, CTO                            |    mens     |
| Analog Innovations, Inc.                         |     et      |
 Click to see the full signature
Reply to
Jim Thompson

Late at night, by candle light, "Paul Hovnanian P.E." penned this immortal opus:

Good point. Had that issue in a supervisory system controlling the motors. The operators never got used to the about five seconds lag, so I ended up replacing the toggle buttons with split on and off ones. Lots of fun watching them furiously click the on button until the corresponding symbol changed color. Total waste of breath telling them that it wouldn't go any faster than clicking once and wait a bit.

- YD.

--
Remove HAT if replying by mail.
Reply to
YD

Aircraft have that problem with the overhead reading lights. Push the button. Now that the lights are controlled over a digital buss, when things get busy there's a few seconds lag. So the passenger pushes the button again. Repeat a few times. Since the system queues the commands, the light will eventually start flashing on and off.

--
Paul Hovnanian  paul@hovnanian.com
----------------------------------------------------------------------
 Click to see the full signature
Reply to
Paul Hovnanian P.E.

Sounds like poor system design to me!

Reply to
Joel Koltner

Is not Centralized Power problem. Is greedy, impatient Imperialist fingers.

--Winston

--
I pride myself on my unimportance.
(One must excel at something, or what
 Click to see the full signature
Reply to
Winston

Well, he did work for Boeing, didn't he?

--
Politicians should only get paid if the budget is balanced, and there is
enough left over to pay them.
Reply to
Michael A. Terrell

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.