5 ms·
As someone who has fallen into the unfortunate position of being the local LabView expert, there's a little tricky you might want to know. Pretty much all of t
by rprospero 13y ago
As someone who has fallen into the unfortunate position of being the local LabView expert, there's a little tricky you might want to know. Pretty much all of the awesome hardware support is contained in the daqmx library. The C api for this library can be connected to through nicaiu.dll (or the corresponding dynamic library format for your OS). By linking in here, you get all the wonderful hardware support while being able to write code in your favorite language with your favorite editor and commit it to your favorite source control.
I've been slowly translating all of our LabView code out of G and it's both made my life vastly simpler and has also allowed other coders to work on it without learning G.
- bnejad 13y agoGood tip! I was aware there were some options along this line but unfortunately using LV(more specifically, "G") was a project requirement. You briefly touch on another point that is worth repeating. Source control with LV is terrible.
- meemoo 13y agoSource control is fine in NoFlo's JSON graph format or DSL.
- RogerL 13y agoSo, are you saying when I diff I am looking at textual representations of the graphs? Which is fine, that is what I'd expect. It's how I'd implement it. But isn't that a huge clue about the fundamental weakness of graphical representation - as soon as you try to do anything nontrivial it's back to text. And back to text for a very good reason, not because the right git plugin hasn't been written yet.
- seanmcdirmid 13y agoOne could write a real 2D graph diffing system, it is not inconceivable, at least. However, you won't get this for free by diffing a textual representation of the graph. One simple hack is to take each version, set transparency to 50%, and then overlay them.