VpPuZzle. Observe. Part 1 - История изменений

Victor Yukhtenko: /* References */

2008-01-31T08:57:38Z

References

← Предыдущая		Версия 10:57, 31 января 2008
Строка 351:		Строка 351:

	=References=		=References=
	[[Category:~~VpPuZzle~~]]		[[Category:VpPuZzleEn]]

Victor Yukhtenko в 21:05, 30 января 2008

2008-01-30T21:05:05Z

← Предыдущая		Версия 23:05, 30 января 2008
Строка 3:		Строка 3:

	DLL-based component technology (The Visual Prolog Puzzle or VPPZL or just PZL) is the set of agreements to build VIP-based applications on the basis of the standard VIP packages placed into DLLs. The VIP package fitted to PZL-technology agreements is named pzl-component. The VIP project (executable or DLL), which contains pzl-components, organized in a special way, is named pzl-container.		DLL-based component technology (The Visual Prolog Puzzle or VPPZL or just PZL) is the set of agreements to build VIP-based applications on the basis of the standard VIP packages placed into DLLs. The VIP package fitted to PZL-technology agreements is named pzl-component. The VIP project (executable or DLL), which contains pzl-components, organized in a special way, is named pzl-container.
	The short description of the pzl-technology and it's ~~masic~~ consepts may be found below.		The short description of the pzl-technology and it's basic consepts may be found below.
	==Motivation==		==Motivation==
	Talking about components we consider component as the peace of software, which can be reused in applications without the change of the source code.		Talking about components we consider component as the peace of software, which can be reused in applications without the change of the source code.

Victor Yukhtenko в 20:57, 30 января 2008

2008-01-30T20:57:03Z

← Предыдущая		Версия 22:57, 30 января 2008
Строка 1:		Строка 1:
	{{copyright}}		{{copyright}}
	{{~~VpPuZzle_Обзор~~. ~~Навигатор~~}}		{{VpPuZzle. Observe. Naivgator}}

	DLL-based component technology (The Visual Prolog Puzzle or VPPZL or just PZL) is the set of agreements to build VIP-based applications on the basis of the standard VIP packages placed into DLLs. The VIP package fitted to PZL-technology agreements is named pzl-component. The VIP project (executable or DLL), which contains pzl-components, organized in a special way, is named pzl-container.		DLL-based component technology (The Visual Prolog Puzzle or VPPZL or just PZL) is the set of agreements to build VIP-based applications on the basis of the standard VIP packages placed into DLLs. The VIP package fitted to PZL-technology agreements is named pzl-component. The VIP project (executable or DLL), which contains pzl-components, organized in a special way, is named pzl-container.

Victor Yukhtenko: /* PzlContainer */

2008-01-30T20:46:44Z

PzlContainer

← Предыдущая		Версия 22:46, 30 января 2008
Строка 345:		Строка 345:

	Being the usual project, PzlContainer may contain not only pzlComponents, but it may contain usual Visual Prolog packs also according to the user needs.		Being the usual project, PzlContainer may contain not only pzlComponents, but it may contain usual Visual Prolog packs also according to the user needs.

	{{VpPuZzle. Observe. Naivgator}}		{{VpPuZzle. Observe. Naivgator}}

	The feature of the PZL-technology, when two pzlComponents placed in one entity communicate explicitly with no use of PzlSystem and communicate via PzlSystem, when they are placed in different entities, gives the possibility to split the application on parts whenever user finds it convenient to him. No change in code is needed. Pzl-technology tools can help in this.		The feature of the PZL-technology, when two pzlComponents placed in one entity communicate explicitly with no use of PzlSystem and communicate via PzlSystem, when they are placed in different entities, gives the possibility to split the application on parts whenever user finds it convenient to him. No change in code is needed. Pzl-technology tools can help in this.

	=References=		=References=
	[[Category:VpPuZzle]]		[[Category:VpPuZzle]]

Victor Yukhtenko: /* Ссылки */

2008-01-30T20:43:16Z

Ссылки

