Jim Kring

QUOTE(Kalmar @ Apr 22 2006, 11:01 AM) Kalmar, It's two years later, but better late than never, I guess Here is a new http://jkisoft.com/easyxml/' target="_blank">labview xml toolkit that makes using xml data in LabVIEW easier than ever before. Thanks, -Jim

QUOTE(Vincent Wong @ Mar 6 2008, 10:58 AM) Hi Vincent, Nice job. This is a great example, and I like the liberal use of the OpenG VIs. In fact, this example reminds of early prototype versions of EasyXML Our proof of concept took only about an afternoon to create. Then, as we started to add support for attributes and test for things like nested entities with similar names, variable whitespace, xml comments, etc. we started noticing that there were lots of bugs and the fixes were not nearly as straight-forward as you might think. In the end, there was a considerable amount of time getting EasyXML to the point where we felt comfortable with releasing it. That's one of the main differences between commercial-grade software and proof of concept code. At JKI, we have an entire suite of unit tests (almost 100 individual tests for EasyXML) that we use to validate that the code meets the specification -- I'll talk about that in a future blog article. And, we're committed to fixing issues that are reported and to continue to improve the product's features over time. Please don't take my comments as a knock against your code, which is very nice. My point is to raise awareness for the fact that if you decide to go down the road you're headed (or if users try to adopt this as a solution for thier XML parsing needs), I believe that you'll soon realize that there is a lot of work in-store. Keep up the great work. This is a wonderful example and raises awareness for OpenG and using XML in LabVIEW Thanks, -Jim

Hi Phil, Here's a simple example (in LabVIEW 8.5): Download File:post-17-1204827742.vi Which versions of LabPython, LabVIEW, and Python are you using? Thanks, -Jim PS - The link here doesn't have anything to do with LabPython -- that example uses TCP-IP to communicate with Python, whereas LabPython uses a DLL to communicate with Python.

QUOTE(bjzimmer @ Mar 3 2008, 08:25 PM) Hi Ben, Congratulations on the launch of your blog and thanks for contributing this content. I'm looking forward to seeing some of your videos. One thing: I'd recommend adding an RSS feed -- that will make it easy for people to receive notifications of new content. Personally, I prefer RSS to email-based subscriptions. Cheers, -Jim o

If you use OpenG VIs, please take this poll and let me know how you feel about the palette integration. I'm considering restoring the dynamic palette capabilities and want your thoughts on the matter. http://forums.openg.org/index.php?&showtopic=800 Thanks,

QUOTE(jlokanis @ Mar 3 2008, 10:34 AM) CRUD is more flexible than a WORM A Create, Read, Update, and Delete interface.

QUOTE(Karl Rony @ Mar 2 2008, 02:58 PM) Hi Karl, Thank you for the kind words and endorsement of our efforts. We look forward to having you as a customer and strive to deliver on your expectations Thanks, -Jim

QUOTE(crelf @ Feb 17 2008, 05:34 AM) I've just announced a new article on my blog with my ideas. I hope it meets your expectations after keeping you in suspense all this time Cheers,

JKI is proud to announce the release of a new, low-cost, cross-platform XML toolkit for LabVIEW, the EasyXML Toolkit for LabVIEW, which promises to make it easy to use XML data in LabVIEW. This cross-platform toolkit is delivered as a package that can be installed using VI Package Manager on LabVIEW 7.1 or greater. JKI unveils the EasyXML Toolkit for LabVIEW, a low-cost, cross-platform XML toolkit that's easy to use

Ton, Thanks for your great many contributions to the LabVIEW Community, and especially here on LAVA. Cheers, -Jim

QUOTE(crelf @ Feb 18 2008, 01:43 PM) Glad to add some happiness to your Monday

The OpenG Dynamic Palette package allows the OpenG libraries to be seen in the LabVIEW palettes. This release (v0.17) adds support for LabVIEW 8.6. You can download+install this package using VI Package Manager. Just press the "Check the Network for Available Packages" button to refresh your package list.

