From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-11-2016 08:26 AM
@crossrulz wrote:
Express VIs will get you started, but don't expect to go far with them
Except that proverb isn't true. Express VIs got a bad rap because some specific express VIs were designed for very low end use cases. But there are some that are quite powerful, and the concept is really REALLY powerful. Express VIs are simply a dialog-driven way to fill in a code template; that template can be as complex or as simple as you want it to be. In its most ridiculous form, the express VI dialog could be an entirely different model of computation, with its own diagram or text editor, which runs through a compiler to generate G code. It's a really open-ended technology.
04-11-2016 08:57 AM
AristosQueue wrote: Express VIs got a bad rap because some specific express VIs were designed for very low end use cases.
Unfortunately, those are the ones we have had to deal with. Yes, they have their place. But to a normal user, the supplied Express VIs are very limited in ability and they need to figure out quickly that they have severe limits in capability.
I did not mean to say that the Express VI technology was bad. Yes, you can do some really cool things with them.
04-11-2016 09:27 AM
@crossrulz wrote:I did not mean to say that the Express VI technology was bad. Yes, you can do some really cool things with them.
I see little difference between express vis and something you would use from a code reuse library. Sure the code in your library might be a teeny bit more efficient but so what? What makes an express vi better IMO is the on-the-fly customization that happens every time you set one up. I think they're very handy.
06-23-2016 08:24 AM
Sometimes an analogy comes to me that I actually like. Today was one of those days.
"
Keeping an output running at the same rate as an input is a lot like reaching out over the front of a railroad locomotive to lay down track you just picked from behind the train.
If you do not stay ahead of the progress it will not go well.
"
Ben
06-23-2016 09:33 AM
I'd like to nicely add that this proverb is not limited to LabVIEW. But it has a strong relation 😉
06-23-2016 09:18 PM
Reminds me of Wallace and Gromit. 🙂
08-10-2016 02:05 PM
As I posted in this thread...
There is a quote from the musical Hello Dolly where (was it Mr Madison) eventually came around to the opinion held by Dolly
"Money Knowlege is like manure. It does the most good when you spread it around."
Ben
08-20-2016 01:52 PM
You mentioned Mondrian and sparked my art geekiness. Now my LabVIEW geekiness and art geekiness have combined to a whole new level of geekiness!
Chief LabVIEW Architect, Testeract | Owner, Q Software Innovations, LLC (QSI)
Director, GCentral | Admin, LabVIEW Wiki | Creator, The QControl Toolkit
Certified LabVIEW Architect | LabVIEW Champion | NI Alliance Partner
08-22-2016 08:47 AM
I shared a sea story here ending with ...
"
If you over-load something, do not be suprised if it fails.
The same thing applies to Dremel tools, drills, and LV.
"
Ben
08-22-2016 09:14 AM
Where does Mondrian come from? I don't quite see his name in this thread. However I kind of like the Mondrian type BD... what does the code actually do ;-). Would be nice if it was drawn by itself.
Happy wireworks
Urs