Support:Howto:Application Binding - Revision history

Wolfgang at 12:37, 25 October 2017

2017-10-25T12:37:02Z

← Older revision		Revision as of 12:37, 25 October 2017
Line 5:		Line 5:
	* Basic Handling of [[Guiliani:GSE\|GSE]]		* Basic Handling of [[Guiliani:GSE\|GSE]]
	=== Prerequisites ===		=== Prerequisites ===
	* Any Installed SDK: [[Downloads:Desktop\|Desktop]] or [[Downloads:~~Boards~~\|~~Board~~]] based		* Any Installed SDK: [[Downloads:Desktop\|Desktop]] or [[Downloads:EvalKits\|EvalKit]] based
	* Installed [https://cmake.org CMake] Version 3.0 or higher		* Installed [https://cmake.org CMake] Version 3.0 or higher
	* IDE matching the used SDK		* IDE matching the used SDK

Patrik: Grammar

2017-01-31T16:12:54Z

Grammar

← Older revision		Revision as of 16:12, 31 January 2017
Line 111:		Line 111:

	=== Using CMake to create your IDE project ===		=== Using CMake to create your IDE project ===
	Startup CMake. Set ''Path to SDK/projects/cmake'' as ''source code path''. The Binary folder hosts the generated project. Enter a folder of your choice and press configure.You will now see a dialog where you can choose your IDE. After selecting the IDE press ''Finish''. In the main window it is needed to set the path to your application as ''GSE_ROOT_PATH_STREAMRUNTIME'' and your application's executable name in ''GSE_STREAMRUNTIME_APPNAME''. Finally, Press ''Generate''.		Startup CMake GUI. Set ''Path to SDK/projects/cmake'' as ''source code path''. The Binary folder hosts the generated project. Enter a folder of your choice and press configure.You will now see a dialog where you can choose your IDE. After selecting the IDE press ''Finish''. In the main window, it is needed to set the path to your application as ''GSE_ROOT_PATH_STREAMRUNTIME'' and your application's executable name in ''GSE_STREAMRUNTIME_APPNAME''. Finally, Press ''Generate''.

	=== Implement CallApplicationAPI ===		=== Implement CallApplicationAPI ===

Patrik: /* Configure CallApplicationAPI in GSE */

2017-01-31T08:17:37Z

Configure CallApplicationAPI in GSE

← Older revision		Revision as of 08:17, 31 January 2017
Line 95:		Line 95:

	=== Configure CallApplicationAPI in GSE ===		=== Configure CallApplicationAPI in GSE ===
	First add a new Button two a dialog of you project. You may want to change the text of the button to i.e. ''Divide by two''. This can be done by unfolding ''StandardText'' and write your text into the ''Text'' Attribute.		First, add a new Button two a dialog of you project. You may want to change the text of the button to i.e. ''Divide by two''. This can be done by unfolding ''StandardText'' and write your text into the ''Text'' Attribute.

	To use the CallApplicationAPI unfold ''GUICommand'' and change ''CommandClassID'' to ''CMD_CALLAPPLICATIONAPI''. You will see that the Attributes ''ApplicationAPI'' and ''Parameter'' appeared.		To use the CallApplicationAPI unfold ''GUICommand'' and change ''CommandClassID'' to ''CMD_CALLAPPLICATIONAPI''. You will see that the Attributes ''ApplicationAPI'' and ''Parameter'' appeared.

	Enter attribute ''ApplicationAPI'' to "divide" and ''Parameter'' to ''2''.		Enter attribute ''ApplicationAPI'' to "divide" and ''Parameter'' to ''2''.

			[[File:Screeen CallApplicationAPI1.png\|Parameterizing CallApplicationAPI]]

	=== Update generated sources ===		=== Update generated sources ===

Patrik: Added screenshot to Datapool part

2017-01-31T08:02:52Z

Added screenshot to Datapool part

← Older revision		Revision as of 08:02, 31 January 2017
Line 73:		Line 73:
	\|-		\|-
	\| MinAngle		\| MinAngle
	\| 45		\| -45
	\|-		\|-
	\| MaxAngle		\| MaxAngle
Line 81:		Line 81:
	\| 200		\| 200
	\|}		\|}
			[[File:Screen DataPool1.png\|Example layout]]
	=== Manage Datapool ===		=== Manage Datapool ===
	Using the menu item "Resources->Manage datapool" it is possible to bind the control to a datapool entry. First we add a new Entry. You might change the name and add a description here. Now add the previously created controls as observers and close the dialog.		Using the menu item "Resources->Manage datapool" it is possible to bind the control to a datapool entry. First we add a new Entry. You might change the name and add a description here. Now add the previously created controls as observers and close the dialog.
			[[File:Screen DataPool Window.png\|Manage Data Pool window]]

	=== See the effect ===		=== See the effect ===

