NI Community Example Code Archive

[Lycangeek]

I wanted to let everyone know that we (NI) have created a new site (http://community.ni.com/) for archiving user's example code. Some of you may know that we've had an example code submission page, but the major complaint was that all the code submitted ended up being owned by National Instruments.

So welcome to the new site! This portal allows you to submit AND OWN the example code. Once it's submitted, you can go back and do updates, maintain revision history and post links back to the archive. There's also an RSS feed if you want to keep up with the new examples.

Anyway, the site is still in beta so you'll need to create a profile just for it right now. Please check it out, search around and if you can, submit some examples. Let us have your feedback!

BTW - I'm actually not involved with the new site, I'm just hyping it 🙂

[smercurio_fc]

This looks like it might be a good place to start for people looking for examples. Of course, it's all contingent on folks submitting examples. I might have missed it, but do you know if guidelines exist on the format of examples? I know you said you're not involved, but perhaps someone who is can answer this...

Also, a side comment/suggestion: Not sure why it's been chosen to break down the categories to the edition level of the software package. With this you have three separate LabVIEW categories. I understand that some VIs won't work in one edition if it's using VIs that are not available in that edition. However, if I have the Professional edition, and I write a VI that doesn't really use Professional edition only VIs, then in which category do I put it? This is quite confusing. My suggestion is to have just one LabVIEW category, and let the examples indicate edition restrictions. The same would apply to the other application packages.

[Russ_Evans]

I agree with smercurio_fc, one labview category seems best. Perhaps in listing the examples footnotes or asterisks or something similar could be used to distinguish whether or not the examples require something more than the base package.

Cheers,

--Russ

Message Edited by Russ Evans on 05-12-2006 01:31 PM

[ColinAE]

Thanks a bunch for the feedback.

Indeed, I agree that it is confusing to list all of the "sub-flavors" of the Application Software.  I believe we should have solution for this upcoming.

Just so you know the reason - we source those pull-down menus from some managed list lookups that are applied site-wide. . .and thus the granularity.  This is also why super-new technologies such as "BridgeVIEW" are in the list . . .