After thinking about this more. I had the idea that if limesuite had a server/client for the registers we could re-use the very fine grained gui to manipulate a lot of existing applications while they are running.
- So when a limesuite device is running, it can be started with a “server” option for the register access. This could be implemented on sockets, IPC, dbus messages, etc. But basically like a server on the localhost.
- Then we have a new limesuite device that inherits from iconnection and all that, except that it just proxies for the register access over the IPC, and otherwise does not implement streaming and things of that nature.
So from the limesuite gui perspective, this device shows up in the connection list once lets say, GRC has been run with driver=lime; and then you can connect to it and twiddle registers potentially. I know the GUI tends to re-initialize the LMS7 when opened and can even take down streaming, so there are some precautions to take. But we could run a lot further with the existing software this way, and get a lot more utility out of it.