Deploying PC Developer apps - Revision history

MartinW: MartinW moved page App Developer Deployment to Deploying PC Developer apps: Name change

2023-12-13T09:10:49Z

MartinW moved page App Developer Deployment to Deploying PC Developer apps: Name change

← Older revision	Revision as of 09:10, 13 December 2023
(No difference)

MartinW: /* The deployment window */

2023-11-27T11:34:14Z

The deployment window

← Older revision		Revision as of 11:34, 27 November 2023
Line 38:		Line 38:
	**Alternatively, you can leave this option unchecked, and be provided simply with a single ".mscada" program file. This file can be then run manually with a copy of the Matrix SCADA runtime engine. This may be more useful for personal use and if you wish to experiment or store multiple copies of your program: without bundling a fresh copy of the Matrix SCADA runtime engine with every version of your program.		**Alternatively, you can leave this option unchecked, and be provided simply with a single ".mscada" program file. This file can be then run manually with a copy of the Matrix SCADA runtime engine. This may be more useful for personal use and if you wish to experiment or store multiple copies of your program: without bundling a fresh copy of the Matrix SCADA runtime engine with every version of your program.

	[[Running_.mscada_deployed_App_Developer_file\|See: Running .mscada deployed App ~~Developer_file~~]]		[[Running_.mscada_deployed_App_Developer_file\|See: Running .mscada deployed App Developer file]]

	==Components tab==		==Components tab==

MartinW: /* The deployment window */

2023-11-27T11:33:54Z

The deployment window

← Older revision		Revision as of 11:33, 27 November 2023
Line 38:		Line 38:
	**Alternatively, you can leave this option unchecked, and be provided simply with a single ".mscada" program file. This file can be then run manually with a copy of the Matrix SCADA runtime engine. This may be more useful for personal use and if you wish to experiment or store multiple copies of your program: without bundling a fresh copy of the Matrix SCADA runtime engine with every version of your program.		**Alternatively, you can leave this option unchecked, and be provided simply with a single ".mscada" program file. This file can be then run manually with a copy of the Matrix SCADA runtime engine. This may be more useful for personal use and if you wish to experiment or store multiple copies of your program: without bundling a fresh copy of the Matrix SCADA runtime engine with every version of your program.

			[[Running_.mscada_deployed_App_Developer_file\|See: Running .mscada deployed App Developer_file]]

	==Components tab==		==Components tab==

MartinW at 11:26, 9 March 2023

2023-03-09T11:26:02Z

← Older revision		Revision as of 11:26, 9 March 2023
Line 9:		Line 9:
	You may also wish to move the cameras to their ideal position for viewing on the 2D/3D panels.		You may also wish to move the cameras to their ideal position for viewing on the 2D/3D panels.

	Once this is done and you are happy with the state of your Flowcode program, select ~~FILE -~~> ~~DEPLOY AS FLOWCODE APP~~		Once this is done and you are happy with the state of your Flowcode program, select '''File''' > '''Export''' > '''Deploy as Flowcode App'''


Line 18:		Line 18:
	===Interface tab===		===Interface tab===

	[[File:FCSCADADeploy.~~jpg\|400px~~]]		[[File:FCSCADADeploy.png]]


