Fundamental Visual Prolog - GUI - Revision history

Thomas Linder Puls: Delete repeated paragraph

2023-02-14T08:56:42Z

Delete repeated paragraph

← Older revision		Revision as of 10:56, 14 February 2023
Line 112:		Line 112:

	Please note that in dialogs, there is another property called the ''default push button'' which can be set separately from the visit order. An event for the button that has been set to be the ''default push button'' will be triggered on pressing the ENTER key irrespective of which control had the ''input focus''. Usually, the default push button is set to be the OK button.		Please note that in dialogs, there is another property called the ''default push button'' which can be set separately from the visit order. An event for the button that has been set to be the ''default push button'' will be triggered on pressing the ENTER key irrespective of which control had the ''input focus''. Usually, the default push button is set to be the OK button.

	When you right-click on the dialog, you can set the overall dialog attributes using the following dialog. If you notice, the Type of the dialog is set to Modal. The term ''modal'' reflects the fact that whenever the dialog is presented to the user, the GUI would stop responding to other parts of the program, when the dialog is visible. Only when the dialog is disposed off by the user (by pressing the OK or Cancel button) the GUI will become responsive once again to all GUI activity.

	When you click on the dialog, you can set the overall dialog properties on the properties panel. If you notice, the Type of the dialog is set to Modal. The term modal reflects the fact that whenever the dialog is presented to the user, the GUI would stop responding to other parts of the program, when the dialog is visible. Only when the dialog is disposed off by the user (by pressing the OK or Cancel button) the GUI will become responsive once again to all GUI activity.		When you click on the dialog, you can set the overall dialog properties on the properties panel. If you notice, the Type of the dialog is set to Modal. The term modal reflects the fact that whenever the dialog is presented to the user, the GUI would stop responding to other parts of the program, when the dialog is visible. Only when the dialog is disposed off by the user (by pressing the OK or Cancel button) the GUI will become responsive once again to all GUI activity.

Kasper B H Petersen: /* Understanding What we have Done So Far */

2021-10-07T11:38:33Z

Understanding What we have Done So Far

← Older revision		Revision as of 13:38, 7 October 2021
Line 351:		Line 351:
	The reason for this error is because the onQueryAncestorOf predicate is expecting this globally accessible predicate called tryGetName from the module ancestorDialog.pro. But we haven't written that yet! Let us now get down to rectifying that error.		The reason for this error is because the onQueryAncestorOf predicate is expecting this globally accessible predicate called tryGetName from the module ancestorDialog.pro. But we haven't written that yet! Let us now get down to rectifying that error.

	This predicate is defined within one module, but called from another module. Hence we need to ensure that the declaration is kept not in the .pro ~~l parts of the program~~. The class declaration file of a module (extension .cl) is one such place. Therefore, let us now open ancestorDialog.cl and insert the following piece of code. (It is a declaration statin called tryGetName is implemented within the module, and that predicate can be called from other modules too.)		This predicate is defined within one module, but called from another module. Hence we need to ensure that the declaration is kept not in the .pro. The class declaration file of a module (extension .cl) is one such place. Therefore, let us now open ancestorDialog.cl and insert the following piece of code. (It is a declaration statin called tryGetName is implemented within the module, and that predicate can be called from other modules too.)

	<vip>predicates		<vip>predicates

Thomas Linder Puls: /* Creating a Modal Dialog */ casing

2016-11-02T12:31:47Z

Creating a Modal Dialog: casing

← Older revision		Revision as of 14:31, 2 November 2016
Line 65:		Line 65:
	:[[Image:FundamentalVisualPrologGui02.PNG]]		:[[Image:FundamentalVisualPrologGui02.PNG]]

	The Create Project Item dialog would be presented. Ensure that Dialog is selected from the left hand side and on the right hand side enter the ~~AncestorDialog~~.		The Create Project Item dialog would be presented. Ensure that Dialog is selected from the left hand side and on the right hand side enter the '''ancestorDialog'''.

	:[[Image:FundamentalVisualPrologGui03.PNG]]		:[[Image:FundamentalVisualPrologGui03.PNG]]

Thomas Linder Puls: /* Modifying the Toolbar */ menu

2016-11-02T12:25:33Z

Modifying the Toolbar: menu