← Предыдущая		Версия 22:43, 30 января 2008
Строка 348:		Строка 348:
	The feature of the PZL-technology, when two pzlComponents placed in one entity communicate explicitly with no use of PzlSystem and communicate via PzlSystem, when they are placed in different entities, gives the possibility to split the application on parts whenever user finds it convenient to him. No change in code is needed. Pzl-technology tools can help in this.		The feature of the PZL-technology, when two pzlComponents placed in one entity communicate explicitly with no use of PzlSystem and communicate via PzlSystem, when they are placed in different entities, gives the possibility to split the application on parts whenever user finds it convenient to him. No change in code is needed. Pzl-technology tools can help in this.

	=~~Ссылки~~=		=References=
	[[~~Категория~~:VpPuZzle]]		[[Category:VpPuZzle]]

Victor Yukhtenko: /* PzlContainer */

2008-01-30T20:42:12Z

PzlContainer

← Предыдущая		Версия 22:42, 30 января 2008
Строка 335:		Строка 335:
	Unlike the pzl-component, the PzlContainer “knows” which pzl-components it contains. All pzl-components, which are placed to the given pzl-container, must be included to the special package PzlConfig. The implementation of the class pzlConfig deals with the pzl-components also.		Unlike the pzl-component, the PzlContainer “knows” which pzl-components it contains. All pzl-components, which are placed to the given pzl-container, must be included to the special package PzlConfig. The implementation of the class pzlConfig deals with the pzl-components also.
	The picture below shows the structure of the PzlConfig package as it can be seen on the Project window of the IDE.		The picture below shows the structure of the PzlConfig package as it can be seen on the Project window of the IDE.

	[[Image:PzlConfigStructure.png]]		[[Image:PzlConfigStructure.png]]

Victor Yukhtenko: /* Pzl-контейнер */

2008-01-30T20:41:31Z

Pzl-контейнер