Line 24:		Line 24:

	* Firstly, select which execution controls you want the user to have access to. E.g. "Start/Stop" buttons only.		* Firstly, select which execution controls you want the user to have access to. E.g. "Start/Stop" buttons only.
	** "Auto start on load" can also be selected, which forces the program to start execution immediately, stopping only when the Matrix ~~SCADA~~ runtime engine is closed. This option is not recommended for programs that require per-machine configuration settings to be applied before execution (e.g. anything involving com ports).		** "Auto start on load" can also be selected, which forces the program to start execution immediately, stopping only when the Matrix App Developer runtime engine is closed. This option is not recommended for programs that require per-machine configuration settings to be applied before execution (e.g. anything involving com ports).
	** If you want the user to have no control over the execution of the program, you can select "No controls". Note that this option also forces the "Auto start on load" option to be selected.		** If you want the user to have no control over the execution of the program, you can select "No controls". Note that this option also forces the "Auto start on load" option to be selected.

	* Secondly, select the main view that you want to be presented to the user for your program. This can be either the 2D ~~Dashboard~~ Panel or the 3D System Panel. It is recommended that you keep all "interactive" components (e.g. buttons, switches, displays) on a single panel in order to have a more streamlined interface, but this is not necessary.		* Secondly, select the main view that you want to be presented to the user for your program. This can be either the 2D Panel or the 3D System Panel. It is recommended that you keep all "interactive" components (e.g. buttons, switches, displays) on a single panel in order to have a more streamlined interface, but this is not necessary.
	** You may also choose to lock the ~~cameras~~ on the ~~2D and~~ 3D ~~panels~~ into place. This removes the ability to pan, rotate, zoom etc. on ~~these panels~~. The initial camera configuration will be the same as the current configuration at the time of export, so it is recommended that you position the camera appropriately before deploying with this option.		** You may also choose to lock the camera on the 3D panel into place. This removes the ability to pan, rotate, zoom etc. on the 3D panel. The initial camera configuration will be the same as the current configuration at the time of export, so it is recommended that you position the camera appropriately before deploying with this option.

	*Thirdly, for the remaining panels, select whether you want each panel to be always visible, optional, or removed entirely. It is also possible to choose whether to forcibly dock, forcibly float, or allow dock-or-float for each panel.		*Thirdly, for the remaining panels, select whether you want each panel to be always visible, optional, or removed entirely. It is also possible to choose whether to forcibly dock, forcibly float, or allow dock-or-float for each panel.
	**The Console Panel and Data Recorder Panel options are only available for deployment if you, as the developer, own the "Test and Debug" feature pack, otherwise they are forcibly removed. The end user of your Matrix ~~SCADA~~ runtime application does not require any licence.		The end user of your Matrix App Developer runtime application does not require any licence.

	*Fourthly, choose an official name for your program. This name will appear as the title bar for the end user. It may also appear as the folder name for your program if you choose to bundle the Matrix SCADA runtime.		*Fourthly, choose an official name for your program. This name will appear as the title bar for the end user. It may also appear as the folder name for your program if you choose to bundle the Matrix SCADA runtime.
Line 39:		Line 39:


	===Components tab===		==Components tab==

	This will show you a list of all the components in the project, you can select whether they will be visible to the end user or invisible, default is visible, to make a component invisible simply click on the component and then use the arrows in the middle to move to the invisible components box, this will work the other way too.		This will show you a list of all the components in the project, you can select whether they will be visible to the end user or invisible, default is visible, to make a component invisible simply click on the component and then use the arrows in the middle to move to the invisible components box, this will work the other way too.

	===Resources tab===		==Resources tab==

	With this tab Flowcode will suggest the embedded runtime resources which your ~~SCADA~~ project will need, you can press the "Suggest" button to do a scan of your project to see if there are linked resources missing from the list.		With this tab Flowcode will suggest the embedded runtime resources which your App Developer project will need, you can press the "Suggest" button to do a scan of your project to see if there are linked resources missing from the list.

	If you would like to create more advanced ~~SCADA~~ programs you can add your own DLL or other resource files here.		If you would like to create more advanced App Developer programs you can add your own DLL or other resource files here.

BenR at 14:49, 7 October 2020

2020-10-07T14:49:05Z

← Older revision		Revision as of 14:49, 7 October 2020
Line 11:		Line 11:
	Once this is done and you are happy with the state of your Flowcode program, select FILE -> DEPLOY AS FLOWCODE APP		Once this is done and you are happy with the state of your Flowcode program, select FILE -> DEPLOY AS FLOWCODE APP

	~~[[File:FCSCADAToolbar.png]]~~

	==The deployment window==		==The deployment window==

BenR at 14:48, 7 October 2020

2020-10-07T14:48:37Z

← Older revision		Revision as of 14:48, 7 October 2020
Line 1:		Line 1:
	==Introduction==		==Introduction==

	Matrix ~~SCADA~~ deployment allows you to take your Flowcode ~~SCADA~~ project, and deploy it as a standalone piece of software (known as a Matrix ~~SCADA~~ runtime application) built on top of the Matrix ~~SCADA~~ runtime. You are free to distribute this resulting application to users who don't have access to Flowcode, and don't ~~have~~ any license. End-users are prevented from viewing the source code of your program, as well as modifying the behaviour of the flowchart. They do however, have access to various Flowcode panels of your choosing, but cannot affect any changes to components. They also cannot modify component properties unless you explicitly grant them access.		Matrix App Developer deployment allows you to take your Flowcode App Developer project, and deploy it as a standalone piece of software (known as a Matrix App Developer runtime application) built on top of the Matrix App Developer runtime. You are free to distribute this resulting application to users who don't have access to Flowcode, and don't need any license. End-users are prevented from viewing the source code of your program, as well as modifying the behaviour of the flowchart. They do however, have access to various Flowcode panels of your choosing, but cannot affect any changes to components. They also cannot modify component properties unless you explicitly grant them access.

	==Preparing for deployment==		==Preparing for deployment==