Patrik: Typos/Grammar

2017-01-30T15:07:49Z

Typos/Grammar

← Older revision		Revision as of 15:07, 30 January 2017
Line 12:		Line 12:
	[[File:Guiliani Event Flow.png\|800px\|Guiliani Event Flow]]		[[File:Guiliani Event Flow.png\|800px\|Guiliani Event Flow]]

	The most common way the Guiliani Event flow is triggered is a user interaction, like a touch on the display. The Guiliani Input device will be triggered or will poll a device driver and generate a GUIEvent which will then processed by the Event handler. That will forward it to affected controls. If the control shall interact with other controls or the application, it will queue a command or interacts with the ~~datapool~~. Both methods are ~~describe~~ later. The control draws itself after that by calling the Graphics Wrapper which will handle the platform independent graphics library. The customer application can also queue commands or set values to the ~~datapool~~.		The most common way the Guiliani Event flow is triggered is a user interaction, like a touch on the display. The Guiliani Input device will be triggered or will poll a device driver and generate a GUIEvent which will then processed by the Event handler. That will forward it to affected controls. If the control shall interact with other controls or the application, it will queue a command or interacts with the Datapool. Both methods are described later. The control draws itself after that by calling the Graphics Wrapper which will handle the platform independent graphics library. The customer application can also queue commands or set values to the Datapool.

	=== ~~DataPool~~ ===		=== Datapool ===
	The ~~datapool~~ can be understood as a kind of database, which is easy-to use. Controls can observe from or set values to the data pool. The application can set to or get from values using the ~~datapool~~ asynchronously. The Datapool can be used for fast changing values, due to the low execution time and low latency.		The Datapool can be understood as a kind of database, which is easy-to-use. Controls can observe from or set values to the data pool. The application can set to or get from values using the Datapool asynchronously. The Datapool can be used for fast changing values, due to the low execution time and low latency.

	=== Commands ===		=== Commands ===
