Jump to content

GOOP - Graphical Object Oriented Programming: Difference between revisions

From LabVIEW Wiki
Line 17: Line 17:
=== See Also  ===
=== See Also  ===


{{Portal|GOOP}}  
{{Portal|GOOP}}


*[[DqGOOP]]  
*[[DqGOOP]]
*[[GOOP History by Mattias Ericsson]]  
*[[GOOP History by Mattias Ericsson]]
*[[OpenGOOP]]
*[[OpenGOOP]]


[http://www.gangoflabview.ch GOOP by Reference LabVIEW OOP]=== External Links  ===
=== External Links  ===


*[http://zone.ni.com/devzone/conceptd.nsf/appnotebynumber/1A7B60096CE0CDA986256A9A0074E4EC?OpenDocument&node=dz52000_us App Note 143] – Graphical Object Oriented Programming (Jorgen Jehander)
*[http://zone.ni.com/devzone/conceptd.nsf/appnotebynumber/1A7B60096CE0CDA986256A9A0074E4EC?OpenDocument&node=dz52000_us App Note 143] – Graphical Object Oriented Programming (Jorgen Jehander)
Line 33: Line 33:


[[Category:GOOP]]
[[Category:GOOP]]
[[Category:GOOP]]
[[Category:GOOP]]

Revision as of 09:16, 24 January 2012

GOOP - Graphical Object Oriented Programming

GOOP stands for Graphical Object Oriented Programming. It is a category of frameworks for non-native object-oriented programming in LabVIEW that support by reference objects with VI methods for operating on data. Some versions of GOOP support inheritance and dynamic dispatch. GOOP really hit mainstream with the release of the GOOP Toolkit from Endevo and National Instruments. OpenG even has its own version of GOOP, called OpenGOOP.

With LVOOP and queues, it is very easy to create basic GOOP functionality. Examples are included in the example folder installed with LabVIEW.

GOOP is great because it allows you to build components that encapsulate their data, functionality, and behavior. Why ecapsulate?...

Benefits of Encapsulation

  • Maintainable
  • Scalable
  • Useable (and therefore Reusable)
  • Testable
  • Enable Multiple Developer Collaboration

See Also

External Links