Comments on: Opening up LabVIEW for Third-party Add-ons (like VI Tester)

By: Jeff

Jeff — Fri, 20 Feb 2009 01:51:08 +0000

Thanks Jim for the comments. JKI’s efforts in building add-ons to LabVIEW add tremendous value to the platform and we commend your efforts.

Ton – I am the guy at NI working on this. I’d love to hear your feedback and bring you into the conversation. Please shoot me an email: jeff.meisel (at) ni.com

By: Jim Kring

Jim Kring — Fri, 20 Feb 2009 01:21:47 +0000

Eli: Thanks for the nice note. I’m happy to hear that you’re hooked on VIPM. Make sure to add a VI Package Configuration to your project, so that you’ll always know which versions of the OpenG VIs you’re using

Ton: Thanks for the feedback. You’re right that there’s a lot more that can be done to open up LabVIEW to everyone. JKI is working very hard to help NI make this a reality. Programmatic builds of LabVIEW applications is another area that can definitely be improved. You can be sure that JKI will be advocating improvements in that area.

By: Ton

Ton — Thu, 19 Feb 2009 20:35:02 +0000

Ok, this is good news.

But how good?

Is the platform really open?, I mean can anyone connect their code to a toolbar?
What I would really, really love is a possibility to do programmatic builds.
LabVIEW 8.2 opened the new builder a little bit by exposing the build properties via some vi.lib VIs, unfortunately the loop is closed again in 8.6 where the info is stored in ABAPI classes with no API.

Ton

By: Elijah Kerry

Elijah Kerry — Thu, 19 Feb 2009 18:30:10 +0000

Happy to help Jim! Any tools that help our users benefits NI.

I regularly use OpenG VIs in LabVIEW applications I write for myself, which has me hooked on VIPM.