Line 43:		Line 43:
	[[File:CustomExtensions Dependencies.png\|600px\|Custom Extensions - Dependencies]]		[[File:CustomExtensions Dependencies.png\|600px\|Custom Extensions - Dependencies]]

	The Application normally consists of the Guiliani library, user code and custom extensions code. GSE consists of a GSE library, Guiliani and the same sources of Custom Extensions as the application.		The Application normally consists of the Guiliani library, user code, and custom extensions code. GSE consists of a GSE library, Guiliani and the same sources of Custom Extensions as the application.
	For further information on events please read our [https://www.guiliani.de/mediawiki/downloads/Guiliani_doc_2.0/index.html documentation].		For further information on events please read our [https://www.guiliani.de/mediawiki/downloads/Guiliani_doc_2.0/index.html documentation].

Patrik: Typos

2017-01-30T12:19:40Z

Typos

← Older revision		Revision as of 12:19, 30 January 2017
Line 145:		Line 145:
	Open GSE and your project. Choose Custom Extensions->Create Custom Extensions. Choose Add Control. Enter name '''MyControl''' and press Generate. Close GSE.		Open GSE and your project. Choose Custom Extensions->Create Custom Extensions. Choose Add Control. Enter name '''MyControl''' and press Generate. Close GSE.

	It’s needed to add the newly created sources to your IDE's project. So we need to regenerate the project using ~~cmake~~. Just Press Configure and Generate.		It’s needed to add the newly created sources to your IDE's project. So we need to regenerate the project using CMake. Just Press Configure and Generate.

	You will now find MyControl.h and MyControl.cpp in the project.		You will now find MyControl.h and MyControl.cpp in the project.

Patrik: Corrected Typos

2017-01-30T12:17:35Z

Corrected Typos

← Older revision		Revision as of 12:17, 30 January 2017
Line 89:		Line 89:

	== CallApplicationAPI ==		== CallApplicationAPI ==
	To demonstrate the CallApplicationAPI this Howto will let you add a button which will divide the DataPool value by two. As described above, the CallApplicationAPI is a ~~builtin~~ command which defines a Text API to do application binding. It requires two Strings:		To demonstrate the CallApplicationAPI this Howto will let you add a button which will divide the DataPool value by two. As described above, the CallApplicationAPI is a built-in command which defines a Text API to do application binding. It requires two Strings:
	* ApplicationAPI: Here you can define an API name		* ApplicationAPI: Here you can define an API name
	* Parameter: A ~~paramter~~ to this API		* Parameter: A parameter to this API

	=== Configure CallApplicationAPI in GSE ===		=== Configure CallApplicationAPI in GSE ===
Line 105:		Line 105:
	Since '''Guiliani 2.1''' GSE can copy these files automatically when checking ''Overwrite Headers in StreamRuntime''.		Since '''Guiliani 2.1''' GSE can copy these files automatically when checking ''Overwrite Headers in StreamRuntime''.

	In '''Guiliani 2.0 or earlier''' it is needed to copy all headers from either the directory ''temp'' when you were ~~simualting~~ the application or the directory you exported to. Copy all header files from there to ''your application/include/GUIConfig''.		In '''Guiliani 2.0 or earlier''' it is needed to copy all headers from either the directory ''temp'' when you were simulating the application or the directory you exported to. Copy all header files from there to ''your application/include/GUIConfig''.

	=== Using CMake to create your IDE project ===		=== Using CMake to create your IDE project ===
Line 137:		Line 137:
	</syntaxhighlight>		</syntaxhighlight>

	After recompiling, start the GSE from the bin directory, load the project and run the simulation. If you now move the sliders and press the button, you will see that the value ~~halfs~~ each time you press the button.		After recompiling, start the GSE from the bin directory, load the project and run the simulation. If you now move the sliders and press the button, you will see that the value halves each time you press the button.

	== Custom Extensions ==		== Custom Extensions ==
Line 160:		Line 160:

	==== MyControl.cpp ====		==== MyControl.cpp ====
	Now add the graphical ~~represantation~~ to the control. The following first sets the foreground color to semi-transparent full red (Line 3). Line 4 draws a filled ~~rect~~ over the whole area of the control.		Now add the graphical representation to the control. The following first sets the foreground color to semi-transparent full red (Line 3). Line 4 draws a filled rectangle over the whole area of the control.

	<syntaxhighlight lang="c++" line>		<syntaxhighlight lang="c++" line>
Line 180:		Line 180:
	</syntaxhighlight>		</syntaxhighlight>

	=== Test the ~~reults~~ ===		=== Test the results ===
	Compile the whole project. After starting GSE and Loading your project you see a new Control MyControl. Add it to your dialog. You see the intended red area.		Compile the whole project. After starting GSE and Loading your project you see a new Control MyControl. Add it to your dialog. You see the intended red area.

Line 201:		Line 201:


	The DoDraw-Method needs also to be updated to ~~calciulate~~ the color out of the ~~attibutes~~ ''MyColor'' and ''MyAlpha'':		The DoDraw-Method needs also to be updated to calculate the color out of the attributes ''MyColor'' and ''MyAlpha'':
	<syntaxhighlight lang="c++" line>		<syntaxhighlight lang="c++" line>
	eC_Bool MyControl::DoDraw()		eC_Bool MyControl::DoDraw()

Patrik: Resized Guiliani Event Flow in Application Binding

2017-01-30T08:33:59Z

Resized Guiliani Event Flow in Application Binding

← Older revision		Revision as of 08:33, 30 January 2017
Line 10:		Line 10:

	=== Guiliani Event Flow ===		=== Guiliani Event Flow ===
	[[File:Guiliani Event Flow.png\|~~600px~~\|Guiliani Event Flow]]		[[File:Guiliani Event Flow.png\|800px\|Guiliani Event Flow]]

	The most common way the Guiliani Event flow is triggered is a user interaction, like a touch on the display. The Guiliani Input device will be triggered or will poll a device driver and generate a GUIEvent which will then processed by the Event handler. That will forward it to affected controls. If the control shall interact with other controls or the application, it will queue a command or interacts with the datapool. Both methods are describe later. The control draws itself after that by calling the Graphics Wrapper which will handle the platform independent graphics library. The customer application can also queue commands or set values to the datapool.		The most common way the Guiliani Event flow is triggered is a user interaction, like a touch on the display. The Guiliani Input device will be triggered or will poll a device driver and generate a GUIEvent which will then processed by the Event handler. That will forward it to affected controls. If the control shall interact with other controls or the application, it will queue a command or interacts with the datapool. Both methods are describe later. The control draws itself after that by calling the Graphics Wrapper which will handle the platform independent graphics library. The customer application can also queue commands or set values to the datapool.

Patrik: /* Final test */

2017-01-27T16:19:29Z

Final test

← Older revision		Revision as of 16:19, 27 January 2017
Line 258:		Line 258:
	After recompilation open your project in GSE. Now you can see the new defined attributes of the MyControl. Felle free to play with the values.		After recompilation open your project in GSE. Now you can see the new defined attributes of the MyControl. Felle free to play with the values.

	For further information on application programming using Guiliani please read our [~~documentation~~ https://www.guiliani.de/mediawiki/downloads/Guiliani_doc_2.0/index.html].		For further information on application programming using Guiliani please read our [https://www.guiliani.de/mediawiki/downloads/Guiliani_doc_2.0/index.html documentation].

Patrik at 16:18, 27 January 2017

2017-01-27T16:18:32Z

Show changes