Ide/Environment Overview - Revision history

Troels Anker Jørgensen: /* Building */

2020-01-06T13:11:28Z

Building

← Older revision		Revision as of 15:11, 6 January 2020
Line 49:		Line 49:
	==Building==		==Building==

	~~Before~~ we make any modifications, we will build (i.e. compile and link) the project. In the '''Build''' menu you find commands for building, compiling and executing the project.		When you create the project, it auto builds the first time.

			However, before we make any modifications, we will try to build (i.e. compile and link) the project manually. In the '''Build''' menu you find commands for building, compiling and executing the project.

	If you choose '''Execute''' the project is first build, so that it is an up to date version you execute. Therefore I will choose '''Execute'''.		If you choose '''Execute''' the project is first build, so that it is an up to date version you execute. Therefore I will choose '''Execute'''.

Troels Anker Jørgensen: /* Creation */

2020-01-06T13:06:31Z

Creation

← Older revision		Revision as of 15:06, 6 January 2020
Line 37:		Line 37:
	For the moment you do not need to consider the remaining tabs and options.		For the moment you do not need to consider the remaining tabs and options.

	Now create the project by pressing '''OK'''.		Now create the project by pressing '''Finish'''.

	The IDE will now look something like this:		The IDE will now look something like this:

Thomas Linder Puls: /* Development */ missing word

2017-06-02T12:30:48Z

Development: missing word

← Older revision		Revision as of 14:30, 2 June 2017
Line 151:		Line 151:
	[[Image:tut01_errorS.png\|Error Wondow]]		[[Image:tut01_errorS.png\|Error Wondow]]

	We will consider what the error message actually means. Instead you should try to double-click on the error message. You will notice that the editor gets focus again and that the caret points exactly to the fail we inserted.		We will not consider what the error message actually means. Instead you should try to double-click on the error message. You will notice that the editor gets focus again and that the caret points exactly to the fail we inserted.

	Reestablish the code without the fail and build the project again.		Reestablish the code without the fail and build the project again.

Thomas Linder Puls: classInfo

2014-11-24T14:31:45Z

classInfo

← Older revision		Revision as of 16:31, 24 November 2014
Line 87:		Line 87:
	[[Image:tut01_projectWindow2.png\|Project Tree]]		[[Image:tut01_projectWindow2.png\|Project Tree]]

	This sub-tree shows that the file '''main.cl''' contains a class called '''main''', which contains ~~two predicates called classinfo and~~ run ~~respectively~~. Predicates are subroutines, but they will not be considered further in this tutorial.		This sub-tree shows that the file '''main.cl''' contains a class called '''main''', which contains the declaration of the predicate <vp>run</vp>. Predicates are subroutines, but they will not be considered further in this tutorial.

	If we collapse this node again and instead expand the '''TaskWindow''' node, you will see this tree:		If we collapse this node again and instead expand the '''TaskWindow''' node, you will see this tree:

Gukalov: /* Debugging */

2013-09-18T15:26:06Z

Debugging

← Older revision		Revision as of 17:26, 18 September 2013
Line 214:		Line 214:
	[[Image:tut01_runStack.png\|Run Stack]]		[[Image:tut01_runStack.png\|Run Stack]]

	contains a "picture" of the run stack. ~~Exactly what you see depends on your settings in '''Tools -> Options... -> Debugger'''.~~ In principle, the run stack contains a number of lines corresponding to calls that has been made. However, optimization (so called last call optimization) might have removed some entries.		contains a "picture" of the run stack. In principle, the run stack contains a number of lines corresponding to calls that has been made. However, optimization (so called last call optimization) might have removed some entries.

	The run stack not only shows the calls, it also shows trap points and backtrack points, these is described in a later tutorial and there I also describe the run stack window in more details.		The run stack not only shows the calls, it also shows trap points and backtrack points, these is described in a later tutorial and there I also describe the run stack window in more details.

Gukalov: /* Development */

2013-09-18T14:58:53Z

Development

← Older revision		Revision as of 16:58, 18 September 2013
Line 169:		Line 169:
	[[Image:tut01_dialogEditorAbout2.png\|Dialog Editor: About Dialog with new button]]		[[Image:tut01_dialogEditorAbout2.png\|Dialog Editor: About Dialog with new button]]

	Now we want to do something whenever the button is pressed~~. To do this we will open the '''Code Expert'''~~: ~~Right click the dialog and select '''Code Expert'''. The code expert will open and I have located my button.~~		Now we want to do something whenever the button is pressed:

	The blue dot indicates that the control is not handled. The IDE has suggested the name onPushButton for the handling predicate. We will choose '''Add''' to add this predicate to our code and to bind it to this control.		[[Image:Tut01_dialogEditorAboutClick.png]]

	If you double-click the line corresponding to the ~~control in the code expert~~, an editor will open positioned at the newly inserted code.
			The IDE has suggested the name onPushButton for the handling predicate. If you double-click the line corresponding to the event, an editor will open positioned at the newly inserted code.

	We will change the button text when the button is pressed. To do this we modify the code as follows:		We will change the button text when the button is pressed. To do this we modify the code as follows:

Gukalov: /* Creation */

2013-09-18T13:40:04Z

Creation

← Older revision		Revision as of 15:40, 18 September 2013
Line 41:		Line 41:
	The IDE will now look something like this:		The IDE will now look something like this:

	[[Image:tut01_totalS~~.png]] [[Image:tut01_message~~.png]]		[[Image:tut01_totalS.png]]


	~~To the left you~~ have the '''Project Window''', which contains information about the entities in your ~~project. Right now there is not very much information, but once we compile the project information will be added. We will explore this window more when we have compiled the~~ project.		You have the '''Project Window''', which contains information about the entities in your project.
			You have the '''Messages Window''', which will contain various status and progress messages.
	~~To the right/bottom you~~ have the '''Messages Window''', which will contain various status and progress messages.

	==Building==		==Building==

Thomas Linder Puls: references

2013-02-12T10:01:34Z

references

← Older revision		Revision as of 12:01, 12 February 2013
Line 251:		Line 251:

	your projects. It contains a number of tools, editor and wizards that will help you in your tasks.		your projects. It contains a number of tools, editor and wizards that will help you in your tasks.

	~~==References==~~

	* {{ide\|Key Bindings\|Key Bindings}}

	[[ru:Среда_разработки]]		[[ru:Среда_разработки]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Thomas Linder Puls: navbar

2013-02-12T10:00:53Z

navbar

← Older revision		Revision as of 12:00, 12 February 2013
Line 1:		Line 1:
			{{ideNavbar\|Environment Overview}}

	In this tutorial I will give an overview of the Integrated Development Environment (IDE).The IDE is used to create, develop and maintain your Visual Prolog projects.		In this tutorial I will give an overview of the Integrated Development Environment (IDE).The IDE is used to create, develop and maintain your Visual Prolog projects.

Line 256:		Line 258:
	[[ru:Среда_разработки]]		[[ru:Среда_разработки]]
	[[Category:Tutorials]]		[[Category:Tutorials]]
	~~[[Category:IDE]]~~

Thomas Linder Puls: /* References */ link

2013-02-12T09:59:14Z

References: link

← Older revision		Revision as of 11:59, 12 February 2013
Line 252:		Line 252:
	==References==		==References==

	*~~[[IDE~~ Key Bindings]]		* {{ide\|Key Bindings\|Key Bindings}}

	[[ru:Среда_разработки]]		[[ru:Среда_разработки]]
	[[Category:Tutorials]]		[[Category:Tutorials]]
	[[Category:IDE]]		[[Category:IDE]]