Factory pattern - Revision history

Q: /* Best practice */ Fixed library links

2020-06-09T16:05:59Z

Best practice: Fixed library links

← Older revision		Revision as of 16:05, 9 June 2020
Line 21:		Line 21:
	==Best practice==		==Best practice==
	* Child classes should be placed in a dedicated directory next to the application executable.		* Child classes should be placed in a dedicated directory next to the application executable.
	* Child classes should be distributed as [[LabVIEW Library\|LabVIEW Libraries]] or [[Packed Project Library\|Packed Project Libraries]].		* Child classes should be distributed as [[LabVIEW Library\|LabVIEW Libraries]], [[LabVIEW Project Library\|LabVIEW Project Libraries]], or [[Packed Project Library\|Packed Project Libraries]].

	==See also==		==See also==

Q: /* Distributing child classes */ fixed library links

2020-06-09T16:05:22Z

Distributing child classes: fixed library links

← Older revision		Revision as of 16:05, 9 June 2020
Line 11:		Line 11:

	==Distributing child classes==		==Distributing child classes==
	Child classes can be distributed as part of the application executable, as source files, or as separate libraries, such as a [[LabVIEW Library]] or [[Packed Project Library]]. If child classes are dynamically loaded from disk, it is also possible to add new child classes to an existing application without rebuilding the executable. In this case child classes must include all of their [[Dependency\|dependencies]]. This can result in a large number of files for each child class, in which case a [[LabVIEW Library]] or [[Packed Project Library]] can be used to store these files in a single container file.		Child classes can be distributed as part of the application executable, as source files, or as separate libraries, such as a [[LabVIEW Library]], [[LabVIEW Project Library]], or [[Packed Project Library]]. If child classes are dynamically loaded from disk, it is also possible to add new child classes to an existing application without rebuilding the executable. In this case child classes must include all of their [[Dependency\|dependencies]]. This can result in a large number of files for each child class, in which case a [[LabVIEW Library]] or [[Packed Project Library]] can be used to store these files in a single container file.

	===Distributing child classes as part of the application===		===Distributing child classes as part of the application===
Line 17:		Line 17:

	===Distributing child classes as separate libraries===		===Distributing child classes as separate libraries===
	Child classes can be distributed separately from the main application by placing source files or class libraries, such as a [[LabVIEW Library]] or [[Packed Project Library]], into a pre-defined location that is used by the factory to create new objects. The benefit of this is the ability to dynamically add features after the application has been delivered and the ability for other developers to add more child classes to an application without having to rebuild the executable.		Child classes can be distributed separately from the main application by placing source files or class libraries, such as a [[LabVIEW Library]], [[LabVIEW Project Library]], or [[Packed Project Library]], into a pre-defined location that is used by the factory to create new objects. The benefit of this is the ability to dynamically add features after the application has been delivered and the ability for other developers to add more child classes to an application without having to rebuild the executable.

	==Best practice==		==Best practice==

Q: Category reorg

2020-06-02T21:02:35Z

Category reorg

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

Logmanoriginal: Add interwiki links

2020-03-29T17:41:21Z

Add interwiki links

← Older revision		Revision as of 17:41, 29 March 2020
Line 24:		Line 24:

	==See also==		==See also==
	* [[~~Wikipedia:Factory (object~~-~~oriented programming)\|Factory (object-oriented programming)~~]]		* [[Design pattern]]
			* [[Object-Oriented Design Patterns]]

	==External links==		==External links==
			* [[Wikipedia:Factory (object-oriented programming)\|Factory (object-oriented programming)]]
	* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]		* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]
	* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]		* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]

Logmanoriginal: Move external links into separate section

2020-03-29T17:40:17Z

Move external links into separate section

← Older revision		Revision as of 17:40, 29 March 2020
Line 25:		Line 25:
	==See also==		==See also==
	* [[Wikipedia:Factory (object-oriented programming)\|Factory (object-oriented programming)]]		* [[Wikipedia:Factory (object-oriented programming)\|Factory (object-oriented programming)]]

			==External links==
	* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]		* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]
	* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]		* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]

Logmanoriginal: Add new category for object-oriented design pattern

2020-03-29T17:31:20Z

Add new category for object-oriented design pattern

← Older revision		Revision as of 17:31, 29 March 2020
Line 28:		Line 28:
	* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]		* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]

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

Logmanoriginal: Fix typos and remove references section

2020-03-29T17:25:22Z

Fix typos and remove references section

← Older revision		Revision as of 17:25, 29 March 2020
Line 4:		Line 4:

	==Loading new child classes into memory at runtime==		==Loading new child classes into memory at runtime==
	Some factory methods or functions utilize [[Get LV Class Default Value (function)\|Get LV Class Default Value]] to dynamically load a child class into memory at runtime. This is done by providing the absolute path to a child class to ''Get LV Class Default Value'', which will load the class into memory and return an object of that class as generic [[LabVIEW object (type)\|LabVIEW object]]. This generic object can then be cast into the more specific parent class.		Some factory methods or functions utilize [[Get LV Class Default Value (function)\|Get LV Class Default Value]] to dynamically load a child class into memory at runtime. This is done by providing the absolute path to a child class to ''Get LV Class Default Value'', which will load the class into memory and return an object of that class as a generic [[LabVIEW object (type)\|LabVIEW object]]. This generic object can then be cast into the more specific parent class.

	[[File:Factory Pattern.png]]		[[File:Factory Pattern.png]]
