FLDigi API Question for W1HKJ

[[e-mail] [linuxham]]

I've been working on a pet project using the FLDigi API for a couple of weeks, and have a question for W1HKJ. Does he happen to hang around on this list? I've built a nice library (a ruby gem, specifically) for using FLDigi as a modem, making it very easy to write ruby scripts to send and receive data (as well as control the radio). But there's one thing I desperately need (want?) that's not in the API - the ability to read the multiple data streams as received in the Signal Browser from the API.


If you're interested in seeing the library in it's current state, the gem is here:


https://rubygems.org/gems/fldigi https://rubygems.org/gems/fldigi



(or just type "sudo gem install fldigi" on Linux, Mac, or FreeBSD). If you'd like the full source, etc, it's hosted here:


https://github.com/jfrancis42/fldigi-ruby https://github.com/jfrancis42/fldigi-ruby



It's not 100% ready for prime time, so I wouldn't rely too much on it yet. It's pretty stable and it works very nicely, but at this point, I can't promise that my API (heh, an API for the API) won't change. I'm still finding better ways to do things, which often require breaking the old way. But it works well enough to do some really useful things with, and it abstracts the FLDigi API into something much easier to use from ruby.


It might work on Windows (or it might not). I don't own or have access to a Windows machine, so it's untested there. It will almost certainly control FLDigi running on Windows, but I don't know if my library itself will run there or not. I do my development on Mac and Linux. I don't do anything deliberately to exclude use with Windows, but I also don't know what I don't know about compatibility.


FWIW, I'm open to suggestions as to additions and/or changes to the library. I'm writing it for my own project, but I'm writing it with the intent that it's useful as a general-purpose tool to do lots and lots of things. For example, I wrote a PropNet client with it, and it would be trivial to write an HF APRS client (which I started, then got sidetracked).


Jeff
N0GQ

[Geoff NW7GM [e-mail] [linuxham]]

Yes, Jeff, Dave does visit the group quite often. He also responds to
direct emails fairly quickly as well.

Post by jeff-CDdbmnNP9qodnm+***@public.gmane.org [linuxham]
I've been working on a pet project using the FLDigi API for a couple of
weeks, and have a question for W1HKJ. Does he happen to hang around on
this list? I've built a nice library (a ruby gem, specifically) for using
FLDigi as a modem, making it very easy to write ruby scripts to send and
receive data (as well as control the radio). But there's one thing I
desperately need (want?) that's not in the API - the ability to read the
multiple data streams as received in the Signal Browser from the API.
https://rubygems.org/gems/fldigi
(or just type "sudo gem install fldigi" on Linux, Mac, or FreeBSD). If
*https://github.com/jfrancis42/fldigi-ruby
<https://github.com/jfrancis42/fldigi-ruby>*
It's not 100% ready for prime time, so I wouldn't rely too much on it yet.
It's pretty stable and it works very nicely, but at this point, I can't
promise that my API (heh, an API for the API) won't change. I'm still
finding better ways to do things, which often require breaking the old way.
But it works well enough to do some really useful things with, and it
abstracts the FLDigi API into something much easier to use from ruby.
It might work on Windows (or it might not). I don't own or have access to
a Windows machine, so it's untested there. It will almost certainly
control FLDigi running on Windows, but I don't know if my library itself
will run there or not. I do my development on Mac and Linux. I don't do
anything deliberately to exclude use with Windows, but I also don't know
what I don't know about compatibility.
FWIW, I'm open to suggestions as to additions and/or changes to the
library. I'm writing it for my own project, but I'm writing it with the
intent that it's useful as a general-purpose tool to do lots and lots of
things. For example, I wrote a PropNet client with it, and it would be
trivial to write an HF APRS client (which I started, then got sidetracked).
Jeff
N0GQ

[Remi Chateauneu [e-mail] [linuxham]]

Hi,

You might have a look at the function viewaddchr in the file Viewer.cpp,
or the method pskBrowser::addchr in the file psk_browser.cxx . As far as
I can tell, they are called by psk and rtty to display a new char.

It might be possible to make it write to a queue which would be
asynchronously read by a new API function.

Hope it helps.

Remi

Post by Geoff NW7GM geoff.nw7gm-***@public.gmane.org [linuxham]
Yes, Jeff, Dave does visit the group quite often. He also responds to
direct emails fairly quickly as well.
I've been working on a pet project using the FLDigi API for a
couple of weeks, and have a question for W1HKJ. Does he happen to
hang around on this list? I've built a nice library (a ruby gem,
specifically) for using FLDigi as a modem, making it very easy to
write ruby scripts to send and receive data (as well as control
the radio). But there's one thing I desperately need (want?)
that's not in the API - the ability to read the multiple data
streams as received in the Signal Browser from the API.
https://rubygems.org/gems/fldigi
(or just type "sudo gem install fldigi" on Linux, Mac, or
_https://github.com/jfrancis42/fldigi-ruby_
It's not 100% ready for prime time, so I wouldn't rely too much on
it yet. It's pretty stable and it works very nicely, but at this
point, I can't promise that my API (heh, an API for the API) won't
change. I'm still finding better ways to do things, which often
require breaking the old way. But it works well enough to do some
really useful things with, and it abstracts the FLDigi API into
something much easier to use from ruby.
It might work on Windows (or it might not). I don't own or have
access to a Windows machine, so it's untested there. It will
almost certainly control FLDigi running on Windows, but I don't
know if my library itself will run there or not. I do my
development on Mac and Linux. I don't do anything deliberately to
exclude use with Windows, but I also don't know what I don't know
about compatibility.
FWIW, I'm open to suggestions as to additions and/or changes to
the library. I'm writing it for my own project, but I'm writing
it with the intent that it's useful as a general-purpose tool to
do lots and lots of things. For example, I wrote a PropNet client
with it, and it would be trivial to write an HF APRS client (which
I started, then got sidetracked).
Jeff
N0GQ
--
Geoff, NW7GM
Seattle, WA
CN87tr