Line 9:		Line 9:
	You may also wish to move the cameras to their ideal position for viewing on the 2D/3D panels.		You may also wish to move the cameras to their ideal position for viewing on the 2D/3D panels.

	Once this is done and you are happy with the state of your Flowcode program, ~~click on the "Deploy" button on the toolbar. Shown below.~~		Once this is done and you are happy with the state of your Flowcode program, select FILE -> DEPLOY AS FLOWCODE APP

	[[File:FCSCADAToolbar.png]]		[[File:FCSCADAToolbar.png]]

BenR: BenR moved page Matrix SCADA Deployment to App Developer Deployment

2020-10-07T14:46:58Z

BenR moved page Matrix SCADA Deployment to App Developer Deployment

← Older revision	Revision as of 14:46, 7 October 2020
(No difference)

DavidA: /* Resources tab */

2019-09-05T07:35:42Z

Resources tab

← Older revision		Revision as of 07:35, 5 September 2019
Line 46:		Line 46:
	===Resources tab===		===Resources tab===

	~~This allows~~ you to ~~embed resources with~~ your project~~, in order~~ to ~~make complex systems even~~ more ~~portable~~.		With this tab Flowcode will suggest the embedded runtime resources which your SCADA project will need, you can press the "Suggest" button to do a scan of your project to see if there are linked resources missing from the list.

			If you would like to create more advanced SCADA programs you can add your own DLL or other resource files here.

DavidA: /* Components tab */

2019-09-04T10:04:44Z

Components tab

← Older revision		Revision as of 10:04, 4 September 2019
Line 42:		Line 42:
	===Components tab===		===Components tab===

	This ~~allows~~ you ~~to choose which~~ components will be invisible in the ~~deployed runtime application~~.		This will show you a list of all the components in the project, you can select whether they will be visible to the end user or invisible, default is visible, to make a component invisible simply click on the component and then use the arrows in the middle to move to the invisible components box, this will work the other way too.


	===Resources tab===		===Resources tab===

	This allows you to embed resources with your project, in order to make complex systems even more portable.		This allows you to embed resources with your project, in order to make complex systems even more portable.

DanielM at 16:31, 15 November 2018

2018-11-15T16:31:19Z

← Older revision		Revision as of 16:31, 15 November 2018
Line 38:		Line 38:
	*Finally, choose whether to bundle the Matrix SCADA runtime engine with your program. In order for your program to be fully standalone and portable, you should check this option. This will create a folder on your filesystem which contains all required software to run your program. This folder can then be distributed to your end users, however you see fit.		*Finally, choose whether to bundle the Matrix SCADA runtime engine with your program. In order for your program to be fully standalone and portable, you should check this option. This will create a folder on your filesystem which contains all required software to run your program. This folder can then be distributed to your end users, however you see fit.
	**Alternatively, you can leave this option unchecked, and be provided simply with a single ".mscada" program file. This file can be then run manually with a copy of the Matrix SCADA runtime engine. This may be more useful for personal use and if you wish to experiment or store multiple copies of your program: without bundling a fresh copy of the Matrix SCADA runtime engine with every version of your program.		**Alternatively, you can leave this option unchecked, and be provided simply with a single ".mscada" program file. This file can be then run manually with a copy of the Matrix SCADA runtime engine. This may be more useful for personal use and if you wish to experiment or store multiple copies of your program: without bundling a fresh copy of the Matrix SCADA runtime engine with every version of your program.


	===Components tab===		===Components tab===

	This allows you to choose which components will be invisible in the deployed runtime application.		This allows you to choose which components will be invisible in the deployed runtime application.


	===Resources tab===		===Resources tab===

	This allows you to embed resources with your project, in order to make complex systems even more portable.		This allows you to embed resources with your project, in order to make complex systems even more portable.