← Предыдущая		Версия 22:41, 30 января 2008
Строка 331:		Строка 331:
	The constant, which defines the way of communication, is defined in the file PzlConfig.i of the package PzlConfig.pack , which is the collection of the pzlComponents of the given entity (executable of DLL).		The constant, which defines the way of communication, is defined in the file PzlConfig.i of the package PzlConfig.pack , which is the collection of the pzlComponents of the given entity (executable of DLL).

	===~~Pzl-контейнер~~===		===PzlContainer===
	~~Pzl-контейнер является проектом системы программирования~~ Visual Prolog (~~один контейнер~~ - ~~один проект~~). ~~Он может быть проектом~~, ~~создающим исполняемое приложение (EXE) или проектом~~, ~~создающим~~ DLL.		The PzlContainer is the usual Visual Prolog project (one container - one project). It can be the project, which generates the executable application or it can be the project, which generates the DLL.
			Unlike the pzl-component, the PzlContainer “knows” which pzl-components it contains. All pzl-components, which are placed to the given pzl-container, must be included to the special package PzlConfig. The implementation of the class pzlConfig deals with the pzl-components also.
			The picture below shows the structure of the PzlConfig package as it can be seen on the Project window of the IDE.
			[[Image:PzlConfigStructure.png]]

	~~Pzl-компонента "не знает"~~, ~~в каком контейнере она помещается~~. ~~В отличие от pzl-компоненты pzl-контейнер "знает" какие pzl-компоненты он содержит~~. ~~Все pzl-компоненты~~, ~~которые помещены в данный~~ pzl-~~контейнер~~, должны быть включены в предопределенный пакет PzlConfig.pack. Имплементация класса pzlConfig содержит обращения к классам pzl-компонент.		The file of the interface type PzlConfig.i, implementation type PzlConfig.pro and package type PzlConfig.pack are the only entities, related to the pzl-components, included to the given project.

	~~Ниже приведена структура~~ PzlConfig~~, как это представляется в проектном окне IDE как главного приложения Exe, так и контейнера~~		Files PzlConfig.cl and PzlConfig.ph has no deal with pzlComponents and thus are included to the set of files of the PzlSystem. Because of the information regarding the pzlComponents included to the given pzlContainer is concentrated only in files of the pzlConfig package. This feature gives the possibility to move pzlComponents from one pzlContainer to another pzlContainer with no changes in other parts of the projects.

	~~[[Изображение:PzlConfigStructure.png]]~~		Pzl-technology tools may update the content of the pzlConfig files automatically, when pzlComponent is added (removed) to (from) the given pzlContainer.

	~~Отсутствующие здесь файлы PzlConfig.cl и PzlConfig.ph не содержат информации по конкретным pzl~~-~~компонентам и включены в набор файлов~~, помещенных в директорию PzlSystem. Приведенные же три файла PzlConfig.i, PzlConfig.pro и PzlConfig.pack обеспечивают работу pzl-компонент, включенных в данный проект. Это обстоятельство позволяет перемещать pzl-компоненты из одного контейнера в другой без модификации остальных частей проектов-контейнеров. Средства pzl-технологии обеспечивают автоматически согласованную модификацию файлов пакета pzlConfig при добавлении или удалении соответсвующих pzl-компонент из проекта-контейнера.

	~~Являясь обычным Vip проектом~~, ~~pzl-контейнер может содержать не только pzl-компоненты, но и любые другие пакеты~~, ~~соответствющие потребностям~~.		Being the usual project, PzlContainer may contain not only pzlComponents, but it may contain usual Visual Prolog packs also according to the user needs.
			{{VpPuZzle. Observe. Naivgator}}
	{{~~VpPuZzle_Обзор~~. ~~Навигатор~~}}		The feature of the PZL-technology, when two pzlComponents placed in one entity communicate explicitly with no use of PzlSystem and communicate via PzlSystem, when they are placed in different entities, gives the possibility to split the application on parts whenever user finds it convenient to him. No change in code is needed. Pzl-technology tools can help in this.
	~~Свойство pzl-технологии, заключающееся в том, что две pzl~~-~~компоненты, помещенные в один проект (генерирующий EXE или DLL)~~, ~~взаимодействуют непосредственно без участия pzl-системы~~, ~~и взаимодействуют через pzl-систему~~, если они помещаются в разные проекты, позволяет легко делить приложения на части тогда, когда программист находит это удобным. ~~Дополнительных изменений в проектах не требуется~~. Средства pzl-технологии позволяют производить такое перемещение без вникания в технические детали организации pzl-~~механизмов~~.

	=Ссылки=		=Ссылки=
	[[Категория:VpPuZzle]]		[[Категория:VpPuZzle]]

Victor Yukhtenko: /* Комбинированное использование оригинального класса и класса-делегата */

2008-01-30T20:20:01Z

Комбинированное использование оригинального класса и класса-делегата

← Предыдущая		Версия 22:20, 30 января 2008
Строка 281:		Строка 281:
	Pzl-technology tools can generate the content of files needed to have a class-proxy automatically.		Pzl-technology tools can generate the content of files needed to have a class-proxy automatically.

	===~~Комбинированное использование оригинального класса и класса-делегата~~===		===The combination of the Original and Proxy classes===
	~~В случаях~~, ~~когд вызываемый и вызывающий классы помещены в одну сущность~~ (~~в EXE или в одну и ту же~~ DLL), ~~взаимодействие классов в форме~~		In the case, when called and calling classes placed in one entity (in the executable or in one DLL), then the communication of the classes in the form
	<vip>		<vip>
	...		...
Строка 289:		Строка 289:
	...		...
	</vip>		</vip>
	~~происходит непосредственно и pzl-система не принимает участие во взаимодействии~~. ~~Здесь действуют обычные правила~~ VIP. ~~Пакет в этом случае выглядит следующим образом~~
			happens explicitly, and PZL system doesn’t participate in the interaction. The usual VIP rules work here. The package for this case looks like
	<vip>		<vip>
	#include@"AboutDialog\AboutDialog.ph"		#include@"AboutDialog\AboutDialog.ph"
