NI forum post asking about LVOOP design pattern

[jcarmody]

Seen here.

Can someone point me to a LabVIEW example of this OOP design? I am learning OOP in LabVIEW and my task is to create an example program using the facade design pattern. I can't find an example to study.

This is something I'm interested in as well...

[mje]

Heh, I'm even interested in an intelligible example of the facade pattern in *any* language. I find the chapter in Gamma et a less than enlightening.

[drjdpowell]

Excuse my ignorance, but isn't this an extremely common pattern, outside of OOP as much as in it? It's just a simplifying "wrapper" API about a more complex lower-level API. Many "LabVIEW drivers" are facades of other APIs such as ActiveX, VISA, or some dll or other.

-- James

[mje]

That's my interpretation, which left me wondering why it even is a pattern. To me it's no different than creating a sub VI that manages several calls to other VIs, whether we are talking about objects or not.

I always figured there was some magical subtlety I was missing that made the pattern worthy of a special name. I guess not?

[jcarmody]

The looking I did has me thinking that it is similar to an interface, or a wrapper around an interface.

[Aristos Queue]

> I always figured there was some magical subtlety I was missing that made the pattern worthy of a special name.

Nope. Patterns are patterns, even the very common ones. Having said that, it is amazing how often in software design that people go to great lengths to solve problem XYZ, and someone else pipes up with, "Why don't you just do MNO?" where MNO is some common action. That's often the case with the facade pattern... rather than trying to call an api directly, create a facade that you call through.