Jim Kring

QUOTE (Val Brown @ Aug 28 2008, 06:50 PM) Hi Val, When you say that you "need to stay with as much native LV as possible", does that mean that you don't use VIs and only primitive functions? Nearly all the OpenG VIs are written in "native LV" (a.k.a., "Pure G"), with the exception of the zip library that makes a call into a DLL. I'm not trying to make light of your requirements, but to understand your environment and use cases. Thanks, -Jim

One great way to get your reusable VIs into the Quick Drop tool is to use VIPM to create a VI Package from and install them into the palettes.

QUOTE (ASTDan @ Aug 21 2008, 11:15 AM) Yes, and hopefully there will be more coming, soon, now that http://forums.jkisoft.com/index.php?showtopic=853' rel='nofollow' target="_blank">it's so easy to build VI Packages. Cheers, -Jim

1) Make sure that connector panes of old VI and new VI match 2) Add new VI to class (so that it is a member) and save the class and new VI 3) close LabVIEW 4) on disk, rename Old VI as New VI and rename New VI as Old VI (meaning swap names on disk) 5) open LabVIEW and your class -- it should relink the way that you want 6) remove the VI that you don't want from the class (it will be named "New VI", but it's really the Old VI) and save your class -- you can also remove this VI from disk.

QUOTE (Pollux @ Aug 20 2008, 12:23 AM) There's a great Info-LabVIEW thread on the topic called http://sthmac.magnet.fsu.edu/cgi-bin/ILVsearch/search.pl?Match=1&Realm=ILV2003&Terms=%22Three+Button+Dialog.vi%22' rel='nofollow' target="_blank">Three Button Dialog.vi.

QUOTE (crelf @ Aug 19 2008, 01:18 PM) I know this is off topic, but I think you're right

QUOTE (crelf @ Aug 17 2008, 04:42 PM) I'm not so sure about that -- I can't believe that I said "certificated"

Welcome, Tom, to the LabVIEW blog community. It's very interesting how the certification topic generates such passionate debate and discussion! I'll reiterate my perspective on certification, which is that certification is an important part of sharpening the tool, both for the individuals getting certificated and for the organizations that encourage the practice. As crelf alludes to, most work comes from having great solutions, created by skilled engineers, and a track-record of success. Making sure that your team and organization stay sharp is what enables this process. Certification might not be a great value for every team, but it sure is for ours. Cheers,

QUOTE (MrFURioUS @ Aug 14 2008, 06:12 PM) Hello MrFURioUS, http://jkisoft.com/vipm' rel='nofollow' target="_blank">VI Package Manager is the only way to go! Thanks, -Jim PS - Any other legacy stuff (OGPI, OpenG Commander) is not supported and might not work. Plus VIPM is way cool!

QUOTE (jlokanis @ Aug 14 2008, 11:03 AM) I believe so. There is a new build specification called RESTful Web Service.

John, I've just posted a question on OpenG: What are your results with OpenG on LabVIEW 8.6? Hopefully we'll get some more data points Thanks, -Jim

[cross-post] Hi All, It was great seeing so many of you at NIWeek 2008. I can't wait for next year! We got a lot of good feedback on the JKI presentations and I wanted to share some tips that our team uses to create a great "user experience" for the audience (it's not unlike creating a great software user experience, in fact). Here's a blog article with some of our tips: Delivering Sold-out NIWeek Presentations If you have ideas about how to deliver great presentations or have feedback on our NIWeek 2008 presentations, don't be shy! We want to hear what you have to say and comments are always welcome Thanks, -Jim

QUOTE (James N @ Aug 14 2008, 07:56 AM) QUOTE (crelf @ Aug 14 2008, 09:12 AM) That's an easy one - use VIPM. Thanks for the plug on this, crelf! By the way, we have a page that describes how to use VIPM in conjunction with source code control, here: Using VI Package Builder with Source Code Control

Hi John, We haven't done exhaustive testing of OpenG in LabVIEW 8.6, but we (JKI) have installed OpenG in 8.6 using VIPM and it appears to work fine. We have also run the entire unit test suite for EasyXML in 8.6. One of our customers reported that a very large app consumed more memory in 8.6, than it did in 8.5. Thanks, -Jim

A cold convention center provides half of the comedic material for the keynotes (the other half being how hot Austin is in August). Without that, NI will have to hire some better writers. Hmmm.... sounds like a great idea to me PS - I'm mostly joking. I did like the engineering mind videos.

QUOTE (Omar Mussa @ Aug 9 2008, 02:50 PM) I'll start a petition

I've been out of town for about 3 weeks (trip to France and then NIWeek) and my LAVA RSS reader has over a thousand unread posts -- I have absolutely no chance of reading them all, so... What did I miss while I was gone? PS - I'm glad to be back

Jed, 1) I flew United direct from Austin to SF. 2) It was great fun hanging out on Thursday night with you and the other stranded folks! Cheers, -Jim

QUOTE (Norm Kirchner @ Jul 21 2008, 12:17 PM) Thanks, Cap'n -Jim

The Jott iPhone app is pretty cool!

QUOTE (Gary Rubin @ Jul 11 2008, 05:41 AM) Don't you mean http://forums.lavag.org/neB-m29.html' target="_blank">neB? Congratulations, Ben, and thanks for being part of what makes LAVA and the LabVIEW community so great!!! :thumbup:

QUOTE (Eugen Graf @ Jul 12 2008, 04:25 PM) How about an emotional song? "Fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa-fa... I keep singing them sad sad songs... sad songs are all I know."

Gavin: Thanks for the great description of dictionaries. Dan: You can find some documentation here. Also, take a look here: Examples <LabVIEW>\examples\OpenG\dictionary\ Help Docs <LabVIEW>\help\OpenG\dictionary\Dictionary.htm Cheers,

I have a buddy who picked up a box of durian hard candy that he picked up while traveling in the Philippines. He likes to bring the box out at parties and offers them to unsuspecting party-goers. It tastes OK at first, and then, as the candy starts to dissolve, so does the smile on the face of the victim.

[cross-post] Hi All, I've written a follow-up article on software reuse that I think will hit close to home for many LabVIEW developers. I know that it certainly describes some of the experiences and frustrations I've felt, over the years, while trying to reuse VIs. As usual, I'm interested in your feedback Top 5 signs you've lost control of your reusable VIs Thanks, -Jim