(Confessions of an NI LabVIEW Guy)
I, like many of you, are taking some time at the end of the year to reflect on the successes of 2008 as well as the gaps that still exist. In thinking about next year’s goals, I thought it might be fun to share some of these with the LabVIEW community at large to get your feedback or commentary about. Most of these address areas where I believe we have some shortcomings today, hence my “confessions” sub-title.
For now, I will simply list my resolutions. I will use a series of subsequent posts to explain in more detail each of these and what I hope to accomplish in 2009.
- Get NI more active in the user community
- Provide better support for third-party tools
- Be more transparent with our roadmaps
- Clearly document our “support” and product lifecycle policies
- Get serious about addressing upgrading and deployment pain
- (an extra bonus) Develop new, more effective ways to capture user input and feature requests (and act on it!)
I will follow up with more details about what each of these means in the near future. For now, have a great holiday season.
Inside LabVIEW 
Well, that’s certainly an ambitious and useful list. Here’s hoping all of it gets advanced.
Enjoy your vacation.
Dear John,
we wanted to use LabView for control and visualisation of chemistry machines.
What we would need:
a possibility for the customer to generate and modyfy flexible the visualisation of his machine
much more and an other kind (“intelligent” not only picture) of symbols for valles, pumps, sensors, …
the symbols need the possibility to be switched from the costomer and to show the status of the machine, if an application sequence is running. -“interactive” access to a running application
——————————-
It’s still my opinion that Law View is not user friedliy. After weeks of use, I still need to much time to search for functions, …
The C interface could be much more efficient, if string access would be possible in the small C window. It’s not good to write and access dll’s for such easy things.