Re: [OVC-demo-team] Focus on ballot GUI

From: Eron Lloyd <elloyd_at_lancaster_dot_lib_dot_pa_dot_us>
Date: Thu Feb 05 2004 - 08:47:43 CST

Greetings Anand,

On Thursday 05 February 2004 8:15 am, Anand Pillai wrote:
> Just some of my ideas ...
> I think that if we use Python the question of internationalization
> is taken care of since Python supports unicode by default.

Certainly. Supporting unicode won't be a problem at all. What I meant was
localizing all UI strings, to allow for language switching. Alan's mockup
hints to Spanish and French. Qt makes this incredibly easy. We should then
produce the ballot XML in each language as well.

> We could use a key as a sort of language-toggle switch which can switch
> the display by cycling through a set of pre-defined language fonts
> in a pre-defined order.
> I would suggest another key which can maximize the GUI and bring
> it to normal size, another toggle switch( Say the "space" key ).
> Then a third toggle key can hide and show the on-screen keyboard,
> so that the user can bring it on when he wants to enter data and
> hide it when he wants to validate what choice he made.

Good ideas. Should these be only keybindings or do we want on-screen buttons
as well? Perhaps for the write-ins, each write-in field will activate the
keyboard, which then produces a label for that field.

> I am not sure of the font enlargement. Does Qt have anything
> like "sizers" (wxWindows) which takes care of widget sizing ?

Definitely. Qt has fantastic layout and geometry classes.

> Thanks
> -Anand



> ----- Original message -----
> From: "Eron Lloyd" <>
> To:
> Date: Thu, 5 Feb 2004 07:39:40 -0500
> Subject: Re: [OVC-demo-team] Focus on ballot GUI
> Heh, it is kind of confusing in that this list sets Reply-To when most
> others
> don't. David, I'm sorry if I've been a bit too vocal for your or anyone
> else's liking over the whole UI issue. I don't mean to be difficult; it's
> just my nature to always want to be able to deeply understand the things
> I
> get involved with, plus the fact that I'm coming into this project with
> very
> real goals and preconceived notions about what should be done and how.
> While I truly respect the spectrum of expertise of the members of this
> project, I too have quite a bit of background in this area and need more
> than
> just a simple directive for why certain choices were made. That aside,
> I'm
> trying hard to restrict my creative juices and assist in getting this
> primary
> objective completed. As I said before, I'm building up a prototype now
> while
> trying to maintain a strict adherence to the guidelines. Before we go too
> far, we should structure the Dev. team a bit more and all be on the same
> page
> as far as our design goals and objectives (a timeline would help, too).
> The basic architecture document summarizes the ballot mockup, XML
> schemas, and
> requirements for a MVC design. Besides that, there are a few items that
> don't
> seem to be mentioned (I can't think of them all, heres a start):
> 1. There is a button for language switching. Is the entire application
> supposed to support l10n strings? What languages? Is this just a placebo?
> 2. Are we to provide for font enlargement, too? Doing so immediately
> breaks
> Alan's pixel-precise positioning, obviously breaking the resolution
> boundaries. In my design, I allow for scrolling (horizontally) since I
> develop in 1024X768 and wanted to accommodate for this adjustment.
> 3. There still hasn't been any discussion on how to factor out the audio
> code
> to remove it's curses dependancy. Is Jan still working on this?
> 4. It's going to take some time to get the look and feel exactly right.
> Even
> in Python, I'm having to resort to low-level drawables and custom widgets
> in
> Qt to piece things together. Doing stuff like that admitly makes it
> frustrating to think this is simply "throw-away" code. Guess it is good
> exercise, though.
> 5. How should we handle write-in entries? There is mention of an
> on-screen
> keyboard; is this the route we're taking? Do we need to accommodate any
> accessibility issues? What about error handling and input validation?
> 6. Where is all the other code? CVS is quite bare besides BVA, RII, and
> the
> printing module. Will there be tabulation and ballot verification code?
> Sorry for the barrage of questions, just throwing them out there for
> anyone to
> answer, really. The list seems very quiet; I hope I haven't scared
> everyone
> off...
> Take care,
> Eron
> On Wednesday 04 February 2004 11:10 pm, David Mertz wrote:
> > > Hi Alan,
> > > I'm sure you've seen a few people on the demo list going off in
> > > different directions about all the possible different designs for a
> > > ballot GUI...
> >
> > Oops... I meant to write to Alan, but failed to take out the list CC:.
> >
> > Oh well, you've all seen my prior notes referred to. I guess it's time
> > to fire me as dev lead for my poor email control :-).
> >
> > ---
> > [This E-mail scanned for viruses by Declude Virus]
> ---
> [This E-mail scanned for viruses by Declude Virus]
> --
> Anand Pillai

Eron Lloyd
Technology Coordinator
Lancaster County Library
Phone: 717-239-2116
Fax: 717-394-3083
[This E-mail scanned for viruses by Declude Virus]
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
Received on Thu Apr 1 02:40:16 2004

This archive was generated by hypermail 2.1.8 : Thu Apr 01 2004 - 02:40:36 CST