Re: Old timey data entry GUI problem

2012-07-23 Thread Björnke von Gierke
Thanks everyone for their hints, much appreciated. Note that the SQLite server architecture exists and works, and I'm not going to change to any other db right now :) Also no big screen, printouts or anything like that, because we want people to mingle (and consume). -- Use an alternative Di

Re: Old timey data entry GUI problem

2012-07-22 Thread Dr. Hawkins
On Sunday, July 22, 2012, Peter Haworth wrote: > Yes, SQLite doesn't work well, if at all, over a network connection mainly > due to the flakiness of file locking over a network. Sounds like you found > a way round that but there are a couple of client/server third party addons > for SQLite. Nev

Re: Old timey data entry GUI problem

2012-07-22 Thread Peter W A Wood
Björnke On 23 Jul 2012, at 01:47, Björnke von Gierke wrote: > As for proof checking as a second persons job, we'd need two or three people > for every one person entering stuff. Printouts would be too slow, but because > there's a networked database solution existing already, proof reading coul

Re: Old timey data entry GUI problem

2012-07-22 Thread Ken Corey
On 22/07/2012 18:47, Björnke von Gierke wrote: As for proof checking as a second persons job, we'd need two or three people for every one person entering stuff. Printouts would be too slow, but because there's a networked database solution existing already, proof reading could be done on anoth

Re: Old timey data entry GUI problem

2012-07-22 Thread Peter Haworth
Yes, SQLite doesn't work well, if at all, over a network connection mainly due to the flakiness of file locking over a network. Sounds like you found a way round that but there are a couple of client/server third party addons for SQLite. Never tried them but Google sqlite server for info. Unfort

Re: Old timey data entry GUI problem

2012-07-22 Thread Mike Bonner
Makes sense. Which brings you back to the main thing, if you can find someone already trained to use a 10 key (a volunteer accountant? *grin* ) their accuracy should be very high. Worst case have guidlines to help people get in a rhythm. As you say, 'smart' people tend to do their own thing becaus

Re: Old timey data entry GUI problem

2012-07-22 Thread Björnke von Gierke
I really like your idea of using the numpad + to switch between fields. That frees the other hand for handling the paperwork. A great speedup! To avoid lag slowing down entry, I can do all checking and db-to-entry comparisions asynchronous. They're done via sockets anyway. As for proof checking

Re: Old timey data entry GUI problem

2012-07-22 Thread Björnke von Gierke
Thanks for your thoughts, some interesting stuff. The game that is played is "Jassen" the (almost) official Swiss national card game: http://en.wikipedia.org/wiki/Jass You asked why I need those exact four numbers. Yes, all 4 numbers need to be entered: - I need to know the ID of the persons w

Re: Old timey data entry GUI problem

2012-07-22 Thread Mike Bonner
I have a couple thoughts on this. First, thinking of the people doing the data entry as "typists" may not be the best viewpoint. You should look for people skilled at 10 key operation and gear the application towards 10 key methods. Approximately 800 numbers total every 30 minutes should be easil

Re: Old timey data entry GUI problem

2012-07-22 Thread Ken Corey
I'm not sure what kind of tourney you've got there, but why in heaven's name do all 4 numbers have to be entered each time? Surely the id is known before-hand...and likely the table and partner number too, otherwise how is this event scheduled? All of this should be entered before the event h

Old timey data entry GUI problem

2012-07-22 Thread Björnke von Gierke
Hi everyone Sorry for the wall of text, here's a short version: I am developing a software for a charity tourney. I need typists to enter 4 numbers about 200 times within 30 minutes (or so). See screenshot of what I got right now: http://i.imgur.com/G7Fgg.png I have no experience with such a