Graphical Object-Oriented Programming - Revision history

Logmanoriginal: Logmanoriginal moved page GOOP to Graphical Object-Oriented Programming: Avoid abbreviations in page titles

2024-08-08T16:18:07Z

Logmanoriginal moved page GOOP to Graphical Object-Oriented Programming: Avoid abbreviations in page titles

← Older revision	Revision as of 16:18, 8 August 2024
(No difference)

Logmanoriginal: Mark as stub, mark for wikification

2024-08-08T16:16:26Z

Mark as stub, mark for wikification

← Older revision		Revision as of 16:16, 8 August 2024
Line 1:		Line 1:
			{{stub}}{{wikify}}
	This is the Portal for GOOP and LabVOOP.		This is the Portal for GOOP and LabVOOP.

Crelf at 16:58, 14 May 2014

2014-05-14T16:58:56Z

← Older revision		Revision as of 16:58, 14 May 2014
Line 1:		Line 1:
	This is the Portal for GOOP and LabVOOP.		This is the Portal for GOOP and LabVOOP.

	GOOP stands for "Graphical Object-Oriented Programming."		GOOP stands for "Graphical Object-Oriented Programming."
	LabVOOP stands for "LabVIEW Object-Oriented Programming."		LabVOOP stands for "LabVIEW Object-Oriented Programming."

	GOOP is a term used to refer to the various ~~GOOP~~ toolkits from Endevo/NI, SciWare and OpenG. These toolkits were written in G.		GOOP is a term used to refer to the various OOP toolkits from V I Engineering, Endevo/NI, SciWare and OpenG. These toolkits were written in G.

	LabVOOP refers to the native LabVIEW classes that first appeared in LV8.2.		LabVOOP refers to the native LabVIEW classes that first appeared in LV8.2.

	The toolkits were not obsoleted by the native implementation. All of the toolkits use a reference model for passing objects on the block diagram, similar to File refnums or Queue refnums in LabVIEW. The native classes pass by value, similar to clusters and arrays. The two mechanisms are complementary, not exclusionary, and there may be times when both approaches are used in the same LV program.		The toolkits were not obsoleted by the native implementation. All of the toolkits use a reference model for passing objects on the block diagram, similar to File refnums or Queue refnums in LabVIEW. The native classes pass by value, similar to clusters and arrays. The two mechanisms are complementary, not exclusionary, and there may be times when both approaches are used in the same LV program.

	==Pages Here:==		==Pages Here:==

Michael_Aivaliotis: GOOP moved to Portal:GOOP

2007-10-06T06:27:13Z

GOOP moved to Portal:GOOP

← Older revision	Revision as of 06:27, 6 October 2007
(No difference)

Jim kring: Added link to new page "LVOOP Frequently Asked Questions"

2007-08-13T22:22:40Z

Added link to new page "LVOOP Frequently Asked Questions"

← Older revision		Revision as of 22:22, 13 August 2007
Line 14:		Line 14:
	*[[History of GOOP]]		*[[History of GOOP]]
	*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]		*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]
			*[[LVOOP Frequently Asked Questions]]

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

MichaelAivaliotis: Added GOOP category.

2007-04-13T17:04:25Z

Added GOOP category.

← Older revision		Revision as of 17:04, 13 April 2007
Line 14:		Line 14:
	*[[History of GOOP]]		*[[History of GOOP]]
	*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]		*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]

			[[Category:GOOP]]

MichaelAivaliotis: Formatting

2007-04-13T17:02:30Z

Formatting

← Older revision		Revision as of 17:02, 13 April 2007
Line 10:		Line 10:
	The toolkits were not obsoleted by the native implementation. All of the toolkits use a reference model for passing objects on the block diagram, similar to File refnums or Queue refnums in LabVIEW. The native classes pass by value, similar to clusters and arrays. The two mechanisms are complementary, not exclusionary, and there may be times when both approaches are used in the same LV program.		The toolkits were not obsoleted by the native implementation. All of the toolkits use a reference model for passing objects on the block diagram, similar to File refnums or Queue refnums in LabVIEW. The native classes pass by value, similar to clusters and arrays. The two mechanisms are complementary, not exclusionary, and there may be times when both approaches are used in the same LV program.

	====Pages Here:====		==Pages Here:==
	*[[GOOP - Graphical Object Oriented Programming]]		*[[GOOP - Graphical Object Oriented Programming]]
	*[[History of GOOP]]		*[[History of GOOP]]
	*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]		*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]

Smercer: /* Pages Here: */

2007-04-13T13:25:27Z

Pages Here:

← Older revision		Revision as of 13:25, 13 April 2007
Line 13:		Line 13:
	*[[GOOP - Graphical Object Oriented Programming]]		*[[GOOP - Graphical Object Oriented Programming]]
	*[[History of GOOP]]		*[[History of GOOP]]
	*[[LVOOP\|[LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]		*[[LVOOP\|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]

Smercer at 13:25, 13 April 2007

2007-04-13T13:25:10Z

← Older revision		Revision as of 13:25, 13 April 2007
Line 13:		Line 13:
	*[[GOOP - Graphical Object Oriented Programming]]		*[[GOOP - Graphical Object Oriented Programming]]
	*[[History of GOOP]]		*[[History of GOOP]]
	*[[LVOOP]]		*[[LVOOP\|[LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]

Smercer at 13:22, 13 April 2007

2007-04-13T13:22:17Z

← Older revision		Revision as of 13:22, 13 April 2007
Line 13:		Line 13:
	*[[GOOP - Graphical Object Oriented Programming]]		*[[GOOP - Graphical Object Oriented Programming]]
	*[[History of GOOP]]		*[[History of GOOP]]
	*[LVOOP]]		*[[LVOOP]]