Ide/Creating new Project Items - Revision history

Thomas Linder Puls: header level

2013-06-13T14:14:50Z

header level

← Older revision		Revision as of 16:14, 13 June 2013
Line 2:		Line 2:
	== Creating a Project ==		== Creating a Project ==

	'''~~How to Create a~~ New Project?'''		To create a new project you should activate the '''Project \| New''' menu command. Then in the opened '''{{ide\|Project Settings\|Project Settings}}''' dialog you should type in or select the desired project settings and press the '''Create''' button. The new project with the default parameters correspondent to your settings will be created.

	To create a new project you should activate the '''Project \| New''' menu command. Then in the opened '''{{ide\|Project Settings\|Project Settings}}''' dialog you should type in or select the desired project settings and press the '''Create''' button. The new project with the default parameters correspondent to your settings will be created.
	~~== Creating a Package ==~~
	{{:ide/Creating new Project Items/Creating a Package}}		{{:ide/Creating new Project Items/Creating a Package}}
	~~== Creating a COM Package ==~~
	{{:ide/Creating new Project Items/Creating a COM Package}}		{{:ide/Creating new Project Items/Creating a COM Package}}
	~~== Creating a Interface ==~~
	{{:ide/Creating new Project Items/Creating a Interface}}		{{:ide/Creating new Project Items/Creating a Interface}}
	~~== Creating a Class ==~~
	{{:ide/Creating new Project Items/Creating a Class}}		{{:ide/Creating new Project Items/Creating a Class}}
	~~== Creating a Text File ==~~
	{{:ide/Creating new Project Items/Creating a Text File}}		{{:ide/Creating new Project Items/Creating a Text File}}
	~~== Creating a Dialog ==~~
	{{:ide/Creating new Project Items/Creating a Dialog}}		{{:ide/Creating new Project Items/Creating a Dialog}}
	~~== Creating a Form ==~~
	{{:ide/Creating new Project Items/Creating a Form}}		{{:ide/Creating new Project Items/Creating a Form}}
	~~== Creating a Toolbar ==~~
	{{:ide/Creating new Project Items/Creating a Toolbar}}		{{:ide/Creating new Project Items/Creating a Toolbar}}
	~~== Creating a Menu ==~~
	{{:ide/Creating new Project Items/Creating a Menu}}		{{:ide/Creating new Project Items/Creating a Menu}}
	~~== Creating a Image ==~~
	{{:ide/Creating new Project Items/Creating a Image}}		{{:ide/Creating new Project Items/Creating a Image}}

Thomas Linder Puls: Ceating a Resources

2013-06-13T13:59:39Z

Ceating a Resources

← Older revision		Revision as of 15:59, 13 June 2013
Line 15:		Line 15:
	== Creating a Text File ==		== Creating a Text File ==
	{{:ide/Creating new Project Items/Creating a Text File}}		{{:ide/Creating new Project Items/Creating a Text File}}
	~~== Creating a Resources ==~~		== Creating a Dialog ==
	=== Creating a Dialog ===
	~~----~~
	{{:ide/Creating new Project Items/Creating a Dialog}}		{{:ide/Creating new Project Items/Creating a Dialog}}
	=== Creating a Form ===		== Creating a Form ==
	~~----~~
	{{:ide/Creating new Project Items/Creating a Form}}		{{:ide/Creating new Project Items/Creating a Form}}
	=== Creating a Toolbar ===		== Creating a Toolbar ==
	~~----~~
	{{:ide/Creating new Project Items/Creating a Toolbar}}		{{:ide/Creating new Project Items/Creating a Toolbar}}
	=== Creating a Menu ===		== Creating a Menu ==
	~~----~~
	{{:ide/Creating new Project Items/Creating a Menu}}		{{:ide/Creating new Project Items/Creating a Menu}}
	=== Creating a Image ===		== Creating a Image ==
	~~----~~
	{{:ide/Creating new Project Items/Creating a Image}}		{{:ide/Creating new Project Items/Creating a Image}}

