BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Retired LabVIEW features?

I have to say I feel cheeky for begging the 99th kudo for the SDE idea here. Not to sum-up, after helping a lot a fast learning new LabVIEW user, I asked him to vote in return for the help I provided to him. (all in frecnh sorry...)


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

Message 31 of 35
(6,571 Views)

@Daklu wrote:

"I would have thought that there was an easy route into basic LVOOP..."

 

Sure, that's a fairly easy way to get started for those already motivated to learn it for other reasons.  But for many developers it doesn't provide a reason to learn LVOOP in the first place.  What pain is being reduced for the CLA level developer by replacing clusters with classes?  In many cases the answer is nothing--they already have coding conventions or dev practices in place to prevent the pain.  For those people creating a class and providing accessors is pointless.

 

 

"Keeping bundle/unbundled private to a library is already a significant architectural advantage... but LVOOP is already an advantage used simply."

 

Personally I agree with you.  I place a very high priority on managing dependencies and LVOOP helps me keep things organized, so it is a significant architectural advantage to me.  However, the things that are important to me and that I value aren't necessarily the same things that are important to anyone else.  Whether or not an arbitrary feature/practice is an advantage depends on what an individual or organization values.


I (as a lone programmer) found just the customized wires quite attractive all by itself.  No more multiple indistinguishable cluster wires on a block diagram.  But if I were to architecture code for a group of programmers, making bundle/unbundle private to the library and thus allowing a well-defined public API seems extreemly valuable.  However, I never really much used things like "Action Engines" that might give some of the same advantages.

 

Now, dynamic dispatch is a whole new level of advantage, but one that does have a bit of a learning curve to it.  I made simple uses of classes for over a year before I attempted any inheritance.  

 

-- James

0 Kudos
Message 32 of 35
(6,561 Views)

@TiTou wrote:

I have to say I feel cheeky for begging the 99th kudo for the SDE idea here. Not to sum-up, after helping a lot a fast learning new LabVIEW user, I asked him to vote in return for the help I provided to him. (all in frecnh sorry...)


 

My boss had the privledge of pushing you into triple digits.

 

Go SDE Go!

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 33 of 35
(6,536 Views)

Ben wrote:

My boss had the privledge of pushing you into triple digits.

 

Go SDE Go!

 

Ben

 


Each and every kudo is a struggle Smiley Very Happy


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 34 of 35
(6,533 Views)

@TiTou wrote:

Ben wrote:

My boss had the privledge of pushing you into triple digits.

 

Go SDE Go!

 

Ben

 


Each and every kudo is a struggle Smiley Very Happy


Well, you guys have campaigned enough.  I've never used it, but if it is half as useful as Ben makes it out to be, I will definately use it.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 35 of 35
(6,513 Views)