<d1b2>
<kule_57901> Hi All, I am Kiran, and our team is currently developing a user interface for our data acquisition hardware. We have come across ngscopeclient by Thunderscope and are interested in learning more about the requirements for developing interfaces to interact with the scope client. I have been reviewing the source code for both the library and the scope client. Any resources or information that could help us understand and evaluate our needs
<d1b2>
to integrate with the scope client would be very beneficial. Thank you for your assistance.
<d1b2>
<azonenberg> So, you've actually got it backwards 🙂
<d1b2>
<azonenberg> We came first, the ThunderScope project was tinkering around with UIs and had some hacky thing that didnt work very well
<d1b2>
<azonenberg> I reached out to them and convinced them not to spend more time trying to make a DIY UI when our project already existed
<d1b2>
<azonenberg> So they're now our first instrument-vendor partner using ngscopeclient as their primary GUI
<d1b2>
<azonenberg> I'm the lead dev of libscopehal / ngscopeclient (although not personally working too closely on ThunderScope integration) and @aleksorsist is the main guy behind ThunderScope
<d1b2>
<azonenberg> As far as integration goes, our limited technical writing resources have mostly gone into writing end user facing, rather than developer facing, documentation so I freely admit dev docs have suffered (i.e. are mostly nonexistent other than comments in the source)
<d1b2>
<azonenberg> The tl;dr is that to make a new instrument driver you create a class derived from Oscilloscope, implement all of the virtual methods, and add an AddDriverClass() call to either the PluginInit() method of your plugin (if a plugin) or to DriverStaticInit() in libscopehal (if your driver is added to libscopehal itself)
<d1b2>
<azonenberg> @kule_57901 What sort of data acquisition hardware are you working with?
bvernoux has quit [Read error: Connection reset by peer]