Line 11:		Line 11:

	==Distributing child classes==		==Distributing child classes==
	Child classes can be distributed as part of the application executable, as source files, or as separate libraries, such as a [[LabVIEW Library]] or [[Packed Project Library]]. If child classes are dynamically loaded from disk, it is also possible to add new child classes to an existing application without rebuilding the executable. In this case child classes must include all of ~~its~~ [[Dependency\|dependencies]]. This can result in a large number of files for each child class, in which case a [[LabVIEW Library]] or [[Packed Project Library]] can be used to store these files in a single container file.		Child classes can be distributed as part of the application executable, as source files, or as separate libraries, such as a [[LabVIEW Library]] or [[Packed Project Library]]. If child classes are dynamically loaded from disk, it is also possible to add new child classes to an existing application without rebuilding the executable. In this case child classes must include all of their [[Dependency\|dependencies]]. This can result in a large number of files for each child class, in which case a [[LabVIEW Library]] or [[Packed Project Library]] can be used to store these files in a single container file.

	===Distributing child classes as part of the application===		===Distributing child classes as part of the application===
	Child classes can be distributed with the application executable by including every child class in the '''Always Included''' section on the '''Source Files''' page of the [[build specification]] and by setting the '''Destination''' for each child class on the '''Source File Settings''' page ~~of the build specification~~.		Child classes can be distributed with the application executable by including every child class in the '''Always Included''' section on the '''Source Files''' page of the [[build specification]] and by setting the '''Destination''' for each child class on the '''Source File Settings''' page.

	===Distributing child classes as separate libraries===		===Distributing child classes as separate libraries===
Line 27:		Line 27:
	* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]		* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]
	* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]		* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]

	~~==References==~~
	~~<references/>~~

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

Logmanoriginal: Add new page

2020-03-29T17:19:48Z

Add new page

New page

'''Factory pattern''' is a basic [[design pattern]] in [[object-oriented programming]] that provides a way to initialize a parent [[object]] with data from different child [[class]]es based on some input value, such as an [[enum]] or [[string]] value. This may include dynamically loading new child classes into memory at runtime. A factory [[method]] or [[function]] creates different objects without exposing the instantiation logic to the client. The client then refers to the newly created object through a common interface that is provided by the parent class.

This pattern is generally used in applications that have a [[plug-in]] component, or some functionality that needs to be loaded dynamically at runtime. It requires the definition of a generic parent class, which encapsulates functionality that can be reused and extended by child classes.

==Loading new child classes into memory at runtime==
Some factory methods or functions utilize [[Get LV Class Default Value (function)|Get LV Class Default Value]] to dynamically load a child class into memory at runtime. This is done by providing the absolute path to a child class to ''Get LV Class Default Value'', which will load the class into memory and return an object of that class as generic [[LabVIEW object (type)|LabVIEW object]]. This generic object can then be cast into the more specific parent class.

[[File:Factory Pattern.png]]

The error output of [[To More Specific Class (function)|To More Specific Class]] is used to determine if the newly created object is a child of the parent class. Additional error handlers are often necessary to report broken or missing child classes to the client.

==Distributing child classes==
Child classes can be distributed as part of the application executable, as source files, or as separate libraries, such as a [[LabVIEW Library]] or [[Packed Project Library]]. If child classes are dynamically loaded from disk, it is also possible to add new child classes to an existing application without rebuilding the executable. In this case child classes must include all of its [[Dependency|dependencies]]. This can result in a large number of files for each child class, in which case a [[LabVIEW Library]] or [[Packed Project Library]] can be used to store these files in a single container file.

===Distributing child classes as part of the application===
Child classes can be distributed with the application executable by including every child class in the '''Always Included''' section on the '''Source Files''' page of the [[build specification]] and by setting the '''Destination''' for each child class on the '''Source File Settings''' page of the build specification.

===Distributing child classes as separate libraries===
Child classes can be distributed separately from the main application by placing source files or class libraries, such as a [[LabVIEW Library]] or [[Packed Project Library]], into a pre-defined location that is used by the factory to create new objects. The benefit of this is the ability to dynamically add features after the application has been delivered and the ability for other developers to add more child classes to an application without having to rebuild the executable.

==Best practice==
* Child classes should be placed in a dedicated directory next to the application executable.
* Child classes should be distributed as [[LabVIEW Library|LabVIEW Libraries]] or [[Packed Project Library|Packed Project Libraries]].

==See also==
* [[Wikipedia:Factory (object-oriented programming)|Factory (object-oriented programming)]]
* [https://forums.ni.com/docs/DOC-13724 LabVIEW Development Best Practice Documents - Factory Pattern]
* [https://vishots.com/005-visv-labview-class-factory-pattern/ Optimizing LabVIEW Class Loading with the Factory Pattern]

==References==
<references/>

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