Survey for LabVIEW users

[tbob]

---

Ben wrote:

To Rolf and all of you that have been doing this longer than me...

Could you please confirm or rule-out a bit of a pattern that I have noticed?

Does it seem like the LV community have improved the structure and readability of their diagrams over the years?

The introduction of control refs so we can push the details of the GUI fiddling down into sub-VI has helped quite a bit since we don't have to do that in the top level VI anymore.

It just seems that back when I started using LV seriously (1999) the diagrams were horendous. Since the advent of the NI forum and Christian beating on the "style drum" things are much better.

Any insight?

Ben

---

I first started Labview in 2000.  But I can truly say that the structure and readability of my code has vastly improved over the years.  Example:  I started off using the stacked sequence structure, then I went into the one long horizontal screen type of vi, then I learned about state machines.  Huge difference in readability and structure.  This forum has really contributed to my improvements.  So I'm asking Christian and all the "old" pros to keep beating the style drum for newcomers.

I actually did some style beating in my last job, and I saw vast improvements in my co-workers code.

[Ray.R]

Ditto, tbob.

This forum and the LV courses have greatly improved my coding style and selection of architecture.

Not sure why they are doing such a survey.  I agree with Ben's posts.  It's skewed and a waste of time.

[Coq_Rouge]

What you are trying to might have some relevance, and be useful. And to do a survey is also correct. But after that point your efforts seams to be a total mess. Then I took your survey I first suspected that someone had hacked the school web system in order to do phishing. Or that this was some school project made by some low level students. Not a work done by an assistant professor. For a Labview user your questions are total incomprehensible. And what has Labview to do with methods used in a spreadsheet program

 

The idiom comparing apples and oranges, is a good description of what you are trying to do. It is also quite tragicomic that you use some work dated back to 1996 as reference. Much have changed since that time, as Labview has developed. My advice to you is. Go back to your cubical and try again, because this is not some assistant professor material . Do some research what Labview really is. Talk to some professional Labview users. I have been using Labview since at least 1998. I feel more like a Labview smith. In order to make code. I Twist, bend, and forge different Labview code together. And reusing is a important part of this. Both code and front panel objects. I use any code that I find useful. I sometimes find code on the internet. But this type of code more thorough validated as I do not know the source.

I also think that if you come up with an understandable survey people will not be negative. Well at least that is  my 02 cent.  

Message Edited by Coq Rouge on 04-26-2010 12:07 PM

[Coq_Rouge]

In this forum I can only speak for my self. But I can not see anything wrong if you come with an improved survey and post it in this forum.

[muks]

---

herrlin wrote:

---

muks wrote:

Jim,

One sure thing. Reading so much of texts will make you like labVIEW even better...

---

I was going to ask for some more pictures because I a cant under stand this survey.

---

they should know that we labVIEWers see\draw and dont read stuffs..

[Coq_Rouge]

The assistant professor has been somewhat quiet lately. Perhaps we was to harsh with him.

[altenbach]

---

Ben wrote: 

Does it seem like the LV community have improved the structure and readability of their diagrams over the years?

---

 It is not just the community, but LabVIEW itself, as well as advancements in computing hardware.

Code developed for a 800x600 monitor may over-use stacked sequences just to fit things on a single screen. Now you get these rookies starting out with 1920x1200 monitors, with the diagram maximized to the screen. 😉

The event structure has significantly changed how the code for the user interface looks. Looking at my old code, there is a lot of (now) unnecessary garbage code just to prevent recalculations unless relevant inputs change. Back then, there were no "projects", just a folder (or even worse: a llb) full of VIs.

The example finder has some extremely old examples, some are excellent, and some are pretty horrible. Look for the ones that still use classic controls and indicators. 😉 (Some of the newer examples are not that great either).

The best way to improve coding habits is by example. I always try to make an effort towards diagram neatness (whatever that means) when posting an example here. Hopefully, some will rub off in the long run. 😉