Command pattern - Revision history

Q: Category reorg

2020-06-02T21:01:27Z

Category reorg

← Older revision		Revision as of 21:01, 2 June 2020
Line 17:		Line 17:
	[[Category:Object-Oriented Programming]]		[[Category:Object-Oriented Programming]]
	[[Category:Object-Oriented Design Pattern]]		[[Category:Object-Oriented Design Pattern]]
	~~[[Category:Design patterns]]~~

Logmanoriginal: Add working links for object and class

2020-04-06T10:20:30Z

Add working links for object and class

← Older revision		Revision as of 10:20, 6 April 2020
Line 1:		Line 1:
	'''Command pattern''' is a basic [[design pattern]] in [[object-oriented programming]] in which an [[object]] is used to [[encapsulation\|encapsulate]] data and behavior in order to perform an action or trigger an [[event]] at a later time. The client then executes a command through a common interface that is provided by the parent [[class]].		'''Command pattern''' is a basic [[design pattern]] in [[object-oriented programming]] in which an [[object (object-oriented programming)\|object]] is used to [[encapsulation\|encapsulate]] data and behavior in order to perform an action or trigger an [[event]] at a later time. The client then executes a command through a common interface that is provided by the parent [[class (object-oriented programming)\|class]].

	This pattern is typically used in message handlers to avoid the need to convert data to/from [[variant]] or [[string]]. It requires the definition of a generic parent class, which defines the interface that must be implemented by its child classes. For every command a new child class is required. Each child class then overrides the execution method of the parent class to implement the specific functionality.		This pattern is typically used in message handlers to avoid the need to convert data to/from [[variant]] or [[string]]. It requires the definition of a generic parent class, which defines the interface that must be implemented by its child classes. For every command a new child class is required. Each child class then overrides the execution method of the parent class to implement the specific functionality.

Logmanoriginal: Add new page

2020-03-30T13:36:32Z

Add new page

New page

'''Command pattern''' is a basic [[design pattern]] in [[object-oriented programming]] in which an [[object]] is used to [[encapsulation|encapsulate]] data and behavior in order to perform an action or trigger an [[event]] at a later time. The client then executes a command through a common interface that is provided by the parent [[class]].

This pattern is typically used in message handlers to avoid the need to convert data to/from [[variant]] or [[string]]. It requires the definition of a generic parent class, which defines the interface that must be implemented by its child classes. For every command a new child class is required. Each child class then overrides the execution method of the parent class to implement the specific functionality.

[[File:Command Pattern.png]]

The command pattern is sometimes combined with the [[channeling pattern]] for pre-processing/post-processing around the execution method of child classes.

==See also==
* [[Queued Message Handler]]
* [[Actor Framework]]

==External links==
* [https://forums.ni.com/t5/LabVIEW-Development-Best/Command-Pattern-for-LabVIEW-OOP/ta-p/3539427 LabVIEW Development Best Practice Documents - Command Pattern for LabVIEW OOP]
* [[Wikipedia:Command pattern|Command pattern]] (Wikipedia)

[[Category:Object-Oriented Programming]]
[[Category:Object-Oriented Design Pattern]]
[[Category:Design patterns]]