Visual Prolog 7.4 Upgrade Notes - Revision history

Thomas Linder Puls: Category

2018-05-14T10:54:42Z

Thomas Linder Puls: short update

2012-11-27T15:18:34Z

short update

← Older revision		Revision as of 17:18, 27 November 2012
Line 14:		Line 14:

	Notice that you should simply delete include directives to PFC files which cannot be found: proper include directives will (normally) be inserted automatically.		Notice that you should simply delete include directives to PFC files which cannot be found: proper include directives will (normally) be inserted automatically.

			Many projects will only require:
			* Accept to remove all unexisting packages
			* Accept to add required packages
			* Delete all include directives for files that does not exist
			* Accept to add include directives


	== Manual updates ==		== Manual updates ==

Thomas Linder Puls: release

2012-11-24T19:46:48Z

release

← Older revision		Revision as of 21:46, 24 November 2012
Line 1:		Line 1:
	~~{{Preliminary Documentation}}~~

	This document describes how to upgrade Visual Prolog 7.3 projects to Visual Prolog 7.4, for older projects you should also read [[Visual Prolog 7.3 Upgrade Notes]].		This document describes how to upgrade Visual Prolog 7.3 projects to Visual Prolog 7.4, for older projects you should also read [[Visual Prolog 7.3 Upgrade Notes]].

Thomas Linder Puls: the_DOMDocument

2012-11-19T15:37:11Z

the_DOMDocument

← Older revision		Revision as of 17:37, 19 November 2012
Line 112:		Line 112:

	The migration should be simple.		The migration should be simple.

			=== the_DOMDocument ===

			<vp>the_DOMDocument</vp> interface and class in the <vp>msxml</vp> package have been renamed to <vp>dOMDocument</vp>.

	== See also ==		== See also ==

Thomas Linder Puls: /* vpiEditor */ regExp => regEx

2012-11-19T15:29:09Z

vpiEditor: regExp => regEx

