[Ham-Mac] Re: 1st draft at consensus of top 5 MLC feature list priorities

[eugene kraft]

Hi,

I fully support Jonathan's comments on the five top features and I am 
also particularly keen to have CW memory keying incorporated.  I look 
forward to hearing more on how this is proceeding.

73,

Eugene G4FTP

On Wednesday, March 16, 2005, at 06:54  pm, Jonathan G0DVJ wrote:

>
> Hi all,
> (Recipients already on the MLC list have already seen a version of 
> this mail so can disregard it second time!!)
>
> A while back, after I initially posted a mail to this list "dreaming" 
> about an OSX native application for contest logging, and some initial 
> debate here on this list, Don Agro set up a specific list to discuss 
> the detail more deeply, and to take it off this general list.  At that 
> time, I promised to report back here when the initial stage was 
> complete ... hence this mail.
>
>
> We have had some good debates over the last couple of months - about a 
> lot of detail and some philosophy regarding a potential 
> MacLoggerContest (MLC) program which would in Don's words aim to be 
> "an insanely great contest logger"!    We have also had time to 
> deliberate and think through what we believe is important and 
> realistic.   The aim has been to draw a number of opinions together to 
> try and achieve some consensus.  Just to remind you why getting a 
> consensus was important ... a quote from a direct email (with 
> permission) from Don ...
>
> On Feb 2, 2005, at 3:28 pm, Don Agro wrote:
>> I would really appreciate seeing your original email posted back to 
>> the Ham-Mac list re-written in order of priority - If 20 people on 
>> the Ham-Mac list can agree on the top 5 priorities I will jump into 
>> the fray with MacLoggerContest. The reason I am asking for that level 
>> of detail is not just to get a consensus amongst the enthusiasts, but 
>> to make sure I get a firm grip on what it would take to make an 
>> insanely  great contesting program.
>
> We are not rushing into this - it takes time to gain consensus;  it 
> means we all have to evaluate what we can live with as opposed to what 
> we can't, and I think we have to take the size of the task into 
> account and look at this as a starter top 5 rather than an end-game.
>
> Having looked at the original feature list from my mail that 
> originally set this discussion off, and trying to take into account 
> the discussions that have been had since then on the MLC list, I offer 
> a draft top 5 features/characteristics of a possible initial MLC.  
> Please note I am not trying to rank these 5 at this stage - this is 
> not required - rather we are prioritising these things against the 
> other features that are derived from the original list.   I have 
> re-worded some of the points where the discussions we have had 
> clarified different items from the original list.
>
> You will see I have tried to categorise the top 5 by 4 essential areas 
> of discussion too as I have read them.   I have allowed ourselves one 
> initial "bell & whistle" feature at this stage.   Each of these 
> contains a certain amount of detail based on the discussions we have 
> had.   I felt I had to bulk some related items together given that 
> there are just a certain number (>5) features that all contest loggers 
> need!   The remainder of the items from the original list I posted are 
> listed again in no order of importance for reference afterwards.   I 
> hope I have managed to achieve a very difficult task at least to some 
> extent.
>
>
> ***   Please consider this initial attempt at a consensus and if you 
> can give it some support at this early stage, please either post a 
> simple note to that effect to this list or direct to Don or via myself 
> if you prefer.   ***
>
> (I have copied this to Don explicitly for those that want to reply 
> direct and can't recall his address)
>
>
> As we continue discussions on the MLC list, I will occasionally report 
> back here for those not ardently following or subscribed to the other 
> list.
>
> Thanks & 73,
> Jonathan G0DVJ
> --
>
>
> Top 5 :  (in categories but NO order of importance)  - 1st draft:
> ---------
>
> SETUP:
> - Easy but flexible configurable set-up for any contest requirements 
> no matter what the exchange required and the scoring schemes defined.  
>  Full support for all popular national and international contests in 
> the calendar (or the ability for users to set up such flexibility), 
> HF, VHF and UHF contests all supported.
>
> ENTRY/EDITING OF QSOs:
> - Fast entry of required contest logging fields through a 
> "bullet-proof" data entry routine.  Auto insertion of relevant data 
> from radio connection (such as Band/Mode) but also enabling other 
> radio communication features as and when.  Auto suggested data 
> insertion (zones, area codes, reports, locators etc. as appropriate).  
> Entry includes the important aspect of editing a QSO easily and 
> quickly.
>
> CHECKING & INFO FOR OPERATORS:
> - Real-time checking (preferably as callsign characters are typed 
> without touching other keys/buttons) of DUPLICATES, but also 
> country/band/locator/other multiplier analysis, beam headings, 
> potential multiplier status ) plus re-scoring in real-time & 
> continuous summary of scoring per band/mode/multipliers/etc.
>
> INTERFACES & STANDARDS:
> - Use of all existing "standard" file formats used by other similar 
> software such as:
> 	-  Partial matches to the standard callsign contest databases 
> produced by K5ZD,
> 	-  Use of standard CTY country prefix files
> 	-  optional Cabrillo log entry file generation
> 	-  ADIF generation for integration with MacLoggerDX and other loggers 
> for your main station log
>
> INITIAL BELL & WHISTLE:
> - A contest CW memory keyer
>
>
> Other outside top 5:  (not in any order).
> --------------------------
>
> - A facility to connect to a public/private DX cluster (either on the 
> net or via RF/TNC) which highlights spots which are potential 
> multipliers.
>
> - SO2R support for 2 radio operation
>
> - Inbuilt contest voice "keyer" for CQ parrot calling.
>
> - Multi-operator support for logging and statistical analysis of rates 
> and mults etc.
>
> - Rendezvous support for Multi-multi operation over ethernet or 
> airport networks.
>
> -  Integration with Apple's iChat for IM chat between operators in 
> multi-multi situations, spotting stations etc.