During this morning’s NI-Week keynote we previewed a new LabVIEW tool to create thin client UIs. By preview, it isn’t avaialble for you to use today. If you make use of web services to share data from LabVIEW applications on Windows or Real-Time (RT) targets (PXI or cRIO) you will be able to make use of the Web LabVIEW UI Builder to create zero install thin client UIs to monitor and update the data with web services. The editor will be accessible through a browser and doesn’t require you to install something on your machine, well except for the Siliverlight plug-in. The editor and your final application are Silverlight applications.
The image below shows you the UI created using the Web LabVIEW UI Builder that was shown today during the keynote as well as editor hosted in a browser.
The Web LabVIEW UI Builder has the LabVIEW graphical programming paradigm but there are some differences with how you use LabVIEW today. These exist to provide true thin client editing and execution and of course to also for us to try some new things out in a supporting tool without changing your daily existing experience with LabVIEW. I’ll write more on these in blog posts after NI-Week and ask you to chime in on your impressions.
The best way to really get involved in the feedback process is apply for the Web LabVIEW UI Builder pioneer program. If you’re interested please let us know since we’re actively selecting people to join the pioneer program. As part of the pioneer program you’ll get early access to the software when it’s ready and interact with the product manager, program manager and engineers to help shape the product’s features.

August 22, 2009 at 11:55 am |
[...] During NI-Week I posted about two of the projects I’ve involved with, the Web LabVIEW UI Builder and the LabVIEW System Designer. The video’s of both of the preview demo’s were posted [...]
September 1, 2009 at 10:06 am |
ARRGL, what did I just read “The editor and your final application are Silverlight applications.” So the Web LabVIEW UI Builded app requires a plugin and therefore is a LOT less a Thin Client. Moreover this will refrain the app usage to mainly desktops a bounded to Silverlight supported machine. Then you have to redo the IT dance stuff which is a no go in many institutions.
Why why why the builded app is a Silverlight app, it should be a plain Web2 (Ajax, JS, Rest, XML, etc.) app without plug-in.
I do not mind to have the editor as a Silverlight app (I could just use LV instead) but the builded app should definitely move from Silverlight to standard web2 technologies.