← Older revision		Revision as of 14:25, 2 November 2016
Line 173:		Line 173:
	:[[Image:FundamentalVisualPrologGui28.png]]		:[[Image:FundamentalVisualPrologGui28.png]]

	We shall now map the Undo, Redo and the Help buttons to represent the following menu items: Query\|Father''..''., Query\|Grandfather... and Query\|Ancestor of ...		We shall now map the Undo, Redo and the Help buttons to represent the following menu items: '''Query -> Father...''', '''Query -> Grandfather...''' and '''Query -> Ancestor of ...'''

	(As noted before, we would not be changing the images of those buttons in this tutorial.)		(As noted before, we would not be changing the images of those buttons in this tutorial.)

Thomas Linder Puls: /* Modifying the Menu */ menu

2016-11-02T12:23:37Z

Modifying the Menu: menu

← Older revision		Revision as of 14:23, 2 November 2016
Line 147:		Line 147:
	Note that by convention an ellipsis (three dots) is used at the end of those menu items which will yield another dialog before any work is carried out. In the above example, &Father and &Grandfather menu items will not have the ellipsis. But the &Ancestor of ... entry will have the ellipsis, because on invoking that menu item, a dialog would open up before any activity gets done.		Note that by convention an ellipsis (three dots) is used at the end of those menu items which will yield another dialog before any work is carried out. In the above example, &Father and &Grandfather menu items will not have the ellipsis. But the &Ancestor of ... entry will have the ellipsis, because on invoking that menu item, a dialog would open up before any activity gets done.

	One last step is remaining in the editing of the TaskWindow menu. By default, when the IDE creates the menu, the File\|Open menu is disabled. You would have to locate that menu item, and enable it by removing the checkmark from that menu item's Menu Item Attributes dialog, as seen below:		One last step is remaining in the editing of the TaskWindow menu. By default, when the IDE creates the menu, the '''File -> Open''' menu is disabled. You would have to locate that menu item, and enable it by removing the checkmark from that menu item's Menu Item Attributes dialog, as seen below:

	:[[Image:FundamentalVisualPrologGui16.png]]		:[[Image:FundamentalVisualPrologGui16.png]]

Thomas Linder Puls: classInfo/Examples install

2014-11-24T14:33:35Z

classInfo/Examples install

← Older revision		Revision as of 16:33, 24 November 2014
Line 3:		Line 3:
	In this tutorial, we shall add a simple [[wikipedia:Graphical_User_Interface\|Graphical User Interface]] (GUI) front end to the family project, which was developed in an earlier tutorial. We shall learn to do create and edit most of the GUI components of a simple Windows program directly within the Visual Prolog IDE (Integrated Development Environment). We shall learn a bit about handling of GUI events (like clicking a button on a specific part of the GUI, etc.), and how they work within a Visual Prolog program. We shall also learn about modal dialogs with two examples: one, which is inbuilt by the Windows operating system, and one, which we shall build for ourselves for our program.		In this tutorial, we shall add a simple [[wikipedia:Graphical_User_Interface\|Graphical User Interface]] (GUI) front end to the family project, which was developed in an earlier tutorial. We shall learn to do create and edit most of the GUI components of a simple Windows program directly within the Visual Prolog IDE (Integrated Development Environment). We shall learn a bit about handling of GUI events (like clicking a button on a specific part of the GUI, etc.), and how they work within a Visual Prolog program. We shall also learn about modal dialogs with two examples: one, which is inbuilt by the Windows operating system, and one, which we shall build for ourselves for our program.

	~~'''Download'''~~ source files of the example project used in this tutorial:		The source files of the example project used in this tutorial are part of the installable examples (in the IDE: '''Help -> Install Examples...''').

	* Visual Prolog 7.4 and 7.3 install examples in the IDE:
	*:'''Help -> Install Examples...'''
	* [http://download.pdc.dk/vip/72/tutorial_examples/fundamental_visual_prolog/family2.zip Visual Prolog 7.2 version].
	* [http://download.pdc.dk/vip/71/examples/tutorial_examples/fundamental_visual_prolog/family2.zip Visual Prolog 7.1 version].


	==Introduction to a GUI==		==Introduction to a GUI==
Line 363:		Line 357:
	trygetName : (window Parent) -> string Name determ.</vip>		trygetName : (window Parent) -> string Name determ.</vip>

	In ancestorDialog.pro, let us now insert the core logic relevant to that module. Just the way we did for Taskwindow.pro, it is inserted just after the following ~~line~~:		In ancestorDialog.pro, let us now insert the core logic relevant to that module. Just the way we did for Taskwindow.pro, it is inserted just after the following lines:

	<vip>~~classInfo(className~~, ~~classVersion).~~</vip>		<vip>implement ancestorDialog inherits dialog
			open core, vpiDomains</vip>

	Here is the code to be inserted:		Here is the code to be inserted:

Thomas Linder Puls: /* Starting a GUI Project */ MDI

2013-12-03T14:49:09Z

Starting a GUI Project: MDI

← Older revision		Revision as of 16:49, 3 December 2013
Line 47:		Line 47:
	==Starting a GUI Project==		==Starting a GUI Project==

	Let us start at the very beginning (a very good place to start!). When we create the project in the Visual Prolog IDE, make sure that the '''Project Kind''' is set to '''GUI application'''.		Let us start at the very beginning (a very good place to start!). When we create the project in the Visual Prolog IDE, make sure that the '''Project Kind''' is set to '''GUI application''' in '''MDI mode'''.

	The IDE then creates the initial set of modules required to handle the GUI along with the GUI component resources: the main menu, one top toolbar, one bottom status bar, the About dialog and the main Task Window of the program.		The IDE then creates the initial set of modules required to handle the GUI along with the GUI component resources: the main menu, one top toolbar, one bottom status bar, the About dialog and the main Task Window of the program.

Gukalov: /* Creating a Modal Dialog */

2013-09-16T15:36:34Z

Creating a Modal Dialog

← Older revision		Revision as of 17:36, 16 September 2013
Line 67:		Line 67:
	==Creating a Modal Dialog==		==Creating a Modal Dialog==

	Now we shall add another GUI component that we would need later on in our program. It is a dialog box which will be used to feed the name of a person to the program for the program to process. In the Project tree (where all the modules and resources are listed in a clearly laid out tree menu), right click on the Task Window and from the context menu, select New in ~~Existing~~ Package...		Now we shall add another GUI component that we would need later on in our program. It is a dialog box which will be used to feed the name of a person to the program for the program to process. In the Project tree (where all the modules and resources are listed in a clearly laid out tree menu), right click on the Task Window and from the context menu, select New in New Package...

	:[[Image:FundamentalVisualPrologGui02.PNG]]		:[[Image:FundamentalVisualPrologGui02.PNG]]

Gukalov: /* Encapsulating the Interactive Code */

2013-09-16T15:34:36Z

Encapsulating the Interactive Code

← Older revision		Revision as of 17:34, 16 September 2013
Line 305:		Line 305:
	Now you should go back to the Dialog and Window Expert, and ensure that the listeners for the Query\|Father, Query\|Grandfather and Query\|Ancestor of ... menu items are also set as shown below:		Now you should go back to the Dialog and Window Expert, and ensure that the listeners for the Query\|Father, Query\|Grandfather and Query\|Ancestor of ... menu items are also set as shown below:

	:[[Image:FundamentalVisualPrologGui22.~~jpg~~]]		:[[Image:FundamentalVisualPrologGui22.png]]

	Now for the Query\|Father menu item, add the following clause body before the default clause body inserted automatically by Visual Prolog:		Now for the Query\|Father menu item, add the following clause body before the default clause body inserted automatically by Visual Prolog:

Gukalov: /* Encapsulating the Interactive Code */

2013-09-16T12:29:20Z

Encapsulating the Interactive Code

← Older revision		Revision as of 14:29, 16 September 2013
Line 258:		Line 258:
	The Dialog and Window Expert (shown below) helps you set default listeners and responders for controls (interactive GUI components) of a particular window or a dialog. The blue filled circle indicates that there is no listener or responder for the indicated control. The green tick-mark indicates that a listener or responder is present.		The Dialog and Window Expert (shown below) helps you set default listeners and responders for controls (interactive GUI components) of a particular window or a dialog. The blue filled circle indicates that there is no listener or responder for the indicated control. The green tick-mark indicates that a listener or responder is present.

	:[[Image:FundamentalVisualPrologGui18.~~jpg~~]]		:[[Image:FundamentalVisualPrologGui18.png]]

	Using the above dialog, ensure that an event handler is set for the menu item represented by the constant ''id_file_open''.		Using the above dialog, ensure that an event handler is set for the menu item represented by the constant ''id_file_open''.