[hpsdr] HPSDR software direction

[Bob Cowdery]

 On 06/08/2010 08:20, Phil Harman wrote:
> There needs to be a set of rules for defining an interface.

I am in total agreement with a lot of what is being said about defining
interfaces, having the system understand the capabilities of its
hardware and software components and act accordingly. Unfortunately
unless the hardware itself has a built in interface to describe its
capabilities they have to be configured in the software, but it's
configuration and not code.

I did start out on a system a while back, but it's been mothballed for
over a year due mainly to lack of time but also lack of interest and my
total inability to resist the temptation to change tack on a regular
basis! It is reasonably well documented at http://www.g3ukb.co.uk and
may provide some ideas. I'm not putting it forward as anything but food
for thought as it's way behind the current leading edge stuff.

I am also quite sure that there is enough high quality code around to
package behind interfaces to make some staggeringly good components
without major effort.

Bob
G3UKB

 1281081769.0