GalinaTchekmareva at 10:02, 22 March 2013

2013-03-22T10:02:36Z

← Older revision		Revision as of 12:02, 22 March 2013
Line 1:		Line 1:
	{{ideNavbar\|Creating new Project Items}}		{{ideNavbar\|Creating new Project Items}}
	== Creating a Project ==		== Creating a Project ==
	{{:ide~~/Creating new~~ Project ~~Items/Creating a~~ Project}}
			'''How to Create a New Project?'''

			To create a new project you should activate the '''Project \| New''' menu command. Then in the opened '''{{ide\|Project Settings\|Project Settings}}''' dialog you should type in or select the desired project settings and press the '''Create''' button. The new project with the default parameters correspondent to your settings will be created.
	== Creating a Package ==		== Creating a Package ==
	{{:ide/Creating new Project Items/Creating a Package}}		{{:ide/Creating new Project Items/Creating a Package}}

GalinaTchekmareva at 10:16, 20 March 2013

2013-03-20T10:16:12Z

← Older revision		Revision as of 12:16, 20 March 2013
Line 14:		Line 14:
	== Creating a Resources ==		== Creating a Resources ==
	=== Creating a Dialog ===		=== Creating a Dialog ===
			----
	{{:ide/Creating new Project Items/Creating a Dialog}}		{{:ide/Creating new Project Items/Creating a Dialog}}
	=== Creating a Form ===		=== Creating a Form ===
			----
	{{:ide/Creating new Project Items/Creating a Form}}		{{:ide/Creating new Project Items/Creating a Form}}
	=== Creating a Toolbar ===		=== Creating a Toolbar ===
			----
	{{:ide/Creating new Project Items/Creating a Toolbar}}		{{:ide/Creating new Project Items/Creating a Toolbar}}
	=== Creating a Menu ===		=== Creating a Menu ===
			----
	{{:ide/Creating new Project Items/Creating a Menu}}		{{:ide/Creating new Project Items/Creating a Menu}}
	=== Creating a Image ===		=== Creating a Image ===
			----
	{{:ide/Creating new Project Items/Creating a Image}}		{{:ide/Creating new Project Items/Creating a Image}}

GalinaTchekmareva at 11:45, 4 March 2013

2013-03-04T11:45:32Z

Show changes

GalinaTchekmareva at 09:41, 4 March 2013

2013-03-04T09:41:50Z