Строка 300:		Строка 301:
	#include @"AboutDialog\AboutDialog.pro"		#include @"AboutDialog\AboutDialog.pro"
	</vip>		</vip>
	~~С технологической точки зрения удобно иметь все упоминания о файлах~~, ~~относящихся к pzl~~-~~компоненте - пакеты, представляющие оригинальный класс и класс-делегат~~, ~~в одном пакете~~.		It was found convenient to have all files, related to the pzlComponent - the Original and Proxy classes and packages, mentioned in one package.

	Возможность комбинированного использования соответствующих деклараций и имплементаций дает использование условной компиляции. ~~В зависимости от значения параметра условной компиляции используется либо оригинальный класс~~, ~~либо класс-делегат~~.		The conditional compilation gives the possibility to use the appropriate declarations and implementations. Depending on the meaning of the conditional compilation parameter, the original or proxy code is used.

	~~Пример текста такого комбинированного пакета приведен ниже~~.		The text of the combined package file is shown below.
	<vip>		<vip>
	#include @"AboutDialog\AboutDialog.ph"		#include @"AboutDialog\AboutDialog.ph"
			#include @"pfc\string\string.ph"

	#if iPzlConfig::useAboutDialogOriginal_C=true #then		#if iPzlConfig::useAboutDialogOriginal_C=true #then
	% privately used packages		% privately used packages
	~~#include @"pfc\string\string.ph"~~

	% private classes		% private classes
Строка 323:		Строка 324:
	#endif		#endif
	</vip>		</vip>
	Тот же принцип используется для комбинированного использования оригинального класса и класса-делегата в файле заголовка AboutDialog.ph.

	~~Таким образом~~, ~~если используется оригинальный класс, то константа~~ useAboutDialogOriginal_C ~~должна иметь значение~~ true, ~~а, если используется класс~~-~~делегат~~, ~~то константа~~ useAboutDialogOriginal_C ~~должна иметь значение~~ false.		The same principle is used to combine the contents of the header file AboutDialog.ph for the use of the Original and the Proxy related files

			So if we need to use the original classes, then the constant useAboutDialogOriginal_C must have the value true, and if we need to use the proxy-related files, then the constant useAboutDialogOriginal_C must have the value false.

	~~Значение константы~~, ~~которая определяет способ взаимодействия~~, ~~определяется в файле~~ PzlConfig.i, ~~в котором собрана информация обо всех pzl-компонентах данной сущности~~ (~~EXE или~~ DLL).		The constant, which defines the way of communication, is defined in the file PzlConfig.i of the package PzlConfig.pack , which is the collection of the pzlComponents of the given entity (executable of DLL).

	===Pzl-контейнер===		===Pzl-контейнер===

Victor Yukhtenko: /* Class delegate (proxy) */

2008-01-30T19:59:52Z

Class delegate (proxy)

← Предыдущая		Версия 21:59, 30 января 2008
Строка 254:		Строка 254:
	...		...
	</vip>		</vip>
	in the case, when called and calling classes placed in different entities (in the executable and DLL or in two different DLLs), the process of creation of the instance of the class uses the delegate (proxy) class. Thus the calling class calls the predicate new(…) of the proxy class and then proxy class communicates with the Pzl-system and Pzl-system returns the pointer to the instance of the called class to proxy class. Proxy class then converts the object domain to the domain of the called class and the creation of the pointer to the instance is complete.		in the case, when called and calling classes placed in different entities (in the executable and DLL or in two different DLLs), the process of creation of the instance of the class uses the delegate (proxy) class.

			Thus the calling class calls the predicate <vp>new(…)</vp> of the proxy class and then proxy class communicates with the Pzl-system and Pzl-system returns the pointer to the instance of the called class to proxy class. Proxy class then converts the object domain to the domain of the called class and the creation of the pointer to the instance is complete.

	The text of the proxy class is extremely simple and it is possible to generate the text of the proxy class automatically for each PzlComponent. As an example the text of the class implementation of the class-proxy is shown		The text of the proxy class is extremely simple and it is possible to generate the text of the proxy class automatically for each PzlComponent. As an example the text of the class implementation of the class-proxy is shown
	<vip>		<vip>

