JanK wrote:
> Will NI ensure it runs on Linux?
No. NI might make it run on Linux, but NI is not making any committment to do so. NI is committed to keeping the GDS working in future LV versions. Nothing beyond that is committed.
I am taking off my "NI LabVIEW R&D" hat at this point and putting on my "Aristos Queue, LabVIEW user" hat.
I wanted the toolkit to be available to more users so that they could benefit from its features. I convinced NI to purchase the rights to the toolkit and make it freely available. That acquisition does not come with dedicated developer resources going forward. It opens the door to several of us who have an interest in the toolkit making adjustments to it in our own time. I have already made several fixes to the toolkit when I built the new installer. It is my hope that this is a large enough block of existing code with a large enough community of users that it can be carried forward by community involvement.
There's a lot I still have to learn about the code base... for example, I know of no reason why it wouldn't run on Linux right now today. I've only heard that it doesn't. I haven't tried it. Perhaps it is something straightforward to fix. Perhaps not. Fixing it would certainly fit with my goal of making the tool available to the widest slice of the LabVIEW user base.
I do not know how this toolkit will develop going forward. I do not have the bandwidth to drive development of the toolkit, but I am going to serve as the pointman for changes. As fixes get posted here and vetted by the community members, I'll update the installer that is available for download from the LabVIEW Tools Network, and update it as new versions of LabVIEW are released. This is on the edge of my job description, but I've been promised enough timeslices that I should be able to do that. Development, on the other hand, is entirely on my own time if I choose to do it.
