topic Re: Do you write or draw a LabVIEW Program? in BreakPoint

Do you write or draw a LabVIEW Program?

TAP_ — Mon, 21 Nov 2011 11:43:17 GMT

Do you write or draw a LabVIEW Program?

As it’s not a proper programming language should it be draw?

Re: Do you write or draw a LabVIEW Program?

shjukheter — Mon, 21 Nov 2011 11:47:41 GMT

Usually I call it as wiring but if you want you can call it as drawing

You can see this videos for more help.

http://zone.ni.com/devzone/cda/tut/p/id/7466

Re: Do you write or draw a LabVIEW Program?

TAP_ — Mon, 21 Nov 2011 11:50:18 GMT

I like wiring it more descriptive!

Re: Do you write or draw a LabVIEW Program?

PaulG. — Mon, 21 Nov 2011 12:27:13 GMT

I prefer "wire". "Draw" only feeds the LV naysayers. "All you guys do is draw pictures all day." They never say the same thing about folks who draw schematics or blueprints.

Re: Do you write or draw a LabVIEW Program?

yenknip — Mon, 21 Nov 2011 13:19:43 GMT

@TAP_ wrote:

As it’s not a proper programming language should it be draw?

How do you define a 'proper' programming language?

Re: Do you write or draw a LabVIEW Program?

smercurio_fc — Mon, 21 Nov 2011 13:41:34 GMT

@PaulG. wrote:

They never say the same thing about folks who draw schematics or blueprints.

Yeah. These guys "sketch".

Re: Do you write or draw a LabVIEW Program?

TAP_ — Mon, 21 Nov 2011 13:43:39 GMT

I was waiting for a responces like this!

It's not as flexible a language as C++ or even C# and I'm always wasting time making the whole thing look pretty so that my colleges can understand what is going on in the code.

Re: Do you write or draw a LabVIEW Program?

smercurio_fc — Mon, 21 Nov 2011 13:53:41 GMT

@TAP_ wrote:

I was waiting for a responces like this!

It's not as flexible a language as C++ or even C# and I'm always wasting time making the whole thing look pretty so that my colleges can understand what is going on in the code.

I'm not even going to bother responding to a statement like this since it's meaningless, has been said way too many times before, and responded to way too many times before, and it's simply a bait. This fish is going somewhere else, thank you very much.

By the way, I program a lot in C# (and cut my teeth on text-based languages), so spare me the "you wouldn't say that if you programmed in text-based languages" spiel.

Re: Do you write or draw a LabVIEW Program?

TAP_ — Mon, 21 Nov 2011 13:56:39 GMT

but you did bite!

Re: Do you write or draw a LabVIEW Program?

yenknip — Mon, 21 Nov 2011 14:04:51 GMT

http://forums.ni.com/t5/BreakPoint/Nightmare/m-p/1733200/highlight/true#M16768

Re: Do you write or draw a LabVIEW Program?

smercurio_fc — Mon, 21 Nov 2011 14:04:56 GMT

My statement was more of a warning to others to simply ignore your comment. Some might even go so far as saying it's simply trolling.

Re: Do you write or draw a LabVIEW Program?

NIquist — Mon, 21 Nov 2011 15:16:36 GMT

Maybe he'll be a fun troll!

BTW, Do C coders write or type their programs???

Re: Do you write or draw a LabVIEW Program?

smercurio_fc — Mon, 21 Nov 2011 15:26:33 GMT

@NIquist wrote:

Maybe he'll be a fun troll!

Re: Do you write or draw a LabVIEW Program?

TAP_ — Mon, 21 Nov 2011 15:45:29 GMT

@NIquist wrote:

BTW, Do C coders write or type their programs???

They type them but it is the convention to say they write them. In the early days they punched holes in card so they must have punch programs in those days.

So what do you think, do you write, draw or wire LabVIEW Programs?

Re: Do you write or draw a LabVIEW Program?

billko — Mon, 21 Nov 2011 15:49:02 GMT

Since good LabVIEW programming is a work of art, why not "create?"

Re: Do you write or draw a LabVIEW Program?

altenbach — Mon, 21 Nov 2011 16:32:37 GMT

I typically just program something in LabVIEW (using the word "program" as a verb).

This term is generic enough to apply to any kind of computer programming.

Other words imply a specific physical action. Drawing, writing, typing, wiring, etc. "Wiring" is too limiting because it describes only a small subset of LabVIEW programming. We need to place the primitives and subVIs before we can wire them up. Also don't forget that we can create LabVIEW programs using voice commands, for example. Maybe somebody could even adapt kinect gestures for LabVIEW programming. 😄

