Re: Touch screens and wxPython

From: Gene Mosher <gene_at_viewtouch_dot_com>
Date: Wed Dec 03 2003 - 14:07:20 CST

Karl Auerbach wrote:

>My own experience with wxPython is that on Linux the
>windows/controls/dialogs are more asethetic, flexible, and responsive than
>those in Java but are still not really visually stunning. On Windoz
>wxPython uses native controls when possible, so it inherits most of the
>Microsoft characteristics and aesthetics.
>I've just checked - the wxBitmapButton object in wxPython can have three
>different bitmaps: for unselected, for selected, and for disabled. That
>gives some flexibilility, but doesn't allow for "effects" (such as a
>flash) when the button is "pushed".
>Generally people who see wxPython stuff think that it looks more
>"professional" on Windows than on Linux. But then again, I think most
>user interfaces look better on Windows than on Linux (which, being a Linux
>wannabe, I find disturbing.)
Well, when the gui is 100% vector based, as this one is, then there's
absolutely no way that it could look different when the OS changes.

>1. The overall screen is "busy", if a ballot had that much stuff I suspect
>that voters would often complain of being confused.
All of these are snapshots which have been collected from our point of
sale application which, of course,has absolutely no regard for the task
of assisting a voter in building a voter's ballot. As I build a gui for
the specific purpose of assisting the voter, then you can be sure that
that gui will reflect absolutely no regard for the needs of people who
operate restaurants.

>2. I suspect that the button spacing is too close for use on a ballot. We
>gotta expect people who are older and less capable than the typical
>restaurant wait-folk.
The gui tools will setting button spacing to the ideal, as soon as it
can be determined to everyone's satisfaction what that might be. This
is true for any gui issue. First the project team establish the gui
design targets, or at least provide some consensus on what the targets
are, then I join with other team members and provide a way to reach the

>3. In an earlier post I suggested having a check box in addition to a
>visual change on the button itself. There was at least some positive
>reception on this. Do you think that is a useful thing to have or would
>you think that the same information can be conveyed in the button itself?
> --karl--
I think it's a great idea to have check boxes to supplement visual
feedback originating within a button. By the way, the last thing I want
to be now or ever is an arbiter. I'm only interested in providing a gui
that satisfies this organization's design requirements and which ensures
that our voting system is demonstrably superior in every way to any
proprietary voting system out there now or ever. There's no doubt that
the gui is the standard by which the entire system will be judged.
That's why the gui has to be top notch. That's why it has to be totally
application specific. The application specific gui toolkit that I'm
using has been built for exactly such situations as this.

I'm looking forward to working with you all. I'm still struggling to
get over the influenza, however, and I'm not able to do all that I
normally could. Perhaps by Thursday I'll be OK.

Gene Mosher
= The content of this message, with the exception of any external
= quotations under fair use, are released to the Public Domain
Received on Wed Dec 31 23:17:04 2003

This archive was generated by hypermail 2.1.8 : Wed Dec 31 2003 - 23:17:18 CST