GUI Editor-GUICode Editor/en - Versionsgeschichte

Cg: /* Modeless (Full) GUI Blocks */

2026-03-08T00:20:19Z

Modeless (Full) GUI Blocks

← Nächstältere Version		Version vom 8. März 2026, 00:20 Uhr
Zeile 70:		Zeile 70:
	Complex interaction with and verification by the network is possible, however they are a bit more complicated to define than the simple modal UI actions.		Complex interaction with and verification by the network is possible, however they are a bit more complicated to define than the simple modal UI actions.

	to be documented		to be documented

	[[Category:Editors]]		[[Category:Editors]]

Cg: /* Modeless (Full) GUI Blocks */

2026-03-08T00:19:58Z

Modeless (Full) GUI Blocks

← Nächstältere Version		Version vom 8. März 2026, 00:19 Uhr
Zeile 70:		Zeile 70:
	Complex interaction with and verification by the network is possible, however they are a bit more complicated to define than the simple modal UI actions.		Complex interaction with and verification by the network is possible, however they are a bit more complicated to define than the simple modal UI actions.

			to be documented


	[[Category:Editors]]		[[Category:Editors]]

Cg: /* Modal vs. Modeless GUI Blocks */

2025-04-11T13:37:11Z

Modal vs. Modeless GUI Blocks

← Nächstältere Version		Version vom 11. April 2025, 13:37 Uhr
Zeile 7:		Zeile 7:
	== Modal vs. Modeless GUI Blocks ==		== Modal vs. Modeless GUI Blocks ==

	So called "''Elementary GUI blocks''" are modal and pop up a dialog-interface when the activity is triggered, and close the window, when either an external close event arrives (at the close input pin) or via user interaction.		So called "''Elementary or Modal GUI blocks''" are modal and pop up a dialog-interface when the activity is triggered, and close the window, when either an external close event arrives (at the close input pin) or via user interaction. Modal GUIs take their inputs from correspondingly named input pins and write values to corresponding output pins.

	The other form of GUI blocks ~~are~~ called "''Compound GUI ~~Blocks~~''". These are modeless (i.e. they do not block execution) and are attached to a compound action block. These are completely controlled by the compound block's activity diagram, and can even show animations or real-time data.		The other form of GUI blocks is called "''Compound or Modeless GUI Block''". These are modeless (i.e. they do not block execution) and are attached to a compound action block. These are completely controlled by the compound block's activity diagram, and can even show animations or real-time data. Modeless GUIs interact by reading/writing values to variables which are defined in the compound actions variable environment.

	<div ID="Example1"> </div>		<div ID="Example1"> </div>

Cg am 11. April 2025 um 13:34 Uhr

2025-04-11T13:34:37Z

← Nächstältere Version		Version vom 11. April 2025, 13:34 Uhr
Zeile 17:		Zeile 17:
	They open up a modal dialog, which blocks other user interaction until the dialog is confirmed (with ok or cancel).		They open up a modal dialog, which blocks other user interaction until the dialog is confirmed (with ok or cancel).

			=== Where do I use this? ===
	These are typically used when multiple values are needed and/or simple yes/no answers are not sufficient.

			These Dialog-like elementary GUI blocks are very useful if the test suite needs additional
			parameters or values from an operator. For example, if there are some measurement values to be entered manually (because you do not have an interface, but need a human to read it).
			Such user interaction is especially useful in semi-automatic testing, where some manual testing/validation is to be integrated into an otherwise automatic test. A concrete example of our own past is a web-site checker, which asked the test-operator questions like "''Please rate the overall design of the page''" or similar.

	=== Example: A Modal Forms Dialog ===		=== Example: A Modal Forms Dialog ===

Cg: /* Where do I use this? */

2025-04-11T13:33:59Z

Where do I use this?

← Nächstältere Version		Version vom 11. April 2025, 13:33 Uhr
Zeile 59:		Zeile 59:
	[[Bild:gui_form_pinData_1.jpg\|600px]]		[[Bild:gui_form_pinData_1.jpg\|600px]]

	=== Where do I use this? ===

			== Modeless (Full) GUI Blocks ==
	These Dialog-like elementary GUI blocks are very useful if the test suite needs additional

	parameters or values from an operator. For example, if there are some measurement values to be entered manually (because you do not have an interface, but need a human to read it).
			These are associated to a compound action and the GUI will be shown as long as the compound action is active.
	Such user interaction is especially useful in semi-automatic testing, where some manual testing/validation is to be integrated into an otherwise automatic test. A concrete example of our own past is a web-site checker, which asked the test-operator questions like "''Please rate the overall design of the page''" or similar.
			Complex interaction with and verification by the network is possible, however they are a bit more complicated to define than the simple modal UI actions.



	[[Category:Editors]]		[[Category:Editors]]

Cg: /* Modal GUI Blocks */

2025-04-11T13:31:41Z

Modal GUI Blocks

← Nächstältere Version		Version vom 11. April 2025, 13:31 Uhr
Zeile 13:		Zeile 13:

	== Modal GUI Blocks ==		== Modal GUI Blocks ==

			So called "Modal" UI actions behave like the other actions found in the "Dialogs" section of the standard library.
			They open up a modal dialog, which blocks other user interaction until the dialog is confirmed (with ok or cancel).

			These are typically used when multiple values are needed and/or simple yes/no answers are not sufficient.

	=== Example: A Modal Forms Dialog ===		=== Example: A Modal Forms Dialog ===

