[Greg McKaskle]

Yep. I mean a textual description. If it is a question looking for input, the most valuable info is often the assumptions and goals, then the approach, then if it benefits things, the picture of the code or the VI.

If it is an answer to a question, it often involves a smart-alec comment, overly long background, and finally a description of the solution or a picture of the code that implements it.

Your question about professional usage is a good one. If you go to the NI forums, you'll be able to observe the daily trade of VI info. I qualify as a professional user, technically, but I'm also privy to lots of internal info. So up until a few years ago, I was often the one doling out the answers. There are a few posts with my name on them.

Perhaps things are changing, but to reiterate my answer, much of the discussion was textual, describing the math or science, not necessarily focussing on the syntax of the language. If it involves performance or syntax, I think little beats a VI simplified to focus on the topic. People don't usually post the code to their entire hydro-electric plant control or electron microscope just isn't cool, but fortunately, most elements in LV are pretty modular, and you can often isolate things without too much work. Again, that isolation often points out the problem before you even post the question.

Assuming most apps will be based upon the robotics from WPI, the team code should actually be pretty small. It will of course be highly coupled to the HW setup. I guess we'll see as things get going.

Greg McKaskle