[Hamlib-developer] branch_ts2k

[Dale E. E. <de...@w-...>]

Stephane,

1) If you have some time in the near future could you check-out and
look at  branch_ts2k?  Especially the include/hamlib/rig.h and how
I added #define's with hooks into rig_newvfo.h.  This would allow
minimal changes to rig.h and prevents the ts2k stuff from interfering.

2) Also, I'm working on a command-line.  You can glance at it and see
if you think its going the right direction.  I'd eventually like to have
it
be called during startup to process .hamlibrc or some such.  It should
also be callable by user routines.  I haven't tried the 'pure-parser'
for re-entrant routines yet.  Also, the flex scanner is set as 'always-
interactive' for use as a command-line parser.  This conflicts with
its use as start-up command processor.  The files live in tests/rc.

I don't know if you can use scanner.l (flex) for rigctl.  If you look at

the code (very bleeding edge, with lots of sharp edges!) you can tell
me things that you'll need or would like to have.  I'll be working on
it as soon as I get my ts2k.c re-write finished.

3)  Last but not least, I've written ts2k_cmds.[ch] which implement
all of the commands available for the TS-2000 except the 'ex;'
command for setting menu options.  These are very nice to use
so that you only worry about parameters (p1, p2,...) and not about
the exact implementation and quirks.  When a bug is fixed it fixes
all code and saves alot of duplication.   I presume others backends
can use them.  The only thing they know about hamlib is:
    a) ts2k_transaction() which can easily be replaced.
    b) RIG * required for the ts2k_transaction.
They simply read/write rig commands and place them in a
parameter struct.  Any ideas or comments will be welcome.

73's
Dale, KD7ENI