← Older revision		Revision as of 17:29, 19 November 2012
Line 95:		Line 95:
	=== vpiEditor ===		=== vpiEditor ===

	The vpiEditor is not ported to the 64 bit ~~program~~ and has been deprecated. Meaning that Visusl Prolog 7.4 is the last version that will contain the it.		The <vp>vpiEditor</vp> is not ported to the 64 bit platform and has been deprecated. Meaning that Visusl Prolog 7.4 is the last version that will contain the it.

	For compatability with the 64 bit platform and future Visual Prolog releases you should migrate to the ~~'''~~sciLexer~~'''~~ instead.		For compatability with the 64 bit platform and future Visual Prolog releases you should migrate to the <vp>sciLexer</vp> instead.

	The sciLexer is the [http://www.scintilla.org/ Scintilla] editor with lexers for various programming languages including Visual Prolog.		The <vp>sciLexer</vp> is the [http://www.scintilla.org/ Scintilla] editor with lexers for various programming languages including Visual Prolog.

	There is not a 1-to-1 match between these editors and there is no trivial migration strategy.		There is not a 1-to-1 match between these editors and there is no trivial migration strategy.

			=== regExp ===

			The <vp>regExp</vp> is not ported to the 64 bit platform and has been deprecated. Meaning that Visusl Prolog 7.4 is the last version that will contain the it.

			For compatability with the 64 bit platform and future Visual Prolog releases you should migrate to the <vp>regEx</vp> (without the 'p') instead.

			The <vp>regEx</vp> package is ceated by means of [www.boost.org/libs/regex Boost Regex].

			The migration should be simple.

	== See also ==		== See also ==

Thomas Linder Puls: /* See also */ vpiEditor => sciLexer

2012-11-19T15:23:57Z

Thomas Linder Puls: First version

2012-11-06T13:27:42Z

First version

← Older revision		Revision as of 15:27, 6 November 2012
Line 1:		Line 1:
	{{Preliminary Documentation}}		{{Preliminary Documentation}}

			This document describes how to upgrade Visual Prolog 7.3 projects to Visual Prolog 7.4, for older projects you should also read [[Visual Prolog 7.3 Upgrade Notes]].

			If you have problems with upgrading your projects and need additional information, you are welcome to ask questions in [http://discuss.visual-prolog.com/viewforum.php?f=2 Visual Prolog Discussion Forum].

			By default, the installation of Visual Prolog 7.4 will not replace any previously installed versions. It is possible to work with several versions on a single computer.
			* The Commercial Edition will by default be installed in '''C:\Program Files (x86)\Visual Prolog 7.4''' or '''C:\Program Files\Visual Prolog 7.4'''.
			* The Personal Edition will by default be installed to '''C:\Program Files (x86)\Visual Prolog 7.4PE''' or '''C:\Program Files\Visual Prolog 7.4PE'''.

			Visual Prolog 7.4 projects are backward-compatible with Visual Prolog 7.3 projects.
			If you are going to use different versions of Visual Prolog installed at one computer, avoid opening projects by double-clicking on prj6 files.
			Some changes might require automatic updates in Visual Prolog 7.3 projects. Therefore, it is recommended to make the project file (PRJ6) writable before the first build. Also, it is recommended to make copies of all project files first.

			When your open a project in the Visual Prolog 7.4 IDE, it will automatically perform necessary updates of the project file. After this, it is recommended that you rebuild the entire project with the help of the '''Build \| Rebuild All command''' and answer "Yes to All" to the messages suggesting adding or removing packages and include statements.

			Notice that you should simply delete include directives to PFC files which cannot be found: proper include directives will (normally) be inserted automatically.

			== Manual updates ==

			This section describes things that may need manual updates.

			=== wParam, lParam & lResult ===

			Event handlers and other such things may give errors like:

			The expression has type 'core::booleanInt', which is incompatible with the type 'gui_native::lResult'

			To maintain the compatibility between 32 and 64 bit programs it is necessary to pay special attention to the three types:

			* <vp>gui_native::wParam</vp>
			* <vp>gui_native::lParam</vp>
			* <vp>gui_native::lResult</vp>

			These types are used extensively in the Windows API and they have different size on the 32 and 64 bit platform.

			The correct way to deal with these are:

			Pointers and handles should be <vp>uncheckedConvert</vp>'ed to/from these types.

			Numbers should be injected into these types using these <vp>gui_api</vp> predicates:

			<vip>predicates
			mkW : (integer Integer) -> wParam WParam.
			mkW : (unsigned Unsigned) -> wParam WParam.
			mkL : (integer Integer) -> lParam LParam.
			mkL : (unsigned Unsigned) -> lParam LParam.
			mkR : (integer Unsigned) -> lResult LResult.
			mkR : (unsigned Unsigned) -> lResult LResult.
			% @short Make an wParam/lParam/lResult from an integer/unsigned.
			% @end</vip>

			Numbers should be projected from these typese using these <vp>gui_api</vp> predicates:

			<vip>predicates
			getUnsigned : (unsignedNative WParam) -> unsigned Integer language prolog as "gui_api_getParam".
			getUnsigned : (integerNative WParam) -> unsigned Integer language prolog as "gui_api_getParam".
			getUnsigned : (wParam WParam) -> unsigned Unsigned language prolog as "gui_api_getParam".
			getUnsigned : (lParam LParam) -> unsigned Unsigned language prolog as "gui_api_getParam".
			getUnsigned : (lResult LResult) -> unsigned Unsigned language prolog as "gui_api_getParam".
			getInteger : (unsignedNative WParam) -> integer Integer language prolog as "gui_api_getParam".
			getInteger : (integerNative WParam) -> integer Integer language prolog as "gui_api_getParam".
			getInteger : (wParam WParam) -> integer Integer language prolog as "gui_api_getParam".
			getInteger : (lParam LParam) -> integer Integer language prolog as "gui_api_getParam".
			getInteger : (lResult LResult) -> integer Integer language prolog as "gui_api_getParam".
			% @short Convert a wParam/lParam/lResult to an unsigned/integer.
			% @end</vip>

			<vp>gui_api</vp> also defines a handy collection of constants of these types:

			<vip>constants
			wNull : wParam = uncheckedConvert(wParam, nullHandle).
			wFalse : wParam = wNull.
			wTrue : wParam = uncheckedConvert(wParam, uncheckedConvert(handle, 1)).
			wMinusOne : wParam = uncheckedConvert(wParam, uncheckedConvert(handle, -1)).
			lNull : lParam = uncheckedConvert(lParam, nullHandle).
			lFalse : lParam = lNull.
			lTrue : lParam = uncheckedConvert(lParam, wTrue).
			lMinusOne : lParam = uncheckedConvert(lParam, uncheckedConvert(handle, -1)).
			rNull : lResult = uncheckedConvert(lResult, nullHandle).
			rFalse : lResult = rNull.
			rTrue : lResult = uncheckedConvert(lResult, wTrue).
			rMinusOne : lResult = uncheckedConvert(lResult, uncheckedConvert(handle, -1)).
			% @short Constant of type lwParam/lParam/lResult.
			% @end</vip>

			Other types (like <vp>listViewControl::itemId</vp>) may have the same problem, because they are subtypes of one of the mentioned types.

			=== classInfo ===

			Some code may reference a <vp>classInfo</vp> predicate which no longer exists. The <vp>classInfo</vp> arguments are no longer used, and there is always another predicate that can be called istead of the one which is called.

			The predicates in <vp>common_exception</vp> have replacements in <vp>exception</vp>; <vp>comExceptionCheck::check</vp> should be replaced with a call to a suitable version of <vp>check2</vp> in the same class.

			== See also ==

			* [[New Features in Visual Prolog 7.4]]
			* [[Visual Prolog 7.3 Upgrade Notes]]

			[[Category:Release Notes]]

Thomas Linder Puls: Dummy

2012-11-06T11:49:44Z

Dummy

New page

← Older revision		Revision as of 12:54, 14 May 2018
Line 127:		Line 127:
	* [[Visual Prolog 7.3 Upgrade Notes]]		* [[Visual Prolog 7.3 Upgrade Notes]]

	[[Category:Release Notes]]		[[Category:Release Notes\|7.4 Upgrade Notes]]

← Older revision		Revision as of 17:23, 19 November 2012
Line 92:		Line 92:

	The predicates in <vp>common_exception</vp> have replacements in <vp>exception</vp>; <vp>comExceptionCheck::check</vp> should be replaced with a call to a suitable version of <vp>check2</vp> in the same class.		The predicates in <vp>common_exception</vp> have replacements in <vp>exception</vp>; <vp>comExceptionCheck::check</vp> should be replaced with a call to a suitable version of <vp>check2</vp> in the same class.

			=== vpiEditor ===

			The vpiEditor is not ported to the 64 bit program and has been deprecated. Meaning that Visusl Prolog 7.4 is the last version that will contain the it.

			For compatability with the 64 bit platform and future Visual Prolog releases you should migrate to the '''sciLexer''' instead.

			The sciLexer is the [http://www.scintilla.org/ Scintilla] editor with lexers for various programming languages including Visual Prolog.

			There is not a 1-to-1 match between these editors and there is no trivial migration strategy.

	== See also ==		== See also ==