(see also)

Re: Do you write or draw a LabVIEW Program?

Mark_Yedinak — Mon, 21 Nov 2011 16:52:34 GMT

What is the purpose of your posts? Are you trying to start some sort of LabVIEW bashing thread? Are you trying to rile the folks here on this forum? I get the sense that you do not like LabVIEW and are here simply to belittle those who do use it. If that is the case please feel free to leave. If not then perhaps should should clarify why you are asking the question.

Re: Do you write or draw a LabVIEW Program?

tst — Mon, 21 Nov 2011 17:19:48 GMT

@altenbach wrote:

Maybe somebody could even adapt kinect gestures for LabVIEW programming. 😄

Why "maybe"? http://www.youtube.com/watch?v=Pu95KXA8uDw&hd=1&t=2m49s

Personally, I use "write", although I don't think it really matters.

Re: Do you write or draw a LabVIEW Program?

TAP_ — Mon, 21 Nov 2011 17:58:26 GMT

@Mark Yedinak wrote:

What is the purpose of your posts? Are you trying to start some sort of LabVIEW bashing thread? Are you trying to rile the folks here on this forum? I get the sense that you do not like LabVIEW and are here simply to belittle those who do use it. If that is the case please feel free to leave. If not then perhaps should should clarify why you are asking the question.

I was writing documentation for a customer, It was a development plan for adding additional functionality to already "Drawn LabVIEW code". I changed it because I through it was unprofessional. As LabVIEW is sold as a graphical programming language then should we treat is as such when we describe code made using the language. In short guess I was trying to start a trend, I was surprised to not find anything similar on this forum.

I was not trying to belittle LabVIEW programmer as this would be hypocritical, I have my CLAD, will soon have my CLD and it is a large part of my job. I wrote it for the reaction ( I may do this on all my posts), sometime I feel that people look at LabVIEW through rose tinted glasses (especially thus who don't use it on a day to day basis). Most of the time I'm writing programs that would be more suited to another languages for no reason expect my boss/customers think it's the best thing ever.

Re: Do you write or draw a LabVIEW Program?

Mark_Yedinak — Mon, 21 Nov 2011 19:01:13 GMT

@TAP_ wrote:

I was writing documentation for a customer, It was a development plan for adding additional functionality to already "Drawn LabVIEW code". I changed it because I through it was unprofessional. As LabVIEW is sold as a graphical programming language then should we treat is as such when we describe code made using the language. In short guess I was trying to start a trend, I was surprised to not find anything similar on this forum.

I was not trying to belittle LabVIEW programmer as this would be hypocritical, I have my CLAD, will soon have my CLD and it is a large part of my job. I wrote it for the reaction ( I may do this on all my posts), sometime I feel that people look at LabVIEW through rose tinted glasses (especially thus who don't use it on a day to day basis). Most of the time I'm writing programs that would be more suited to another languages for no reason expect my boss/customers think it's the best thing ever.

Well, given that my degree is Computer Science and that I have been developing code in LabVIEW for many years now as well as written a significant amount of code in other traditional text based languages I think I have the experience to comment on this. With respect to terms when developing code in LabVIEW I don't think you need any special terminology. You are developing code and as such are programming. Just because it is graphical does not mean you should say "drawing". The true nature of programming is the design and architecture of the code regardless of the specifics of how it is implemented. Just like in OOP you design and define your classes in a generic manner which does not dictate implementation details or language. A design of an application is just that, a design. How it is implemented is up to the developer.

I would be interested in what areas you feel LabVIEW is ill suited. I have not really encountered any solution where I felt LabVIEW lacked the ability to implement the system. And for the record I use LabVIEW in my day to day life as a pure programming language. I can count on one hand how many pieces of external equipment I have used. So that in itself negates the argument that it is only good for test and measure or dealing with DAQ equipment. One shortcoming of LabVIEW has been it's ability to implement complex algorithms in a concise readable format. However with the formula node that is no longer the case. Embedded realtime systems are limited only by the current supported platforms. If LabVIEW supported more generic platforms I can easily see it being more widely utilized for realtime embedded development. As for a PC based application, I can't think of any application that LabVIEW would not be capable of implementing.

In my experience generally the folks who argue that LabVIEW is not a real programming language either have never used it and are simply biased or they have not fully embraced dataflow programming and are still thinking in terms of sequential or procedural programming.