QUOTE(tcplomp @ Feb 14 2008, 12:08 PM) Here is how to install the LabVIEW 8.0 run-time engine on Ubuntu. I hope it works for you. 1) Install alien using the Synaptic Package Manager (System>>Administration>>Synaptic Package Manager) and make sure that it automatically installs the various other dependencies, such as rpm. 2) Install the LabVIEW runtime engine files: sudo alien -ic labview80-rte-8.0.1-1.i386.rpm labview-rte-aal-1.1-1.i386.rpm 3) Install libosmesa6 using the Synaptic Package Manager. 4) Create a symbolic link so that the LabVIEW runtime can find libOSMesa.so.4 sudo ln -s /usr/lib/libOSMesa.so.6 /usr/lib/libOSMesa.so.4 That's all there is to it. After completing these steps, you should be able to run the VIPM 1.0 installer. Notes: You should install LabVIEW and the runtime engines in the order they were released (e.g., 8.0 before 8.2). I have had bad results trying to install the LabVIEW 8.0 runtime engine after the 8.2 runtime engine. The problem is probably fixable, but is beyond me.

By the way, you can get a list of the object names and IDs used in the palettes inside the objectnames.js file that's inside the LabVIEW help (chm) file. Type this into the address bar of Internet Explorer to extract the javascript file (IE will ask you if you want to save the file to disk): mk:@MSITStore:C:\Program%20Files\National%20Instruments\LabVIEW%208.5\help\lvhowto.chm::/objectnames.js (you can replace the "8.5" above with the LabVIEW version of interest) I have attached these files, here: Download File:post-17-1203021794.txt Download File:post-17-1203021800.txt Download File:post-17-1203021807.txt Download File:post-17-1203021814.txt Also, you'll need to un-URL-escape the names (e.g., convert "%20" into space characters), but all this can be automated, very easily. Cheers,

Yen, Here are some suggestions: First, I wouldn't override the File>>New VI operation. This is annoying, in my opinion. I would add an option to the Tools menu to start up the tool and have it run behind the scenes waiting on a configurable key combination. Second, I would take a look at Launchy, a really cool keystroke app launcher for Windows. It's very well designed and doesn't get into the way. After you press the magic key combo to activate it, you see a text input box. As you type, it shows you the one item that it guesses you want to launch. If you pause your typing for longer than some threshold (a few seconds), it shows you a list of the top matches. It's pretty cool. You can scroll through this list and double-click on the item you want. Cheers, -Jim

QUOTE(Adam Kemp @ Feb 14 2008, 11:05 AM) I believe that I've installed LabVIEW 8.0 and 8.2 on Ubuntu. I don't think that I've installed 8.5, yet.

QUOTE(Yen @ Feb 14 2008, 10:40 AM) I don't think that 7.1 has custom symbols either. PJM's cool UI example is written in 8.2. (I know, because I got to play with it :thumbup: )

Here is an article that I wrote a while back, which includes some info about how the palettes work: Customizing the LabVIEW Development Environment Cheers, -Jim

LabVIEW can be installed on Ubuntu (or Debian), but you need to convert the RPM packages to DEB packages using alien before they can be installed. Also, after the installation you will need to fix a symbolic link to the mesa shared library.

See here for links.

QUOTE(monash321 @ Feb 12 2008, 10:59 PM) Hi, I'm glad to hear that you are considering the book for your course. There are instructions on the book's website for how to contact the publisher to apply for an exam copy of the book (see the Instructors section on the main page). You might also want to try contacting Pearson Education India. Thanks, -Jim

QUOTE(crelf @ Feb 12 2008, 07:52 PM) NI USB-9162 - USB C Series Single Module Carrier http://sine.ni.com/nips/cds/view/p/lang/en/nid/204178

Custom item symbols works, too! Woohoo! :thumbup:

QUOTE(PJM_labview @ Feb 5 2008, 09:25 AM) Hmmm... the NI Example Finder window cannot be resized.