[MacLoggerContest] Contest entry screen specification

[B. Scott Andersen]

Colleagues,

I would like to reiterate Don's request that these discussions appear  
on the
Contesting list ONLY so that we do not cross-post to uninterested  
groups.
That's the Netiquette way!

Below is the very specific suggestions that I gave Don for the contest  
data entry screen.
The data entry screen is a little more "busy" than some contest-only  
logging programs
might demand, but the extra information (name, QTH info, etc.) are  
helpful when logging
even in a contest (or so I find). Certainly the mapping of the call  
sign to country is very
helpful in DX contests and I contend mapping call sign to state is  
helpful for US contests.
The other information presented (name, street, city) is not  
distracting, IMHO, and
because this screen might be used for DXpeditions--and sometimes  
you'll be working
somebody who sounds familiar, but in the heat of the pile-up you  
didn't recognize the
call--the full information popping up is actually very helpful! I  
confess there were several
pile-ups while I was on Montserrat where a friend from the local club  
called, I typed in
the (very familiar) call sign, but did not recognize him until I did  
the lookup. So, while
it might not be key for contesting, I contend that this panel could be  
used for quick entry
for DXing, too, and it is very helpful to have the QTH information  
present.

The above handles the left-side of the box.

Now to the right side. The following is an exact copy of the message I  
sent to Don along
with the details of the specification, rationale, and some additional  
thoughts that I had,
but ultimately dropped. Don has asked the contesting community for a  
specification of
what might be helpful for contesters--and I responded with a  
lightweight software
specification with rationale. The fact that the new contesting data  
entry screen looks very
much like the one I designed and specified is a testament to Don's  
willingness to listen
and accept solid, specific, unambiguous, and detailed suggestions. For  
that, I gladly
give him my thanks!

The design I sent Don follows. Questions about why I asked Don for these
specific things are best sent to me, probably. After all, Don just did  
what we (I)
asked. {grin}

Here's the thing I sent Don:





Don,

Here's my idea. If we are confined to just one panel then this is a  
good start IMHO.

1. Tabs move between the following fields:
	Call --> Recv text --> Recv S/N --> Sent text --> Sent S/N --> RSTR -- 
 > RSTS

2. CMD-K (clear) clears call, Recv text, and Recv S/N. Focus is left  
in Call.

3. Lookup doesn't change anything in the data entry fields

4. Logging clears like CMD-K. Again, focus is left in the Call to  
begin again.

5. If enabled, serial number increment for Sent S/N happens when Logging
as with the current software.

6. The clock (lower right) should increment in real time, not just  
when the lookup
is preformed. Near the beginning and end of the contest it is  
important to know
the time and log it closely to prevent accusations of "rubber clocking".

7. Power could be set elsewhere (preferences panel?) or set here. In  
some ways,
having it set elsewhere might be preferable -- just reminding the  
operator of the
category they are playing in.

-=-=-

So: here's how a QSO would go.

CMD-K clears Call, Recv text, and Recv S/N. Focus left in Call
The clock continues to tick while I call CQ
Somebody answers my CQ. I type in the call.
I hit CMD-L to lookup. All that great data gets filled in.
Tab. I copy his exchange data into the Recv text area. OR!
Tab Tab. I copy his exchange serial number into the Recv S/N area.
Shift-CMD-L to log it.  This clears call, Recv text, and Recv S/N.  
Focus is left in Call.
I'm ready to go again.

I toyed with the idea of making the focus change from Call to Recv S/N
selectable with a checkbox option--and it still might be a good idea-- 
but
this gets us close.

Frequency/band/mode information is up top so you know where you're  
playing.
The clock, important but not critical until the end of the contest, is  
still in an obvious
place but well away from the main area of activity.

The ITC and CQ Zone information appears directly below the call so  
they can be
seen in a single glance after lookup and BEFORE exchange capture. This  
is handy
for any contest like CQ WW.

Users can repeatedly log QSOs without touching the mouse--just keyboard,
keyboard, keyboard. That's good. If your hand needs to leave the  
keyboard
during a contest is should be going for the radio, not the mouse.

The data handling (using the ADIF STX, SRX, STXn, and SRXn fields) is
unchanged from the current incarnation of MLDX. There is little  
incentive,
therefore, to alter the current Cab-converter approach of consuming an
exported ADIF file. So, my world will remain the same.

That is my thinking on the design. Your thoughts?

-- Scott (NE1RD)

B. Scott Andersen           | "Magic is real, unless declared integer."
bsandersen -atsign- mac.com | -- The collected sayings of Wiz Zumwalt
Acton, MA (NE1RD)           | http://www.bsandersen.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/9fea5abf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: contest-layout-bsa.png
Type: image/png
Size: 64720 bytes
Desc: not available
Url : <http://seven.pairlist.net/pipermail/macloggercontest/attachments/20090124/9fea5abf/attachment-0001.png>