Re: [Hamlib-developer] Re: [Groundstation-developer] Gnome RIG 0.2

[Alexandru C. <al...@ph...>]

Hi Joop and Stephane,


> > > know anything about hamlib. Eventually, this widget will become a bonobo control
> > > making it embedable in any Gnome program that can use bonobo controls (Gnumeric,
> > > Abiword, etc. - yes, you will be able to control your RIGs from your spreadsheet
> > > file :-).
> > 
> > Weird stuff....
> 
> You'll see, one day you'll be able to rotate your 32x moon melter array from emacs!
> 

I think you can already do that but you might need some Emacs/Lisp
bindings for Hamlib ;-)


> > I got word from terry, the hamlib maintainer for debian, that he is working on
> > hamlib-1.1.3. I'd really like to test grig, but gnome is quite a mess at the
> > moment in debian/unstable. I would like to wait until the migration to
> > gnome2 is finished.
> 
> hey, that's great news (well, not for gnome :(
> 

I have tried to compile grig on Debian 3.0r0 which comes with Gnome 1.4,
but I have no experience with Debian/unstable.


> > Now that we have a nice program for displaying and controlling the rig's
> > frequency and other things, have you ever thought about possible information
> > exchange between different programs? I am using xlog for logging and when
> > I do, I can't use grig (and vice-versa). It would be nice if there was some
> > kind of way for either of these programs to work together. We could think of
> > message queues or shared memory. This way I can run xlog, have grig displaying
> > the frequency and still use hamlib for my logging information with xlog...
> 
> And the answer already exists. Alex would tell you to use his Bonobo
> control, but there is simpler for simple application: the RPC backend.
> Just run rpc.rigd on the localhost, tell xlog and grig to use MODEL_RPC,
> they will share the rig. And voila!
> 
> This way, no need to put hacks in all the applications around to make them
> live together.
> 
> What do you think?
> 

I probably would have agreed on some shared memory or FIFO, but I think
Stephane is right. If the RPC backend can handle multiple clients, there
is no need to redo that or something similar in the client applications.
Question: Can you have more than one rpc.rigd's running on the same host
but controlling different rigs? If not, can it be done?


Alex