← Older revision		Revision as of 11:41, 4 March 2013
Line 225:		Line 225:

	=== Creating a Text File ===		=== Creating a Text File ===

			'''How to Create a New Text File?'''

			To create a new text file in the project you should use the '''File \| New''' IDE command. In the left pane of the opened '''Create Project Item''' dialog you should select '''Text File'''. Then the dialog accepts the following shape:

			[[Image:Ide_How_NewTextFile.png\|center\|frame\|The '''New TextFile''' Dialog]]

			'''Name:'''

			In the '''Name''' edit control you should type in the name of the text file (the '''TextModule.pack''' on the picture).

			Notice that if you type in a filename without a filename extension, then the default extension '''.TXT''' is added.

			'''Parent Directory'''

			In the '''Parent Directory''' you should type in or select (using the '''Browse''' button) the parent directory. The created text file will be placed into this directory.

			'''Add to Project as Module'''

			If it is checked '''ON''', then the created text file will be seen in the {{ide\|Project Tree#The Project Tree\|Project Tree}} in the '''Project''' window.

			Notice that this feature is relatively smart. Its behavior depends upon the filename extension of the text file. If you specify the '''.PACK''' extension, for example '''TextModule.pack''', then the IDE understands that the created file can be a real project module (can be a compilation unit) and adds to the project make scripts correspondent commands to compile the module and use the obtained object (<span style="color:Purple">.OBJ</span>) file for project linking.

			If '''Add to Project as Module''' is checked '''OFF''', then the created text file will '''NOT''' be seen in the {{ide\|Project Tree#The Project Tree\|Project Tree}} in the '''Project''' window, and it will not be registered as a project module.

			After you fill in all required settings for a new text file, you can press the '''Create''' button.

	=== Creating a Resources ===		=== Creating a Resources ===

GalinaTchekmareva at 09:28, 4 March 2013

2013-03-04T09:28:28Z

@@ Line 199: / Line 199: @@
 === Creating a Class ===
 === Creating a Text File ===
 === Creating a Resources ===

GalinaTchekmareva at 08:26, 4 March 2013

2013-03-04T08:26:34Z

@@ Line 16: / Line 16: @@
 * The subdirectory into which the package files will be placed.
-* The package header file (i.e. '''NewPackage.ph''' that describes the ''public'' view of the package. The package header file should be inserted by <vp>#include</vp> directives in all other packages that use the package. The package header file contains the list of ''public'' interfaces, the list of ''public'' classes, and some <vp>#requires</vp> directives.<br />Names declared in public interfaces and classes are seen outside the package in all places where the package header file is included. <vp>#requires</vp> directives are used to guaranty that all packages required to use the package are included into the project.
+* The package header file (i.e. '''NewPackage.ph''') that describes the ''public'' view of the package. The package header file should be inserted by <vp>#include</vp> directives in all other packages that use the package. The package header file contains the list of ''public'' interfaces, the list of ''public'' classes, and some <vp>#requires</vp> directives.<br />Names declared in public interfaces and classes are seen outside the package in all places where the package header file is included. <vp>#requires</vp> directives are used to guaranty that all packages required to use the package are included into the project.
 * The package implementation file (i.e. '''NewPackage.pack''') produces a Visual Prolog compilation unit which is added to a set of project modules.
@@ Line 54: / Line 54: @@
 The package header file provides external view of the package.
-* It provides <vp>#include</vp> directives for all files containing declarations of all interfaces ('''.i''') and all classes ('''.cl''' files) exported from the package (''public ''interfaces and classes).
+* It provides <vp>#include</vp> directives for all files containing declarations of all interfaces ('''.i''' fles) and all classes ('''.cl''' files) exported from the package (''public ''interfaces and classes).
 * It contains <vp>#include</vp> directives for package header ('''.ph''' files) files of all packages publicly used by the package. Since these package header files provide declarations of all public names declared in them; therefore, all public names declared in these packages are also publicly visible from the package.
 * It contains some <vp>#requires</vp> directives. <vp>#requires</vp> directives define packages whose implementations (compiled code) have to Â be accessible in order to use the package.
@@ Line 96: / Line 96: @@
 [[Image:Ide_How_COMPackage.png|center|frame|Creating '''New COM Package''' Dialog]]
-After you fill in all required COM package settings, you can press the '''Create''' button. Then the IDE creates the package subdirectory, the package header file '''XML.ph''' for the above picture), and the package implementation file ('''XML.pack''' for the above picture). They appear in the project tree in the Project Window after the created package is compiled.
+After you fill in all required COM package settings, you can press the '''Create''' button. Then the IDE creates the package subdirectory, the package header file ('''XML.ph''' for the above picture), and the package implementation file ('''XML.pack''' for the above picture). They appear in the project tree in the Project Window after the created package is compiled.
 ==== Options: ====
@@ Line 165: / Line 165: @@
 === Creating a Interface ===
 === Creating a Class ===
 === Creating a Text File ===
 === Creating a Resources ===

GalinaTchekmareva at 10:59, 21 February 2013

2013-02-21T10:59:32Z

GalinaTchekmareva at 10:41, 21 February 2013

2013-02-21T10:41:41Z

@@ Line 86: / Line 86: @@
 The Component Object Model (COM) is a way for software components to communicate with each other. It is a binary standard that allows any two components to communicate regardless of what machine they are running on (as long as the machines are connected), what operating systems the machines are running (as long as they support COM), and what language the components are written in. COM provides location transparency: it does not matter whether components are in DLLs or in EXEs. COM components are binary units of code that include packaging and registration code and that create COM objects. Each COM component, in the COM programming model, is a programming structure encapsulating both data and functionality. It is defined and allocated as a single unit and the only public access to the COM data and functionality is through the programming interfaces.
-Each COM is simply a program module: a DLL or an EXE file. It can contain one or more COM ''components''. (In Microsoft MSDN terminology ''components''are ''coclasses''.) Each component knows about several interfaces. (In MSDN terminology - each component can support several interfaces.) Each component supports the default interface '''iUnknown'''. Using the '''iUnknown::queryInterface/2->''' predicate from the '''iUnknown''' interface, one can retrieve references to all interfaces known to a component. Each interface can provide several predicates (methods).
+Each COM is simply a program module: a DLL or an EXE file. It can contain one or more COM ''components''. (In Microsoft MSDN terminology ''components'' are ''coclasses''.) Each component knows about several interfaces. (In MSDN terminology - each component can support several interfaces.) Each component supports the default interface '''iUnknown'''. Using the '''iUnknown::queryInterface/2->''' predicate from the '''iUnknown''' interface, one can retrieve references to all interfaces known to a component. Each interface can provide several predicates (methods).
 The main aim of importing a COM component into your project is using predicates defined in this COM component. Therefore, the COM package generated for an imported COM component has to provide some wrapper (glue code) to methods implemented in the COM component. That is, the generated COM package must provide declarations of correspondent interfaces, predicates, and domains.
@@ Line 135: / Line 135: @@
 *:'''CLSID''' is a universally unique identifier (UUID) that identifies the type of a COM component. Each COM component has its '''CLSID''' in the Windows system registry database so that it can be loaded and used by other applications. For example, a spreadsheet can create worksheet components, chart components, and macrosheet components. Each of these components has its own '''CLSID''' that uniquely identifies this component to the system. That is, if your COM module (COM server or COM container) allows linking to its embedded components, then you need to register the special '''CLSID''' for each COM component embedded into the COM module.
 *:The '''CLSID''' is stored in the Windows registry database under the following registry key:
-*:'''<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID = {<CLSID>}</vipbnf>'''
+*:'''<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID = {CLSID}</vipbnf>'''
 *:The '''CLSID''' is a 128-bit number (in the hexadecimal format) within a pair of curly braces. Typically, '''CLSID'''s (and other UUID values) are represented as strings of hexadecimal numbers with the following format:
 *:<vipbnf>{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</vipbnf>
@@ Line 142: / Line 142: @@
 *:You can use the '''UUIDGEN.exe''' tool to create a new UUID.
 *:When you find a '''CLSID''' you can find the associated '''PROGID''' under the following registry sub-key:
-*:<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{CLSID}\ProgID = <programatic identifier></vipbnf>
+*:'''<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{CLSID}\ProgID = <programatic identifier></vipbnf>'''
 *:See the '''[#PROGID PROGID]''' options description below.
 *:'''Universally unique identifier (UUID)'''
@@ Line 163: / Line 163: @@
 *:In the system registry database you can find all registered '''IID'''s under:
 *:'''<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface</vipbnf>'''
 === Creating a Interface ===

← Older revision		Revision as of 12:59, 21 February 2013
Line 114:		Line 114:
	Controls in this group box are used to specify a COM module ('''DLL''' or '''EXE''') from which a component should be imported. It contains the following controls:		Controls in this group box are used to specify a COM module ('''DLL''' or '''EXE''') from which a component should be imported. It contains the following controls:

	*'''Type Library~~'''~~		===== Type Library =====
	*:When this option is checked ON, then in the edit control you should specify a file that contains the ''type library'' describing the COM component.		*:When this option is checked ON, then in the edit control you should specify a file that contains the ''type library'' describing the COM component.
	*:Press the '''Load''' button to activate the '''Load Type Library File''' dialog using which you can find and insert the name of the type library file into the edit control.		*:Press the '''Load''' button to activate the '''Load Type Library File''' dialog using which you can find and insert the name of the type library file into the edit control.
Line 120:		Line 120:
	*:If a COM client (our program importing COM server components) needs using COM server predicates, then the client application must have information about predicates in COM server components. Predicates often return values and accept parameters. The COM client requires declarations of all these predicates (and domains) in order to use them. This information can be made known in several ways. The Microsoft recommended way is to create a type library. (Remember that type libraries do not provide Prolog declarations.) Type library information can be stored in files with the following filename extensions: '''.TLB''' (type library itself), '''.OLB''' (multiple type libraries or foreign object libraries), '''.DLL''' (COM DLLs can embed type library resources), '''.EXE''' (COM EXEs can embed type library resources), '''.OCX''' (ActiveX controls).		*:If a COM client (our program importing COM server components) needs using COM server predicates, then the client application must have information about predicates in COM server components. Predicates often return values and accept parameters. The COM client requires declarations of all these predicates (and domains) in order to use them. This information can be made known in several ways. The Microsoft recommended way is to create a type library. (Remember that type libraries do not provide Prolog declarations.) Type library information can be stored in files with the following filename extensions: '''.TLB''' (type library itself), '''.OLB''' (multiple type libraries or foreign object libraries), '''.DLL''' (COM DLLs can embed type library resources), '''.EXE''' (COM EXEs can embed type library resources), '''.OCX''' (ActiveX controls).

	*'''TypeLib ID~~'''~~		===== TypeLib ID =====
	*:When this option is checked ON, then in the edit control you should specify the '''TypeLib ID''' of the ''type library'' for the COM component that you wish to import. The '''TypeLib ID''' is a universally unique identifier (UUID) under which the type library is registered in the Windows system registry. (See [#CLSID CLSID] for more information.) The '''TypeLib ID''' should be specified as a string of hexadecimal numbers with the following format:		*:When this option is checked ON, then in the edit control you should specify the '''TypeLib ID''' of the ''type library'' for the COM component that you wish to import. The '''TypeLib ID''' is a universally unique identifier (UUID) under which the type library is registered in the Windows system registry. (See {{ide\|Creating new Project Items#CLSID\|CLSID}} for more information.) The '''TypeLib ID''' should be specified as a string of hexadecimal numbers with the following format:
	*: <vipbnf>{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</vipbnf>		*: <vipbnf>{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</vipbnf>
	*:Then you '''MUST''' press the '''Load''' button to enforce the IDE to load COM information from the type library registered with this '''TypeLib ID'''.		*:Then you '''MUST''' press the '''Load''' button to enforce the IDE to load COM information from the type library registered with this '''TypeLib ID'''.
Line 127:		Line 127:
	*:'''<vipbnf>HKEY_CLASSES_ROOT\TypeLib = {TypeLib ID}</vipbnf>'''		*:'''<vipbnf>HKEY_CLASSES_ROOT\TypeLib = {TypeLib ID}</vipbnf>'''

	*'''CLSID~~'''~~		===== CLSID =====
	*:When this option is checked ON, then in the edit control you should specify the '''CLSID''' of the COM component that you wish to import. The '''CLSID''' should be specified as a string of hexadecimal numbers with the following format:		*:When this option is checked ON, then in the edit control you should specify the '''CLSID''' of the COM component that you wish to import. The '''CLSID''' should be specified as a string of hexadecimal numbers with the following format:
	*:<vipbnf>{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</vipbnf>		*:<vipbnf>{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</vipbnf>
Line 143:		Line 143:
	*:When you find a '''CLSID''' you can find the associated '''PROGID''' under the following registry sub-key:		*:When you find a '''CLSID''' you can find the associated '''PROGID''' under the following registry sub-key:
	*:'''<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{CLSID}\ProgID = <programatic identifier></vipbnf>'''		*:'''<vipbnf>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{CLSID}\ProgID = <programatic identifier></vipbnf>'''
	*:See the '''[#PROGID PROGID]''' options description below.		*:See the '''{{ide\|Creating new Project Items#PROGID\|PROGID}}''' options description below.
	*:'''Universally unique identifier (UUID)'''		*:'''Universally unique identifier (UUID)'''
	*:The universally unique identifier (UUID) is also known as the globally unique identifier (GUID). The UUID, or GUID, is a unique, 128-bit value used to identify objects. Objects can be OLE servers, interfaces, client objects, etc. Beginning from this moment objects will be identified with UUIDs.		*:The universally unique identifier (UUID) is also known as the globally unique identifier (GUID). The UUID, or GUID, is a unique, 128-bit value used to identify objects. Objects can be OLE servers, interfaces, client objects, etc. Beginning from this moment objects will be identified with UUIDs.

	*'''PROGID~~'''~~		===== PROGID =====
	*:When this option is checked ON. In the edit control you should specify the '''PROGID''' of the COM module from which you wish to import the COM component. The '''PROGID''' should be specified as a string of the following format:		*:When this option is checked ON. In the edit control you should specify the '''PROGID''' of the COM module from which you wish to import the COM component. The '''PROGID''' should be specified as a string of the following format:
	*:'''<vip><Program>.<Component>.<Version></vip>'''		*:'''<vip><Program>.<Component>.<Version></vip>'''
	*:Words are separated by dots as in <span style="color:Purple">Word.Document.6</span>. (Blank spaces cannot be used.)		*:Words are separated by dots as in <span style="color:Purple">Word.Document.6</span>. (Blank spaces cannot be used.)
	*:Then you '''MUST''' press the '''Load''' button to enforce the IDE to load COM information from the COM module registered with this '''PROGID'''.		*:Then you '''MUST''' press the '''Load''' button to enforce the IDE to load COM information from the COM module registered with this '''PROGID'''.
	*:'''PROGID'''s are versioned programmatic identifiers. '''PROGID'''s present human-readable versions of class identifiers ([#CLSID CLSID]) used to identify COM components. '''PROGID''' is a registry entry that can be associated with [#CLSID CLSID]. Like [#CLSID CLSID], '''PROGID''' identifies a COM component but with less precision because it is not guaranteed to be globally unique. The ''<vp>Version</vp>'' portion is optional but strongly recommended. Using ''<vp>Version</vp>'', even if there is only one version of the '''PROGID''', helps to avoid conflicts. It enables different versions of a component coexist without overwriting '''PROGID'''s. If you do not specify a version for a '''PROGID''', the default ''<vp>Version</vp>'' <vp>= 1</vp>.		*:'''PROGID'''s are versioned programmatic identifiers. '''PROGID'''s present human-readable versions of class identifiers ({{ide\|Creating new Project Items#CLSID\|CLSID}}) used to identify COM components. '''PROGID''' is a registry entry that can be associated with {{ide\|Creating new Project Items#CLSID\|CLSID}}. Like {{ide\|Creating new Project Items#CLSID\|CLSID}}, '''PROGID''' identifies a COM component but with less precision because it is not guaranteed to be globally unique. The ''<vp>Version</vp>'' portion is optional but strongly recommended. Using ''<vp>Version</vp>'', even if there is only one version of the '''PROGID''', helps to avoid conflicts. It enables different versions of a component coexist without overwriting '''PROGID'''s. If you do not specify a version for a '''PROGID''', the default ''<vp>Version</vp>'' <vp>= 1</vp>.
	*:How to find '''PROGID''' entries in the registry is described in the [#CLSID CLSID].		*:How to find '''PROGID''' entries in the registry is described in the {{ide\|Creating new Project Items#CLSID\|CLSID}}.

	*'''IID~~'''~~		===== IID =====
	*:When this option is checked ON, then in the edit control you should specify the '''IID''' of the COM component interface that you wish to import.		*:When this option is checked ON, then in the edit control you should specify the '''IID''' of the COM component interface that you wish to import.
	*:'''IID''' is a universally unique identifier (UUID) that uniquely identifies a particular COM interface. '''IID''' should be specified as a string of hexadecimal numbers with the following format:		*:'''IID''' is a universally unique identifier (UUID) that uniquely identifies a particular COM interface. '''IID''' should be specified as a string of hexadecimal numbers with the following format: