[Hamlib-developer] Re: hamlib-1.1.0

[Stephane F. <f4...@fr...>]

Matthew Francey wrote:
> a) Networked from day 1.  The "backend" and "frontend" stuff should
> communicate over a cleanly designed, extensible, protocol that runs on
> top of TCP/IP or some other connection mechanism.
> 
  nice, a little bit heavy to my taste. We can achieve the same result
  for half the price. That's what the RIG_PORT_NETWORK is for,
  and there's already some rig protocols around, waiting for someone
  to write a backend for..

> b) Event driven.  This is particularly important, as many radios
> (e.g., PCR-1000) issue events based on what is happening (signal
> strength, etc) on the channel.  Polling is Bad.
> 
	Hamlib has basic event support, and it works, at least with
  my Icom. Even though polling is bad, it IS needed sometimes.
  For example, Icoms CI-V does not notify of VFO changes.
  Work planned.

> c) Capabilities are essential.  Without being able to discover what a
> radio is capable of, you'll end up with a framework that won't be
> too exciting to people 10 years from now.
> 
	We'll be happy if Hamlib is still applicable in 10 years.
  At that moment, perhaps this will be the time for a new generation.
  In the meatime, capabilities are there from the day one, and we
  try to make the API the more generic it can be. But we are lacking
  developers/designers, and I'm sure your input would be very valuable.
  We learned a lot by experimenting (isn't it the OM approach after all?),
  esp. by trying to implement funky rigs, receivers, etc.

> d) Rethink what is being controlled.  A "radio" can actually consist
> of several independent channels.  

  Yup, this is true. The problem we're facing right now is we don't know of
  every breed of rigs out there, and Hamlib may want to control them
  in the future. Hence how one can forsee how much generic the interface
  should be, yet retaining good efficiency ?
  If you have some patchs to control coffee machines, they're welcome :)
  Well, it seems you have thought already a lot about this, so I hope
  you'll join us on the list!

Cheers,
-- 
Stephane