Victor Yukhtenko: /* Класс-делегат (proxy) */

2008-01-30T19:55:46Z

Класс-делегат (proxy)

← Предыдущая		Версия 21:55, 30 января 2008
Строка 245:		Строка 245:
	The user is free to choose the way to represent the identifier. For instance while learning the programming with the pzl-system use it is convenient to use the string representation of the identifier str(...). In the case of the real commercial programming it is preferable to use the numeric identifier uid(...).		The user is free to choose the way to represent the identifier. For instance while learning the programming with the pzl-system use it is convenient to use the string representation of the identifier str(...). In the case of the real commercial programming it is preferable to use the numeric identifier uid(...).

	===~~Класс-делегат~~ (proxy)===		===Class delegate (proxy)===
	~~При использования обычного для~~ VIP ~~стиля программирования~~
			To use the usual VIP style
	<vip>		<vip>
	...		...
	MyClassInstance =myClass::new(SomeObject),		MyClassInstance =myClass::new(SomeObject),
	MyClassInstance:~~callNeededPredicate~~(…)		MyClassInstance:CallNeededPredicate(…)
	...		...
	</vip>		</vip>
	~~в случае~~, ~~если вызывающий и вызываемый классы помещены в разные сущности~~ (~~EXE и DLL или в разные~~ DLL) , ~~процесс создания экземпляра класса использует класс-делегат~~ (proxy). ~~При этом вызывающий класс вызывает предикат~~ new() ~~класса-делегата, а класс~~-~~делегат взаимодействует с PZL~~-~~системой, которая возвращает классу-делегату указатель на экземпляр вызываемого класса~~. ~~Класс-делегат преобразует указатель, имеющий тип~~ object ~~в тип вызываемого класса и, таким образом, создание указателя экземпляра завершается~~.		in the case, when called and calling classes placed in different entities (in the executable and DLL or in two different DLLs), the process of creation of the instance of the class uses the delegate (proxy) class. Thus the calling class calls the predicate new(…) of the proxy class and then proxy class communicates with the Pzl-system and Pzl-system returns the pointer to the instance of the called class to proxy class. Proxy class then converts the object domain to the domain of the called class and the creation of the pointer to the instance is complete.
			The text of the proxy class is extremely simple and it is possible to generate the text of the proxy class automatically for each PzlComponent. As an example the text of the class implementation of the class-proxy is shown
	Текст класса-делегата очень прост и единообразен, что создает возможность его автоматической генерации для каждой pzl-компоненты. ~~Пример текста класса~~-~~делегата для класса "AboutDialog" приведен ниже~~
	<vip>		<vip>
	implement aboutDialog		implement aboutDialog
Строка 270:		Строка 270:
	new(ObjIn)=convert(iAboutDialog,ObjOut):-		new(ObjIn)=convert(iAboutDialog,ObjOut):-
	ObjOut=pzl::new(iAboutDialog::componentID_C, ObjIn).		ObjOut=pzl::new(iAboutDialog::componentID_C, ObjIn).
			</vip>
	~~end implement aboutDialog~~		The package file AboutDialog.pack has the text
	</vip>
	~~Пакет~~ AboutDialog.pack ~~имеет текст~~
	<vip>		<vip>
	#include@"AboutDialog\AboutDialog.ph"		#include@"AboutDialog\AboutDialog.ph"
	#include@"AboutDialog\AboutDialogProxy.pro"		#include@"AboutDialog\AboutDialogProxy.pro"
	</vip>		</vip>
	~~Средства pzl~~-~~технологии генерируют классы~~-~~делегаты автоматически~~.		Pzl-technology tools can generate the content of files needed to have a class-proxy automatically.

	===Комбинированное использование оригинального класса и класса-делегата===		===Комбинированное использование оригинального класса и класса-делегата===