Leaderboard

So it looks like I won't be able to continue my LabVIEW development in the near future (or at least have a major break) *sadface* Is anyone interested in continuing development of the project? It is now at the point where all dependencies to web services have been removed and replaced with web sockets. That means the page for the front panel can be viewed via file:// protocol and doesn't require a http:// any more. Web socket connection is established to a configurable port. It can handle multiple clients (how ever stupid that may be to give control over a single system to multiple users; makes sense if they're all indicators). It supports a bunch of common controls that can be represented as HTML5 and it supports representing any control as an image. I've implemented a basic config editor that can be used to select if a control should be represented as HTML or image. Current version is attached. FPPublisher.zip

It's almost 2016. Can I serialize LabVIEW objects to a standard interchange format yet?

Is this no longer on Bitbucket? Where is the repository now?

Here is a Beta version with a new “Treatment of Infinity/NaN†terminal on the JSON write functions. Three options: -- Default JSON: write all as nulls. -- Extended: use JSON strings for Infinities ("Infinity", "-Infinity"); NaN still null. -- LabVIEW extentions (compatable with the LabVIEW JSON primatives): Infinity, -Infinity, NaN (not in quotes) Note that the LabVIEW extentions are not valid JSON. The Extended option IS valid JSON, but not all JSON parsers will process strings as numeric values. lava_lib_json_api-1.4.0.28.vip

The ViewPoint systems one works fine and is newer, not that this means it is better. But honestly I think using a toolkit is optional. I've generally just always used the tortoise SVN which add right click menus in Windows Explorer. I also work in the Lock, Edit, Commit scheme, instead of the Edit, Merge. What this means is files are read-only until you get a lock. Once you get the lock the VI is now not read-only. You make the changes you want, and then commit them which by default will unlock it, setting the file back to read-only, allowing someone else to update and lock. So if I'm working on a VI and I don't have the lock I will hit save, and LabVIEW will prompt saying it can't save it is read-only and the explorer window will be opened asking me where to save it. I will in this window right click my file and get the lock. I'll then cancel that window and save again, and this time it will save because I have the lock and it isn't read only. I can do all the SVN operations I want from the explorer window, and don't need to invoke another tool like Viewpoint. The only exception is for things like invoking compare, and rename, which generally needs to rename both in SVN and in an open project. Note that if you have LabVIEW 32 bit on a Windows 64 bit, you'll want to install this additional installer to give the right click menus in 32 bit applications after installing the 64 bit tortoise client. This is mentioned on the download page of tortoise SVN.

OK are those really 2 different pictures? Or did they just photoshopped the shirt?