Cg: /* Example: A Modal Forms Dialog */

2025-04-11T13:28:59Z

Example: A Modal Forms Dialog

← Nächstältere Version		Version vom 11. April 2025, 13:28 Uhr
Zeile 22:		Zeile 22:
	[[Bild:Gui_block_schema.jpg]]		[[Bild:Gui_block_schema.jpg]]

	Notice, that some of the input and output pins share a common name. This is only allowed for elementary UI blocks, and specifies that a pin value is used both to fill a value into a UI-component AND to be eventually read out of the UI component and sent to the blocks output pin ~~(for example, to provide an initial value for an input field)~~.		Notice, that some of the input and output pins share a common name. This is only allowed for elementary UI blocks, and specifies that a pin value is used both to fill a value into a UI-component AND to be eventually read out of the UI component and sent to the blocks output pin.

	Next, navigate to the UI-tab, and click on the UI-editor icon.		Next, navigate to the UI-tab, and click on the UI-editor icon.

Cg am 11. April 2025 um 13:27 Uhr

2025-04-11T13:27:36Z

← Nächstältere Version		Version vom 11. April 2025, 13:27 Uhr
Zeile 12:		Zeile 12:
	<div ID="Example1"> </div>		<div ID="Example1"> </div>

	== ~~Example: A~~ Modal ~~Forms~~ ~~Dialog~~ ==		== Modal GUI Blocks ==

			=== Example: A Modal Forms Dialog ===

	The following example demonstrates how a modal form-dialog using an elementary GUI block can be constructed. The goal is to present a textual list of choices, a radio-button list and a few other checkbox-choices in a modal box, for a user to make a choice and confirm.		The following example demonstrates how a modal form-dialog using an elementary GUI block can be constructed. The goal is to present a textual list of choices, a radio-button list and a few other checkbox-choices in a modal box, for a user to make a choice and confirm.
Zeile 52:		Zeile 54:
	[[Bild:gui_form_pinData_1.jpg\|600px]]		[[Bild:gui_form_pinData_1.jpg\|600px]]

	== Where do I use this? ==		=== Where do I use this? ===

	These Dialog-like elementary GUI blocks are very useful if the test suite needs additional		These Dialog-like elementary GUI blocks are very useful if the test suite needs additional

Cg: /* Introduction */

2025-04-11T13:26:21Z

Introduction

← Nächstältere Version		Version vom 11. April 2025, 13:26 Uhr
Zeile 3:		Zeile 3:
	<!-- Notice that the UI-editor and GUI block elements are only included in the expecco PRO version. -->		<!-- Notice that the UI-editor and GUI block elements are only included in the expecco PRO version. -->

	The most notable difference is in the handling and representation of the models for the UI widget components. Where the Smalltalk version uses ValueHolders as provided by an application class, ~~the~~ expecco ~~framework for GUI-Blocks~~ uses adaptors. These adaptors look like regular value holders towards the widgets, but read and write pin data of the underlying step when accessed. Therefore, it is possible, to let an EditField or a Combobox operate on a pin's input- or output data.		The most notable difference is in the handling and representation of the models for the UI widget components. Where the Smalltalk version uses ValueHolders as provided by an application class, expecco uses adaptors. These adaptors look like regular value holders towards the widgets, but read and write pin data or variables of the underlying step when accessed. Therefore, it is possible, to let an EditField or a Combobox operate on a pin's input- or output data.

	== Modal vs. Modeless GUI Blocks ==		== Modal vs. Modeless GUI Blocks ==

Cg am 27. Dezember 2019 um 14:05 Uhr

2019-12-27T14:05:07Z

← Nächstältere Version		Version vom 27. Dezember 2019, 14:05 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	The UI-Editor provided by expecco is a modified variant of the Smalltalk/X UIPainter component. This is described in detail in [http://live.exept.de/doc/online/english/tools/uipainter/TOP.html "Using the UI-Painter].		The UI-Editor provided by expecco is a modified variant of the Smalltalk/X UIPainter component. This is described in detail in [http://live.exept.de/doc/online/english/tools/uipainter/TOP.html "Using the UI-Painter].
	Notice that the UI-editor and GUI block elements are only included in the expecco PRO version.		<!-- Notice that the UI-editor and GUI block elements are only included in the expecco PRO version. -->

	The most notable difference is in the handling and representation of the models for the UI widget components. Where the Smalltalk version uses ValueHolders as provided by an application class, the expecco framework for GUI-Blocks uses adaptors. These adaptors look like regular value holders towards the widgets, but read and write pin data of the underlying step when accessed. Therefore, it is possible, to let an EditField or a Combobox operate on a pin's input- or output data.		The most notable difference is in the handling and representation of the models for the UI widget components. Where the Smalltalk version uses ValueHolders as provided by an application class, the expecco framework for GUI-Blocks uses adaptors. These adaptors look like regular value holders towards the widgets, but read and write pin data of the underlying step when accessed. Therefore, it is possible, to let an EditField or a Combobox operate on a pin's input- or output data.