diff --git a/documentation/current/guide/index.wiki b/documentation/current/guide/index.wiki index ec9f64a7..5cc6be55 100644 --- a/documentation/current/guide/index.wiki +++ b/documentation/current/guide/index.wiki @@ -11,10 +11,10 @@ The documentation is organized into virtual books. Each book covers an important * [[Guide]] -- Guide to Eiffel Information * [[Why Eiffel?]] -- Why Eiffel? -* [[Method]] -- The Eiffel Method and Language +* [[Method|Method and Language]] -- The Eiffel Method and Language * [[EiffelStudio]] -- The EiffelStudio Interactive Development Environment * [[Solutions]] -- Eiffel Solutions, Technologies, and Class Libraries -* [[Windows]] -- Eiffel with Microsoft Windows +* [[Platform specifics]] -- Specific support for particular platforms, e.g., Microsoft Windows * [[Community]] -- Community Contributions There are also important sources of information on Eiffel external to these documentation pages. diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-class-reference.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-class-reference.wiki new file mode 100644 index 00000000..19571af0 --- /dev/null +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-class-reference.wiki @@ -0,0 +1,5 @@ +[[Property:title|EiffelCOM Class Reference]] +[[Property:weight|0]] +[[Property:uuid|476f2bc7-9afa-125e-0b68-3e4fc30e97f4]] +==View the [[ref:libraries/com/reference/index|EiffelCOM Class Reference]] == + diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/index.wiki index 80008b0c..f954704c 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/index.wiki @@ -7,7 +7,7 @@ The EiffelCOM library includes the following clusters: * A [[Structures|Structures]] cluster includes wrappers for COM structures and additional data structures. * A [[ref:libraries/com/reference/index|Support]] cluster provides access to helper classes. -{{seealso| '''See Also'''
+{{seealso|
[[About COM and Eiffel]]
[[EiffelCOM Wizard|EiffelCOM wizard]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/interfaces.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/interfaces.wiki index 8887999e..d56424c0 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/interfaces.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/interfaces.wiki @@ -5,7 +5,7 @@ COM interfaces have several facets. First, an interface is a deferred, or an abs ==ECOM_INTERFACE== -For each interface listed in a type library, the EiffelCOM wizard generates a deferred class and two effective classes: a proxy of an interface pointer, or a client side class, and a stub of an interface pointer, or a server side class. The deferred interface class inherits from [libraries/com/reference/ecom_interface_chart.xml| ECOM_INTERFACE ] and has a deferred feature per each interface function. Both effective classes, or implemented interfaces, inherit from the deferred class and implement its functions. The functions of the interface proxy calls the underlying C layer, which in turn calls the COM component while the functions of the interface stub implement the component functionality. +For each interface listed in a type library, the EiffelCOM wizard generates a deferred class and two effective classes: a proxy of an interface pointer, or a client side class, and a stub of an interface pointer, or a server side class. The deferred interface class inherits from [[ref:libraries/com/reference/ecom_interface_chart|ECOM_INTERFACE]] and has a deferred feature per each interface function. Both effective classes, or implemented interfaces, inherit from the deferred class and implement its functions. The functions of the interface proxy calls the underlying C layer, which in turn calls the COM component while the functions of the interface stub implement the component functionality. [[ref:libraries/com/reference/ecom_interface_chart|ECOM_INTERFACE]] holds a pointer to the underlying COM interface. @@ -19,7 +19,7 @@ which queries a COM component internally. Every interface proxy class inherits f ==ECOM_STUB== -[[ref:libraries/com/reference/ecom_stub_chart|ECOM_STUB]] inherits from [[ref:libraries/com/reference/ecom_interface_chart|ECOM_INTERFACE]] , and exposes the feature [[ref:libraries/com/reference/ecom_stub_chart|create_item]] which allows creating the underlying COM object. +[[ref:libraries/com/reference/ecom_stub_chart|ECOM_STUB]] inherits from [[ref:libraries/com/reference/ecom_interface_chart|ECOM_INTERFACE]], and exposes the feature [[ref:libraries/com/reference/ecom_stub_chart|create_item]] which allows creating the underlying COM object. diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/structures.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/structures.wiki index 57a23106..35b0f97f 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/structures.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/eiffelcom-interface-content/structures.wiki @@ -92,22 +92,22 @@ Many COM Automation servers have routines that take arguments with default value For example, the following adds a new workbook to Excel. The default argument tells Excel to decide for itself how many worksheets to put in the new workbook: - class - MY_EXCEL_APPLICATION +class + MY_EXCEL_APPLICATION - inherit - APPLICATION_PROXY +inherit + APPLICATION_PROXY - ECOM_VARIANT_ACCESS + ECOM_VARIANT_ACCESS - feature +feature - add_workbook is - local - workbook: WORKBOOK_PROXY - do - workbook := workbooks.add (missing, 0) - end + add_workbook is + local + workbook: WORKBOOK_PROXY + do + workbook := workbooks.add (missing, 0) + end diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/index.wiki index 6b84fbc1..5c84bfb0 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-library/index.wiki @@ -8,7 +8,7 @@ Platform: Windows
The EiffelCOM library provides support classes for the code generated by the EiffelCOM wizard. It has wrappings for standard COM data types such as VARIANT, SAFEARRAY, CURRENCY, DECIMAL, IUnknown, IDispatch, etc. -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/access-type.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/access-type.wiki index e0f46b5e..042fee3b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/access-type.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/access-type.wiki @@ -213,7 +213,7 @@ As information on any interface cannot be accessed dynamically, the description ==EiffelCOM== The idea in EiffelCOM is the way a component is accessed is implementation detail that the user should not have to deal with. Of course he should be able to choose what kind of access he wants to use but this choice should have no impact on the design of the Eiffel system itself. For that reason, the Eiffel code generated by the wizard follows the same architecture independently of the choice made for interface access and marshalling. The difference lies in the runtime where the actual calls to the components are implemented. -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]]
[[EiffelCOM Library| EiffelCOM library]]
[[EiffelCOM: Introduction| Introduction]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/coclass.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/coclass.wiki index c635528c..afb05b75 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/coclass.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/coclass.wiki @@ -1,5 +1,6 @@ [[Property:title|Coclass]] [[Property:weight|3]] +[[Property:uuid|7f91f9ce-e042-1d48-9d01-f9b794269ec4]] We have seen that interfaces can be perceived as views of a component. This conceptual representation actually maps the implementation of an EiffelCOM component since the coclass inherits from the interfaces and implements their deferred features. Indeed, interfaces are deferred classes with all features accessible from outside deferred. The coclass is an Eiffel class that inherits from these interfaces and implements all the features. This design is not specific to Eiffel though and can be found in other languages as well. The coclass defines the behavior of the interface functions.
==Class Object== diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-concepts.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-concepts.wiki index 9393c2bf..f2546480 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-concepts.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-concepts.wiki @@ -3,7 +3,7 @@ [[Property:weight|1]] [[Property:uuid|9cb19fc1-3d26-5752-6232-ea23f2668c32]] COM is a binary standard that describes how the component can communicate with the outer-world. The component communicates through well defined interfaces. Each interface is a specification of a group of properties and methods, and it does not contain the implementation of these routines but only their specification (signatures). The actual implementation lies in the coclass. There can be different implementations of a same interface in different coclasses. Finally, each coclass can be instantiated using a class object or class factory. These three notions will be discussed further in the forthcoming paragraphs. -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]]
[[EiffelCOM Library| EiffelCOM library]]
[[EiffelCOM: Introduction| Introduction]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-interfaces.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-interfaces.wiki index 7959586a..5ccb2a09 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-interfaces.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/com-interfaces.wiki @@ -9,7 +9,7 @@ The COM specification requires that any interface provides access to all interfa The two other functions exposed by '''IUnknown''' are '''AddRef''' and '''Release'''. These functions should be called respectively when a client gets a reference on an interface or when it discards that reference. These two functions define the lifetime of the component: each interface keeps track of clients keeping a reference on them and when no clients have references anymore, the component can be unloaded from memory. You might start worrying thinking that this business of reference counting will imply lots of headaches, memory leaks, etc. and you would be right should you choose a low-level language to implement your components. Fortunately, you will never have to implement or use these functions in Eiffel: all the processing related to IUnknown is provided by the EiffelCOM runtime. Calls to '''QueryInterface''' are done "behind the scene" and only when needed. The lifetime of the component is also taken care of by the EiffelCOM runtime. -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]]
[[EiffelCOM Library| EiffelCOM library]]
[[EiffelCOM: Introduction| Introduction]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki index 574631bd..ff1792f8 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki @@ -10,7 +10,7 @@ One main difference with out-of-process components (other than the nature of the
==Out-of-process Components== These components are standard executable acting as servers that can be accessed locally or over a network. Typically used in a three tier client server architecture, the major difference with in-process servers (other than the module type - executable instead of DLL) is their lifetime. In-process components are typically loaded to achieve a specific task and unloaded just after while out-of-process components are servers supposed to run continuously. The EiffelCOM wizard allows to build clients for such servers in Eiffel. It also provides the ability to create such servers.
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]]
[[EiffelCOM Library| EiffelCOM library]]
[[EiffelCOM: Introduction| Introduction]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/deeper-com.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/deeper-com.wiki index f11a4011..f8780475 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/deeper-com.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/deeper-com.wiki @@ -1,5 +1,6 @@ [[Property:title|Deeper into COM]] [[Property:weight|6]] +[[Property:uuid|f28ee911-1b15-260c-a290-540b9531113a]] The next paragraph gives some details on the COM internals. The understanding of these details are not required to use the EiffelCOM wizard but might help making better decisions when designing new EiffelCOM components. ==Apartments== diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/eiffelcom-introduction.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/eiffelcom-introduction.wiki index 9f19473a..a03727a4 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/eiffelcom-introduction.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/eiffelcom-introduction.wiki @@ -7,7 +7,7 @@ Briefly said, the Component Object Model is a Microsoft binary standard that est The advantages of such an approach include an increased reusability (binary reuse), a better version management (COM standard implies that new component versions are compatible with the older ones) and a built-in runtime environment. The binary reuse aspect of COM added with the source reuse ability of Eiffel offer the developer an ideal platform to increase considerably their productivity. -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]]
[[EiffelCOM Library| EiffelCOM library]]
[[Generalities| Generalities]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/index.wiki index d6346b01..eefe59c9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/index.wiki @@ -4,7 +4,7 @@ [[Property:uuid|32e79152-1e8f-43cd-e014-a83aab18e440]] ==About COM and Eiffel== -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard|EiffelCOM wizard]]
[[EiffelCOM Library| EiffelCOM library]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki index ddefd0fd..0c56106c 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki @@ -25,7 +25,7 @@ To implement a client of the StringManipulator component open a ==Contracts== Contracts can be broken directly on the proxy in which case you will get a standard contract violation in the client. If contracts are broken on the server then the exception will be forwarded by the EiffelCOM runtime to the client. The feature replace_substring_user_precondition in MY_STRING_MANIPULATOR includes has some assertions.: Comment them out. Now the contract of the [[ref:libraries/base/reference/string_8_chart|replace_substring ]] feature is wrong and erroneous calls can be made. Quick melt the changes and run the client. Enter some invalid numbers in the fields used to call this feature. After you click '''Replace''' you will see an error message box warning you that a precondition was violated on the server side. This demonstrates contracts `over the wire'. The precondition was violated in the server; this exception was caught by the EiffelCOM runtime and sent back to the client. -{{seealso| '''See Also'''
+{{seealso|
[[Creating a new COM component|Creating a new COM component]]
[[Creating a new component from an Eiffel project|Creating a new component from an Eiffel Project]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-com-component.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-com-component.wiki index c440b138..27a00816 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-com-component.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-com-component.wiki @@ -36,7 +36,7 @@ where ''system_name'' is the name of the dll (e.g. string_manipulator). So to re cd $ISE_EIFFEL\examples\com\wizard\string_manipulator\generated\component\server\EIFGENs\default\W_code regsvr32 string_manipulator.dll Once registered, follow the steps described in [[Accessing a COM component|Accessing a COM component]] to build the component's client. -{{seealso| '''See Also'''
+{{seealso|
[[Creating a new component from an Eiffel project|Creating a new component from an Eiffel Project]]
[[Accessing a COM component|Accessing a COM component.]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki index 252e7174..bbefa3fe 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki @@ -33,7 +33,7 @@ You do not need to modify or implement any classes. The wizard produces a ready- {{tip|
In most Eiffel systems functionality is spread out throughout the system. No single class exposes the full functionality of the system and can serve as a Facade to the outside world. Running the wizard on any such class would not be practical. Before starting the wizard write an Eiffel class that acts as a Facade and forwards client calls to the appropriate subsystems. Enter the Facade class name into '''Name of Eiffel facade class''' field. The wizard generates an IDL file from this class. }} -{{seealso| '''See Also'''
+{{seealso|
[[Creating a new COM component|Creating a new COM component]]
[[Accessing a COM component|Accessing a COM component.]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/index.wiki index 74b51d9c..9faf9668 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/index.wiki @@ -7,7 +7,7 @@ This chapter explains how to use the EiffelCOM wizard to create COM components a * [[Accessing a COM component|Accessing a COM component.]] -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard Introduction|Introduction]]
[[EiffelCOM Wizard Reference|EiffelCOM wizard reference]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-introduction.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-introduction.wiki index 5e1b6cab..0ca9f27f 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-introduction.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-introduction.wiki @@ -13,7 +13,7 @@ The wizard generates code from a Type Library and additional information given b [[Image:introduction]] The wizard can automatically compile the generated C and Eiffel code. To produce a Type Library corresponding to a given IDL file the wizard relies on '''MIDL''', the Microsoft IDL compiler. You may also provide the wizard with a Type Library directly. The wizard can also be used to add a COM interface to an existing Eiffel project. For the rest of the manual a '''COM Definition File''' will refer to the input file given to the wizard (either an IDL file, a Type Library or an Eiffel project file). -{{seealso| '''See Also''': [[EiffelCOM Wizard Guided Tour|Guided Tour]] , [[EiffelCOM Wizard Reference|EiffelCOM wizard reference]] }} +{{seealso|[[EiffelCOM Wizard Guided Tour|Guided Tour]] , [[EiffelCOM Wizard Reference|EiffelCOM wizard reference]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki index 5c9e85d9..80a9b8e3 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki @@ -64,7 +64,7 @@ end -- class ECOM_SERVER_COCLASS_IMP This class inherits from the generated Eiffel coclass and from ECOM_EXCEPTION. It redefines the feature coclass_feature from the generated coclass. This feature is part of the interface functions that can be called by clients of the component. Its implementation uses the featuretrigger from ECOM_EXCEPTION to raise exceptions in case the feature cannot be executed normally (invalid argument). The EiffelCOM runtime catches the exception and maps it into an HRESULT that is sent back to the client. -{{seealso| '''See Also''': [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} +{{seealso|[[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/class-hierarchy.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/class-hierarchy.wiki index c12def30..39e91943 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/class-hierarchy.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/class-hierarchy.wiki @@ -11,7 +11,7 @@ The '''Interface_proxy''' folder includes Eiffel classes wrapping interfaces tha [[Image:implemented-interface]] The '''Interface_stub''' folder includes Eiffel classes implementing interfaces that may be given to the component as an argument. These classes inherit from both the deferred interface class and [[ref:libraries/com/reference/ecom_stub_chart| ECOM_STUB ]] . [[Image:implemented-interface-server]] -{{seealso| '''See Also''': [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} +{{seealso|[[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/eiffel-project-processing.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/eiffel-project-processing.wiki index ef5a44ea..b88479ac 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/eiffel-project-processing.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/eiffel-project-processing.wiki @@ -13,7 +13,7 @@ There are some rules that the facade class must follow for the COM wizard to be * The facade class should not contain any public attribute, only routines can be exported to COM clients. * The facade class must belong to a successfully compiled Eiffel project. -{{seealso| '''See Also''': [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Accessing a COM component|Accessing a COM Component]] , [[Reusing a COM Component|Reusing a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} +{{seealso|[[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Accessing a COM component|Accessing a COM Component]] , [[Reusing a COM Component|Reusing a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/generated-files.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/generated-files.wiki index b6f8f5c9..61b99bf9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/generated-files.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/generated-files.wiki @@ -8,7 +8,7 @@ The EiffelCOM Wizard generates code into the specified destination folder. The f * Optionally, the EiffelCOM Wizard may generate a '''idl''' folder which contains the IDL file generated from the Eiffel facade class if the project consists of adding a COM interface to an existing Eiffel project. * The '''Server''' folder includes files used to implement a COM component. Apart from the usual C++ folders, it also includes a '''Component''' folder which contains Eiffel classes corresponding to the component's coclasses and a '''Interface_stub''' folder which contains Eiffel classes wrapping interfaces that may be given as argument to the component. This last folder may also be useful when accessing a COM component. The '''Server''' folder also includes a ECF file which can be used to compile the generated system if the project consists of creating a new component. -{{seealso| '''See Also''': [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} +{{seealso|[[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki index 12fc4f6b..fd0f13ab 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki @@ -13,7 +13,7 @@ Optionally, EiffelStudio can be opened on the generated system by clicking the c {{note|The EiffelStudio button will only be enabled if the Eiffel code was compiled. }} -{{seealso| '''See Also''': [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} +{{seealso|[[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/index.wiki index 7b27e714..9c864326 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/index.wiki @@ -10,7 +10,7 @@ The EiffelCOM Wizard allows the creation of Eiffel projects implementing or reus * [[Building a COM Component|Building a COM Component]] describes how to build a new COM component. * [[Wizards: Command Line Options|Command Line Options]] describes using the wizard from the command line. -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Wizard Introduction|Introduction]]
[[EiffelCOM Wizard Guided Tour|Guided Tour]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/reusing-com-component.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/reusing-com-component.wiki index b3d23560..932e3262 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/reusing-com-component.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/reusing-com-component.wiki @@ -87,7 +87,7 @@ feature -- Basic Operations end -- class COCLASS_CLIENT -{{seealso| '''See Also''': [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Building a COM Component|Reusing a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} +{{seealso|[[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Building a COM Component|Reusing a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/wizards-command-line-options.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/wizards-command-line-options.wiki index 1976567a..db0db543 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/wizards-command-line-options.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/wizards-command-line-options.wiki @@ -27,7 +27,7 @@ The list of options is the following: * '''--version, -v''': Print version information. * '''--help, -h''': Display help on how to use the EiffelCOM Wizard command line utility. -{{seealso| '''See Also''': [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] }} +{{seealso|[[How the EiffelCOM Wizard works|How the EiffelCOM Wizard Works]] , [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/index.wiki index 56edf48e..9c318e6f 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/index.wiki @@ -4,7 +4,7 @@ Type: Wizard
Platform: Windows -{{seealso| '''See Also'''
+{{seealso|
[[EiffelCOM Library|EiffelCOM library]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/com/index.wiki b/documentation/current/platform-specifics/microsoft-windows/com/index.wiki new file mode 100644 index 00000000..5b58027c --- /dev/null +++ b/documentation/current/platform-specifics/microsoft-windows/com/index.wiki @@ -0,0 +1,7 @@ +[[Property:title|COM]] +[[Property:weight|0]] +[[Property:uuid|993f5778-97c1-e113-31d7-61ae81c559fb]] +==Microsoft COM== + +Eiffel support for Microsoft COM. + diff --git a/documentation/current/platform-specifics/microsoft-windows/net/building-net-application.wiki b/documentation/current/platform-specifics/microsoft-windows/net/building-net-application.wiki index 15c8e470..49e19f5e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/building-net-application.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/building-net-application.wiki @@ -1,5 +1,6 @@ [[Property:title|Building a .NET application]] [[Property:weight|1]] +[[Property:uuid|a44736cf-41df-1679-9c6d-7b56f31d5f9a]] Eiffel for .NET has some specific functionality meant to leverage necessary aspects of the .NET Framework. For that reason, the [[EiffelStudio: Project settings window|project settings]] for Eiffel for .NET introduces new options. These options include: diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki index eaebb75c..65348fb1 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki @@ -32,7 +32,7 @@ This last setting will only appear for configurations other than the default con New configurations may be created by clicking the ''New'' button or the ''New'' entry in the ''File'' menu. The New Configuration dialog box asks for the name and the path of the configuration. It will create a file with the extension '''.ecd''' ('''E'''iffel '''C'''ode'''D'''om) with the specified name in the directory located at the specified path. Whenever one of the applications listed at the bottom of the New Configuration dialog loads the Eiffel CodeDom Provider, it will use this new configuration. ==Configuration Properties== Double clicking on the configuration name in the configurations list, clicking the ''Properties'' button or choosing the ''Properties'' menu entry in the ''File'' menu will open the Configuration Properties dialog. This dialog gives the dates of creation and last modification of the configuration as well as the list of applications that use it if it's not the default configuration. -{{seealso| '''See also:''' [[Configuration|Configuration]] , [[Logging|Logging]] }} +{{seealso|[[Configuration|Configuration]] , [[Logging|Logging]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/esplitter.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/esplitter.wiki index 599f531f..42a3e08f 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/esplitter.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/esplitter.wiki @@ -1,5 +1,6 @@ [[Property:title|eSplitter]] [[Property:weight|0]] +[[Property:uuid|2cf7249c-fd1e-b8e0-08ab-c2995b2b8227]] This tool comes in two flavors: a command line only utility ''esplit.exe'' and a graphical tool ''esplitter.exe''. Both applications achieve the same goal: to produce standard Eiffel source files ('''.e''' files) from Eiffel CodeDom Provider generated source files ('''.es''' files). ==Command Line Utility (esplit.exe)== This utility is located in the ''Codedom\bin'' subfolder of the Eiffel for ASP.NET directory. The command line syntax is: diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/index.wiki index 7364e763..bc8615ec 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/index.wiki @@ -1,5 +1,6 @@ [[Property:title|Eiffel for ASP.NET Tools and Administration]] [[Property:weight|2]] +[[Property:uuid|960d3d4b-33d0-327f-343d-ad9d5591f07a]] The Eiffel for ASP.NET delivery comes together with several tools: * [[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] allows administering the Eiffel CodeDom Provider. * [[eSplitter|ESplitter]] allows generating standard Eiffel source files ('''.e''' files) from Eiffel CodeDom Provider generated files ('''.es''') files. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki index ce2276be..0113e3c5 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki @@ -8,7 +8,7 @@ The assemblies the tool will look into for the .NET type whose name was given in {{note|When adding an assembly and if the assembly has not been consumed (i.e. the XML names mapping files have not been generated in the Eiffel Metadata Cache) then the Name Mapper will consume the assembly, this may take a while. }} -{{seealso| '''See also:''' [[Names Mappings|Names Mapping]] }} +{{seealso|[[Names Mappings|Names Mapping]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/about-code-document-object-model-codedom.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/about-code-document-object-model-codedom.wiki index 725e7991..5bb72883 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/about-code-document-object-model-codedom.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/about-code-document-object-model-codedom.wiki @@ -4,7 +4,7 @@ CodeDom stands for the '''Code Document Object Model'''. CodeDom allows for representing source code in an abstract data structure. Such a representation is called a '''CodeDom tree''' as the underlying data structure uses a tree paradigm. This abstract representation can then be generated into different programming languages. Each language vendor provides its implementation of the CodeDom interfaces, this implementation is called a '''CodeDom Provider'''. Programmers can then build tools that can work with many different languages without having to know about each one, instead they just delegate code generation to each CodeDom Provider. The CodeDom interfaces also expose types and methods that allow for parsing source code and creating the corresponding CodeDom. The current implementation of the Eiffel CodeDom Provider does not support parsing. Code generation is a much more popular useage of the CodeDom and the current version focuses on this aspect of the technology. -{{seealso| '''See also:''' [[Installation|Installation]] }} +{{seealso|[[Installation|Installation]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/common-scenarios.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/common-scenarios.wiki index 6de025f2..a61e4eb7 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/common-scenarios.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/common-scenarios.wiki @@ -9,9 +9,9 @@ Another use of the CodeDom technology is via the WSDL utility. This utility is p Wsdl /language:"EiffelSoftware.CodeDom.CodeDomProvider, EiffelSoftware.CodeDom, Version=2.0.1.1402, Culture=neutral, PublicKeyToken=def26f296efef469"
http://api.google.com/GoogleSearch.wsdl -{{note| '''Note:''' The vesion number used above might differ depending on the version of the Eiffel CodeDom Provider dll installed on your system. }} +{{note|The vesion number used above might differ depending on the version of the Eiffel CodeDom Provider dll installed on your system. }} -{{note| '''Note:''' The example above uses the Google web service, the corresponding URL is correct at the time of writing but there is no guarentee it won't change (or be removed) in the future. }} +{{note|The example above uses the Google web service, the corresponding URL is correct at the time of writing but there is no guarentee it won't change (or be removed) in the future. }} This will generate a file with the extension '''.es''' which contains multiple Eiffel class definitions. Compiling this file will require using the CodeDom compiler (programmatically via the CodeDom ICodeCompiler interface) or using the [[eSplitter|eSplitter]] tool to generate standard Eiffel source files ('''.e''' files) that can then be compiled by the standard Eiffel compiler. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki index 804c6c96..22fcf22a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki @@ -6,7 +6,7 @@ The association between applications and configurations as well as the actual se {{note|The Eiffel for ASP.NET installation program will add a shortcut in the start menu to the Eiffel CodeDom Provider Manager. }} -{{seealso| '''See also:''' [[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] , [[Logging|Logging]] , [[Required Permissions|Required permissions]] }} +{{seealso|[[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] , [[Logging|Logging]] , [[Required Permissions|Required permissions]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki index 5a58bc07..39a322b7 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki @@ -16,7 +16,7 @@ Another interesting snippet member is the ''indexing clause snippet'' which must ==Eiffel Configuration== There are several Eiffel specific settings that can be set in the Eiffel CodeDom Provider which will affect the generated code as well as the CodeDom compiler behavior. These settings are covered in the [[Configuration|Configuration]] section. -{{seealso| '''See also:''' [[eSplitter|eSplitter]] , [[Configuration|Configuration]] }} +{{seealso|[[eSplitter|eSplitter]] , [[Configuration|Configuration]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/index.wiki index 889f283c..76857f95 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/index.wiki @@ -2,16 +2,4 @@ [[Property:weight|0]] [[Property:uuid|0b45f31f-83ea-6301-9017-7b78c6827772]] The Eiffel CodeDom Provider provides an implementation of the CodeDom Provider generation and compilation interfaces defined in the System.CodeDom namespace of the .NET Framework. This documentation includes the following sections: -* [[About the Code Document Object Model (CodeDom)|About CodeDom]] introduces the basic concepts behing the CodeDom technology. -* [[Installation|Installation]] describes the steps involved in installing the Eiffel CodeDom Provider. -* [[Supported Constructs|Supported constructs]] lists the CodeDom constructs supported by the Eiffel CodeDom Provider. -* [[Configuration|Configuration]] describes how to administer the Eiffel CodeDom Provider. -* [[Logging|Logging]] describes the logging functionality of the Eiffel CodeDom Provider. -* [[Required Permissions|Required permissions]] describes the permissions that must be granted to the process using the Eiffel CodeDom Provider. -* [[Common Scenarios|Secnarios]] shows how the Eiffel CodeDom Provider can be used with different applications. -* [[Eiffel Implementation|Eiffel implementation]] describes a few points of the Eiffel CodeDom Provider implementation that are specific to the Eiffel language. -* [[Limitations|Limitations]] lists the limitations of the current Eiffel CodeDom Provider implementation. - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki index 11662e69..5124e97f 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki @@ -10,7 +10,7 @@ Conversely, should the Eiffel Codedom Provider not be required anymore, running {{note|The '''Eiffel for ASP.NET''' installation program will take care of registering and unregistering the Eiffel CodeDom Provider properly. }} -{{seealso| '''See also''': [[Supported Constructs|Supported constructs]] }} +{{seealso|[[Supported Constructs|Supported constructs]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/limitations.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/limitations.wiki index a074cfdf..af6647b5 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/limitations.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/limitations.wiki @@ -1,5 +1,6 @@ [[Property:title|Limitations]] [[Property:weight|8]] +[[Property:uuid|6d8ab90d-f051-5010-55df-218a020d9cb5]] ==Generation Only== The current implementation of the Eiffel CodeDom Provider does not support parsing Eiffel source code to produce a CodeDom tree. Only code generation and compilation are supported in the current release. ==Managed Code Only== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/logging.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/logging.wiki index 8b5c95ed..78736ac1 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/logging.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/logging.wiki @@ -14,7 +14,7 @@ There are three types of events that can be logged: information events, warnings ==Log Location== All the Eiffel CodeDom Provider events are logged into the Windows '''System''' Log. This log can be viewed via the Windows administrative tool ''Event Viewer''. The source for the events raised by the Eiffel CodeDom Provider is ''Eiffel CodeDom Provider''. By default all the events are logged on the machine running the Eiffel CodeDom Provider but it is possible to change its configuration so that the events are logged on a different machine (see [[Required Permissions|Required permissions]] ). -{{seealso| '''See also''': [[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] , [[Supported Constructs|Supported constructs]] , [[Required Permissions|Required permissions]] }} +{{seealso|[[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] , [[Supported Constructs|Supported constructs]] , [[Required Permissions|Required permissions]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/required-permissions.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/required-permissions.wiki index 7f6bdd1e..7649965a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/required-permissions.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/required-permissions.wiki @@ -4,11 +4,11 @@ The account running the Eiffel CodeDom Provider might have restricted permissions such as when used through ASP.NET. This section aims at defining the security permissions required for the execution of the Eiffel CodeDom Provider. ==Eiffel Metadata Cache== Both when generating and compiling source code, the Eiffel CodeDom Provider needs to read and write from and to the Eiffel Metadata Cache. This repository stores the mapping information between .NET and Eiffel names for both types and their members. By default the Eiffel Metadata Cache is located in the ''Assemblies'' subfolder of the Eiffel CodeDom Provider directory. -{{note| '''Note:''' The Eiffel for ASP.NET installation program will grant read and write access to the Eiffel Metadata Cache folder for the ''ASPNET'' (default ASP.NET worker process account on Windows XP Professional) and the ''IIS_WPG'' (default ASP.NET worker process account on Windows Server 2003) accounts. }} +{{note|The Eiffel for ASP.NET installation program will grant read and write access to the Eiffel Metadata Cache folder for the ''ASPNET'' (default ASP.NET worker process account on Windows XP Professional) and the ''IIS_WPG'' (default ASP.NET worker process account on Windows Server 2003) accounts. }} The path to the Eiffel Metadata Cache folder might be changed via the [[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] , make sure the new folder can be read from and written to by the account running the process that uses the Eiffel CodeDom Provider. ==Precompile Cache== The same requirements apply to the Precompile Cache folder. By default the Precompile Cache folder is located in the ''Precompile'' subfolder of the Eiffel CodeDom directory. -{{note| '''Note:''' The Eiffel for ASP.NET installation program will grant read and write access to the Precompile Cache folder for the ''ASPNET'' (default ASP.NET worker process account on Windows XP Professional) and the ''IIS_WPG'' (default ASP.NET worker process account on Windows Server 2003) accounts. }} +{{note|The Eiffel for ASP.NET installation program will grant read and write access to the Precompile Cache folder for the ''ASPNET'' (default ASP.NET worker process account on Windows XP Professional) and the ''IIS_WPG'' (default ASP.NET worker process account on Windows Server 2003) accounts. }} As with the Eiffel Metadata Cache folder, it is possible to change the location of the Precompile Cache folder but the process running the Eiffel CodeDom Provider must always have read and write access to the folder. ==Logging== Logging requires registry read access as well as event log write access. By default, the ASP.NET worker process does not have these permissions. The easiest way to grant the required permissions to the ASP.NET worker process is by using ASP.NET impersonation. This mechanism allows the ASP.NET worker process to run under a different account. This is done by providing a ''web.config'' file in the root folder of the ASP.NET application. The content of the configuration file needs to include the following declaration: diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/supported-constructs.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/supported-constructs.wiki index d39b4c9f..ac9b927d 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/supported-constructs.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/supported-constructs.wiki @@ -1,5 +1,6 @@ [[Property:title|Supported Constructs]] [[Property:weight|2]] +[[Property:uuid|99e15890-75a9-8b76-d0b6-b9be419be5ce]] Since not every language might support all the constructs CodeDom can represent, there needs to be a way for the CodeDom Provider to specify which constructs are supported and which ones are not. This is done through the System.Codedom.Compiler.ICodeGenerator interface using method Supports.
This method takes a flag corresponding to the CodeDom contruct the caller is interested in and returns a boolean value indicating whether or not the construct is supported. In the Eiffel CodeDom Provider implementation there is a third category of constructs which will be reported as supported since the provider will generate valid Eiffel code for them but that should be distinguished from other "truly" supported constructs as the generated code will not correspond to the .NET equivalent of the construct.
Let's take an example: Enum declarations are supported by the Eiffel CodeDom Provider because the generated Eiffel code will correctly make use of the values defined in the enum. However there is no such thing as an enum type in Eiffel so there won't be a corresponding .NET enum type in the generated assembly. Such constructs are said to be "non-roundtripable" because even if the Eiffel CodeDom Provider supported parsing source code, the corresponding CodeDom tree would not include the constructs like the initial CodeDom did. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki index c6fea704..32fe0a7e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki @@ -9,7 +9,7 @@ Writing ASP.NET pages in Eiffel also requires to be familiar with the Eiffel lan The '''Samples''' folder of the Eiffel for ASP.NET delivery includes ASP.NET pages written in Eiffel. To run the samples you can either click on the corresponding link in the ''Start'' menu or open the page [http://localhost/EiffelSample http://localhost/EiffelSample] in your internet browser. Each sample comes with an extensively commented source code. {{note|The samples will only be available if IIS was installed prior to installing Eiffel for ASP.NET. }} -{{seealso| '''See also:''' [[Using Eiffel (to write ASP.NET pages)|Using Eiffel]] }} +{{seealso|[[Using Eiffel (to write ASP.NET pages)|Using Eiffel]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/eiffel-aspnet-installation.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/eiffel-aspnet-installation.wiki index 6988217f..f384a1ce 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/eiffel-aspnet-installation.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/eiffel-aspnet-installation.wiki @@ -11,7 +11,7 @@ Without IIS, ASP.NET pages cannot be loaded and thus the samples will not be ins ==ASP.NET Installation== Please consult the corresponding documentation (available online at [http://msdn.microsoft.com/asp.net/ http://msdn.microsoft.com/asp.net/] ) for configuring ASP.NET properly. In particular, be aware that by default ASP.NET is disabled on Windows 2003 Server. -{{seealso| '''See also:''' [[CodeDom: Getting Started|Getting Started]] }} +{{seealso|[[CodeDom: Getting Started|Getting Started]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/index.wiki index 29945d3a..f39d2f87 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/index.wiki @@ -2,11 +2,4 @@ [[Property:weight|-1]] [[Property:uuid|7027e7f3-38e1-5e26-c936-20aea0e0c205]] Eiffel for ASP.NET allows running ASP.NET pages written in Eiffel. It should be installed on both the web server and the developer's machine. This documentation includes the following sections: -* [[Eiffel for ASP.NET Installation|Installation]] describes the steps involved in installing Eiffel for ASP.NET. -* [[CodeDom: Getting Started|Getting started]] lists resources that will help getting started with Eiffel for ASP.NET. -* [[Using Eiffel (to write ASP.NET pages)|Using Eiffel]] lists a few points that are specific to using Eiffel for writing ASP.NET pages. -* [[Names Mappings|Names mapping]] explains how to retrieve Eiffel identifiers from .NET ones. - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki index 34144336..f349281b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki @@ -27,7 +27,7 @@ The steps to follow to retrieve the Eiffel identifier corresponding to a .NET me Max_Occurs_String -> max_occurs_string Although these simplified steps will work in most cases there are certain .NET identifiers that require additional manipulation to be translated into Eiffel. The [[Name Mapper|Name Mapper]] utility should be used when such cases arise. -{{seealso| '''See also:''' [[Name Mapper|Name Mapper]] }} +{{seealso|[[Name Mapper|Name Mapper]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/using-eiffel-write-aspnet-pages.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/using-eiffel-write-aspnet-pages.wiki index 2030334d..9e8caff5 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/using-eiffel-write-aspnet-pages.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/using-eiffel-write-aspnet-pages.wiki @@ -13,7 +13,7 @@ However if an instance of STRING is passed as an argument to an ==Compilation and Timeouts== Eiffel compilations can take longer than the default timeouts set in ASP.NET. In particular ASP.NET will run batch compilations on the entire directory that is being accessed by IIS each time the time stamp of that directory changes. If the batch compilation takes longer than the ''batchTimeout'' property defined in the machine wide configuration file (''machine.config'') then ASP.NET will start another compilation just for the requested file. This can be quite resource intensive for the Web server and thus it might be beneficial to increase the default value of 15 seconds for ''batchTimeout''. -{{seealso| '''See also:''' [[Names Mappings|Names Mapping]] }} +{{seealso|[[Names Mappings|Names Mapping]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/constructors-and-creation-procedures.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/constructors-and-creation-procedures.wiki index 576d6c60..3f02a7af 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/constructors-and-creation-procedures.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/constructors-and-creation-procedures.wiki @@ -1,5 +1,6 @@ [[Property:title|Constructors and Creation Procedures]] [[Property:weight|4]] +[[Property:uuid|f06eb414-c284-902b-0481-3f00da82d47e]] This section deals with what happens when objects, that is runtime instances of types, get created and initialized. When a new instance is created, there is an opportunity to initialize the state of the instance. This is done with a constructor in .NET, and with a creation procedure in Eiffel. ==Eiffel Creation Procedures== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-class-and-feature-names.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-class-and-feature-names.wiki index d856b3b0..8ecabdfb 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-class-and-feature-names.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-class-and-feature-names.wiki @@ -1,7 +1,7 @@ [[Property:title|Eiffel Class and Feature Names]] [[Property:weight|2]] [[Property:uuid|16e4a231-7aae-4b37-52fd-67876cc222ad]] -Certain naming conventions are respected by Eiffel programmers. Although Eiffel is not case-sensitive, convention dictates the use of upper and lower case in particular situations. When you program in EiffelEnvision, you create new Eiffel classes, but you also use types from .NET assemblies. These .NET types are presented to you in a view that is consistent with Eiffel conventions. +Certain naming conventions are respected by Eiffel programmers. Although Eiffel is not case-sensitive, convention dictates the use of upper and lower case in particular situations. When you program in Eiffel for .NET, you create new Eiffel classes, but you also use types from .NET assemblies. These .NET types are presented to you in a view that is consistent with Eiffel conventions. ==Eiffel Class Names== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-net-terminology.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-net-terminology.wiki index a42ebcd1..a61f0b2c 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-net-terminology.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-net-terminology.wiki @@ -1,5 +1,6 @@ [[Property:title|Eiffel for .NET Terminology]] [[Property:weight|1]] +[[Property:uuid|ab1ac480-e2d3-df5d-5f06-963899f1072d]] ==Eiffel Terminology Defined for C# and VB.NET Programmers== Eiffel programmers feel that it is important to have a set of precise terms with which to communicate about our method of software development. Like everything else in Eiffel, the use of certain terms is not accidental. They were chosen carefully to impart particular meaning. Many of the Terms that Eiffel programmers use are different from those used by developers using other object-oriented languages. But that does not mean that their meanings will be foreign to you. If you have some understanding of object-oriented technology, you will find that in many cases the Eiffel terms describe concepts with which you were already familiar, just under different names, and possibly with slightly different meanings. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-reserved-words.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-reserved-words.wiki index 8f6ba4ba..a348a15a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-reserved-words.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/eiffel-reserved-words.wiki @@ -1,6 +1,7 @@ [[Property:title|Eiffel Reserved Keywords]] [[Property:link_title|Eiffel reserved words]] [[Property:weight|6]] +[[Property:uuid|3b80ea3e-2ed1-adf6-ddf5-acd4e18c6d03]] There are 56 language keywords in Eiffel which cannot be used as developer defined identifiers in Eiffel class code. ==Eiffel Reserved Keywords== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/index.wiki index c120973b..a16198e9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/index.wiki @@ -1,5 +1,15 @@ [[Property:title|Conventions]] [[Property:weight|1]] [[Property:uuid|1f101597-06cd-b851-8cc1-e214b3eedb3e]] +In this section, you'll find information about how the conventions that are normally used in Eiffel programming are affected by working in the presence of .NET. +Also, you'll find out how .NET types sometimes look a little different in the presence of Eiffel. + +Because there are differences in the underlying object models upon which .NET and Eiffel have been designed, before .NET types can be made available to Eiffel developers, the assemblies in which they reside must be processed by a utility called the Eiffel Metadata Consumer. Fortunately, this all happens behind the scenes for you. You need only be aware that when you are looking at .NET types from within EiffelEnvision, you're seeing them through Eiffel-tinted lenses. + +This is really the same thing that happens with other .NET languages with Visual Studio .NET support. For example, if you look at a constructor in a .NET type using the "ildasm" utility, the constructor will be named .ctor . But, if you're in C# and look at the same constructor in the Visual Studio .NET Object Browser, the constructor will have the same name as the type ...it's a C# convention. Likewise, the same constructor viewed in Visual Basic .NET will have the name New ...that's the Visual Basic .NET convention. So, when you use ENViSioN, you see things as presented using Eiffel Conventions. + +Consider what happens when you look at .NET types using ENViSioN. When you look, for example at the type System. EventArgs , you will see it represented as an Eiffel class called EVENT_ARGS . The members of the .NET type will show up as features of the Eiffel class. Of course, you can also see the corresponding .NET names as they exist in the assembly metadata. + +The documents in this section tell you what you need to know in order to use .NET types in Eiffel, and vice versa. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/similar-types-occurring-both-libraries.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/similar-types-occurring-both-libraries.wiki index a5577f54..7ab7656e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/similar-types-occurring-both-libraries.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/similar-types-occurring-both-libraries.wiki @@ -65,7 +65,7 @@ In the following sample, we use these features of STRING to make end -{{note| '''Note:''' As shown in the above example, it is necessary to apply to_cil to a manifest string if you are assigning it to a System.String or passing it as an argument where a System.String is called for.
+{{note|As shown in the above example, it is necessary to apply to_cil to a manifest string if you are assigning it to a System.String or passing it as an argument where a System.String is called for.
This is expected to change in a future release. It shall become unnecesary to apply to_cil to manifest strings. Instead, whether a STRING or System.String is needed will be determined by the context in which the manifest string is being used, and the proper type of object will be generated. }} ===Other Similar Types=== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/type-organization.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/type-organization.wiki index 1af97921..62b77cbf 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/type-organization.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/conventions/type-organization.wiki @@ -1,5 +1,6 @@ [[Property:title|Type Organization]] [[Property:weight|3]] +[[Property:uuid|1837e091-695b-339c-f04f-cbfaea791a6c]] In any comprehensive object-oriented system, the act of programming results in creation of new data types. There must be a way of organizing these types and/or their static representation as classes. This section tells you how classes are organized in Eiffel and in .NET, and how these organization methods are used together. ==Eiffel Clusters== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net-integration.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net-integration.wiki index bb5ac50f..d8862ac7 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net-integration.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net-integration.wiki @@ -1,6 +1,7 @@ [[Property:title|Eiffel for .NET Limitations]] [[Property:link_title|Eiffel for .NET Integration]] [[Property:weight|3]] +[[Property:uuid|fe8a6a7d-4590-0db2-d59a-307082b18ecc]] ==Differences between Eiffel and Eiffel for .NET== ===Limitation of Eiffel for .NET in version 5. 5=== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki index ff37c2f0..bbf04260 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki @@ -201,7 +201,7 @@ In this feature: * "INTEGER" (after the argument list) is the feature's type. * "do " introduces the implementation code. * "Result := an_attribute + an_int" is an instruction. -{{warning| '''Note:'''This feature is a function. As a consequence the computation uses the keyword "Result" as an entity name for the value to be returned by the function }} +{{note|This feature is a function. As a consequence the computation uses the keyword "Result" as an entity name for the value to be returned by the function }} * "end" ends the feature declaration diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/design-contract-and-assertions.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/design-contract-and-assertions.wiki index 2382144a..7b4b9801 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/design-contract-and-assertions.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/design-contract-and-assertions.wiki @@ -1,5 +1,6 @@ [[Property:title|Design by Contract and Assertions]] [[Property:weight|5]] +[[Property:uuid|41172f82-227a-96b1-2dad-624f04374ee0]] ==Motivation: Concerning Correctness== When you produce an element of software, how do you know that what you produced is correct? diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki index 3ebaa4dd..5603ab86 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki @@ -26,7 +26,7 @@ class end -Okay, so class SIMPLE is only interesting in its simplicity. Let's look at a more useful example: +Okay, so class SIMPLE is only interesting in its simplicity. Let's look at an example that is more illustrative: indexing description: Objects that model lists @@ -72,7 +72,7 @@ invariant before_constraint: before implies (active = first_element) after_constraint: after implies (active = last_element) -Here is a class that, although somewhat contrived, utilizes all of the required and optional parts of the class. Let's look at each part individually. +Here is a class that, although completely contrived, utilizes all of the required and optional parts of the class. Let's look at each part individually. ===Indexing=== indexing diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki index 8b5f9933..5f283bcc 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki @@ -1,9 +1,10 @@ [[Property:title|Eiffel for .NET Compliance]] [[Property:weight|9]] [[Property:uuid|1e19c2f0-995e-02c1-0588-c134a11e0003]] -As of EiffelEnvision 2.6, Eiffel for ASP.NET 5.6 and EiffelStudio 5.7; Eiffel for .NET introduces the notion of '''Eiffel-Compliance'''. .NET specifies a number of language interopability rules in a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp Common Language Specification-Compliance] specification. Eiffel for .NET supports all CLS-Compliant type and features in .NET but now additionally supports a number of non-CLS-compliant types and features. This is the purpose of the Eiffel-Compliant notion. +As of Eiffel for ASP.NET 5.6 and EiffelStudio 5.7; Eiffel for .NET introduces the notion of '''Eiffel-Compliance'''. .NET specifies a number of language interoperability rules in a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp Common Language Specification-Compliance] specification. Eiffel for .NET supports all CLS-Compliant type and features in .NET but now additionally supports a number of non-CLS-compliant types and features. This is the purpose of the Eiffel-Compliant notion. + +The information contained within this page does not go into any depth on the Common Language Specification (CLS) or CLS-Compliance. For this information please see Microsoft's on-line documentation [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp What is the Common Language Specification?] -{{note|The information contained within this page does not go into any depth on the Common Language Specification (CLS) or CLS-Compliance. For this information please see Microsoft's on-line documentation [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp What is the Common Language Specification?] }} ==Applicability== @@ -11,7 +12,7 @@ The CLS states a number of rules .NET tools have to abide by to be CLS-compliant ==What is Eiffel-Compliant?== -As already state, anything CLS-compliant is Eiffel-compliant. Eiffel-Compliancy merely allows for exceptions so that non-CLS-compliant assemblies, types and members can be used in Eiffel for .NET. +As already stated, anything CLS-compliant is Eiffel-compliant. Eiffel-Compliancy merely allows for exceptions so that non-CLS-compliant assemblies, types and members can be used in Eiffel for .NET. The following list outlines the supported non-CLS-compliant types: * All unsigned numerical basic types such as System.UInt32 as System.UInt64, represented by NATURAL_xx. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/event-programming-agents.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/event-programming-agents.wiki index 596e1197..304528cd 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/event-programming-agents.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/event-programming-agents.wiki @@ -1,5 +1,6 @@ [[Property:title|Event Programming with Agents]] [[Property:weight|7]] +[[Property:uuid|ea9d7b9d-daa1-a415-628a-e3a2f935c12a]] In Eiffel there is a facility referred to as agents. The implementation of agents is an advanced topic, but you do not have to understand the details of the implementation of agents to put agents to work for you. That is what you will learn in this section. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/exception-mechanism.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/exception-mechanism.wiki index aabbf861..c40fc271 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/exception-mechanism.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/exception-mechanism.wiki @@ -1,5 +1,6 @@ [[Property:title|Exception Mechanism]] [[Property:weight|6]] +[[Property:uuid|84a159dd-4a19-af73-7b0b-0618a284142a]] ==Motivation: Concerning Robustness== The notion of software correctness that we saw in [[Design by Contract and Assertions|Design by Contract and Assertions]] is half of the formula for software reliability. Correctness covers what the software is supposed to do, that is, its specification. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/genericity.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/genericity.wiki index fc2d229b..e3c86d74 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/genericity.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/genericity.wiki @@ -1,5 +1,6 @@ [[Property:title|Genericity]] [[Property:weight|4]] +[[Property:uuid|3a0bfe10-78e7-00eb-d9a0-b977d1fa352a]] We got a very short introduction to generic classes when we were looking at the formal generic part of class structure in [[Eiffel Classes|Eiffel Classes]] . That discussion left to the imagination the motivation and benefits for creating generic classes. You will see that most of the generic classes model containers for multiple items and at least one of their formal generic parameters represents the type of items that are to be stored in the container. Some generic classes, like LINKABLE , care for only one instance of the type represented by their formal generic parameter. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/index.wiki index c470c08a..2d322e0b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/index.wiki @@ -1,18 +1,19 @@ [[Property:title|Eiffel for .NET]] [[Property:weight|2]] [[Property:uuid|446038d8-abd6-0a0d-2b90-94124e1ac810]] -* [[Eiffel for.NET Language|Introduction]] -* [[Eiffel Classes|Eiffel Classes]] -* [[Adding Class Features|Adding Class Features]] -* [[Inheritance|Inheritance]] -* [[Genericity|Genericity]] -* [[Design by Contract and Assertions|Design by Contract]] -* [[Exception Mechanism|Exception Mechanism]] -* [[Event Programming with Agents|Event Programming with Agents]] -* [[Using Referenced Assemblies|Using Referenced Assemblies]] -* [[Eiffel for .NET Compliance|Eiffel for .NET Compliance]] -* [[Referenced Assembly Type and Feature Name Conversion|Referenced Assembly Type and Feature Name Conversion]] +These pages contain documentation that describes the Eiffel programming language. +Eiffel is considered both a development methodology and a programming language. +Eiffel the methodology is a recipe for constructing quality software which is based on a small number of powerful concepts. Eiffel the programming language is a notation which is designed to support the methodology. +Eiffel for.NET is the Eiffel programming language made available in the .NET environment. Eiffel for.NET components can use and inherit from components in .NET assemblies that were produced using other.NET languages. And, programmers using other.NET languages can use and inherit from components in assemblies produced using Eiffel for.NET. + +==Eiffel for.NET Conventions Documentation== + +In Eiffel, as in other languages, certain conventions have evolved which constitute "the way things are done". Conventions provide consistency and therefore predictability and readability of software text. + +When working in the.NET components, particularly when using components from .NET assemblies delivered from Microsoft or produced by other parties, the conventions of Eiffel are maintained in the view of these components. The first section, titled [[Conventions]], provides you with an understanding of Eiffel terminology, conventions , and how they work with .NET. + +The remaining sections of this section are a reference for the Eiffel for .NET language. It is not a complete reference, though. Rather, it is intended to help you with the tasks that Eiffel programmers commonly encounter. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/inheritance.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/inheritance.wiki index 71722e02..3cb2f0b7 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/inheritance.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/inheritance.wiki @@ -192,7 +192,7 @@ The redefine part lists the names of effective features for which the producer o So, in this example the implementation for linear_representation , for example, that LINKED_QUEUE would have inherited from QUEUE will not be used. Instead LINKED_QUEUE implements its own version of linear_representation . -{{note| '''Note:''' When a class implements a version of an inherited feature which was deferred in its parent, this is known as "effecting" the feature. Because features being effected are getting their first implementation, it is not necessary to list their names in the redefine part, or anywhere else in the inheritance part of the heir. }} +{{note|When a class implements a version of an inherited feature which was deferred in its parent, this is known as "effecting" the feature. Because features being effected are getting their first implementation, it is not necessary to list their names in the redefine part, or anywhere else in the inheritance part of the heir. }} ===Select=== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/referenced-assembly-type-and-feature-name-conversion.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/referenced-assembly-type-and-feature-name-conversion.wiki index 68955929..2548708a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/referenced-assembly-type-and-feature-name-conversion.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/referenced-assembly-type-and-feature-name-conversion.wiki @@ -1,7 +1,7 @@ [[Property:title|Referenced Assembly Type and Feature Name Conversion]] [[Property:weight|10]] [[Property:uuid|5d575090-35d9-f983-7308-172b1641173f]] -The [[The Eiffel for .NET language|Eiffel for .NET language]] is Eiffel. It is not a variant of Eiffel that spawned a new language, as is '''C#''', or a dramatic evolution of Eiffel, such as '''Visual Basic .NET''' is to '''VB6'''. As Eiffel stands today, and will probably remain, Eiffel's conventions for class names and features names do not match that of the OO Pascal variants and the "Camel-casing" conventions recommended by Microsoft. Eiffel also does not support the notion of full quantified type names. The period (''''.'''') between namespace and type names is not valid Eiffel syntax. These naming convention rules pose a problem for maintaining the Eiffel language. To address this issue, when referencing .NET assemblies, all referenced assembly type names and feature names are converted into "Eiffel-case" when using Eiffel. +The [[The Eiffel for .NET language|Eiffel for .NET language]] is Eiffel. It is not a variant of Eiffel that spawned a new language, as is '''C#''', or a dramatic evolution of Eiffel, such as '''Visual Basic .NET''' is to '''VB6'''. As Eiffel stands today, and will probably remain, Eiffel's conventions for class names and features names match neither that of the OO Pascal variants nor the "Camel-casing" conventions recommended by Microsoft. Eiffel also does not support the notion of full quantified type names. The period (''''.'''') between namespace and type names is not valid Eiffel syntax. These naming convention rules pose a problem for maintaining the Eiffel language. To address this issue, when referencing .NET assemblies, all referenced assembly type names and feature names are converted into "Eiffel-case" when using Eiffel. ==What is Eiffel-Case?== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/using-referenced-assemblies.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/using-referenced-assemblies.wiki index 6ab5286f..6e460f83 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/using-referenced-assemblies.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/using-referenced-assemblies.wiki @@ -1,7 +1,7 @@ [[Property:title|Using Referenced Assemblies]] [[Property:weight|8]] [[Property:uuid|acbe0407-b95e-6268-fc20-238f91df595e]] -Eiffel for.NET is a first class citizen in the Microsoft.NET programming world. This means that if you are programming in Eiffel for.NET, say with ENViSioN!, you have full access to the thousands of software components in the .NET type libraries. But, that's not all. You also have full access to the thousands of components in the traditional Eiffel class libraries. And even that's not all. You have the ability to build software components which comply with.NET standards, so that they can be used by programmers using any other .NET language. Still not all. When you use Eiffel, you can choose to build software that will run under Microsoft.NET, but will be portable to other popular operating systems as well. +Eiffel for.NET is a first class citizen in the Microsoft.NET programming world. This means that if you are programming in Eiffel for.NET, you have full access to the thousands of software components in the .NET type libraries. But, that's not all. You also have full access to the thousands of components in the traditional Eiffel class libraries. And even that's not all. You have the ability to build software components which comply with.NET standards, so that they can be used by programmers using any other .NET language. Still not all. When you use Eiffel, you can choose to build software that will run under Microsoft.NET, but will be portable to other popular operating systems as well. Being an Eiffel for.NET programmer obviously put you in a very powerful position. How do you take advantage of it? diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/index.wiki index 93c1c701..a856ee35 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/index.wiki @@ -13,5 +13,3 @@ We will see: * what is Eiffel on .NET * which Eiffel mechanisms have been implemented and which haven't. - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/known-issues.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/known-issues.wiki index 74e0118d..42f01acc 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/known-issues.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/known-issues.wiki @@ -1,5 +1,6 @@ [[Property:title|Known issues]] [[Property:weight|4]] +[[Property:uuid|78c6b5c1-a87b-805d-38bd-fe64cb4e7c0d]] ==Eiffel issues== * Check here first for the [[Eiffel for .NET Limitations|Difference between Eiffel and Eiffel for .NET]] . * The root creation routine of the root class must not take any arguments. You can access the command line given to the application via the class ARGUMENTS. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/index.wiki index e80b8818..5409ccbf 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/index.wiki @@ -1,11 +1,8 @@ [[Property:title|.NET]] [[Property:weight|-15]] [[Property:uuid|55eda2f0-0c60-f08c-b141-913e31a49c2f]] -* [[.NET Installation instructions|Installation instructions]] -* [[Building a .NET application|Building a .NET application]] -* [[The Eiffel for .NET language|Eiffel for .NET language description]] -* [[Samples|Samples]] - - +==.NET== + +Eiffel support for Microsoft .NET. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/net-installation-instructions.wiki b/documentation/current/platform-specifics/microsoft-windows/net/net-installation-instructions.wiki index e6536363..81cb8df4 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/net-installation-instructions.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/net-installation-instructions.wiki @@ -3,6 +3,3 @@ [[Property:uuid|64f7e3b1-f6ee-5cc4-1006-2fc4dfdaeae7]] Before installing the .NET components for Eiffel for .NET you need to install either the .NET Framework, the .NET Framework SDK or Visual Studio .NET. If you do not have any of those installed, the installation program will prompt you with a warning because no .NET features support will be installed. - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/adonet-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/adonet-sample.wiki index 8797e3a3..965bffc0 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/adonet-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/adonet-sample.wiki @@ -1,5 +1,6 @@ [[Property:title|ADO.NET Sample]] [[Property:weight|0]] +[[Property:uuid|45d24893-63d0-c2a9-9f62-ead08ca4b901]] This sample consist of a command line showing how to interact with a database. The DataReader object is somewhat synonymous with a read-only/forward-only cursor over data. The DataReader API supports flat as well as hierarchical data. A DataReader object is returned after executing a command against a database. The format of the returned DataReader object is different from a recordset. For example, you might use the DataReader to show the results of a search list in a web page. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/index.wiki index 789207a9..9c327871 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/ado-net-samples/index.wiki @@ -1,8 +1,5 @@ [[Property:title|ADO .NET Samples]] [[Property:weight|0]] [[Property:uuid|b58f17b4-57b0-ffe9-3160-86d95512f900]] -* [[ADO.NET Sample|Ado]] - - - +ADO .NET is the data access technology of Microsoft .NET. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/calculator-console.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/calculator-console.wiki index f558d85f..208d4f37 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/calculator-console.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/calculator-console.wiki @@ -4,7 +4,7 @@ =The Calculator Sample= This sample consists of a command line reverse Polish notation (RPN) calculator. -{{note| '''Note:''' A RPN calculator works slightly differently from standard calculators. It consists of a stack of numbers. Operations are applied to the two numbers on top of the stack. The result is then put on top of the stack so that it can be used in the next operation. This sample refers to the top of the stack as ''Accumulator''. }} +{{note|A RPN calculator works slightly differently from standard calculators. It consists of a stack of numbers. Operations are applied to the two numbers on top of the stack. The result is then put on top of the stack so that it can be used in the next operation. This sample refers to the top of the stack as ''Accumulator''. }} ==Compiling== @@ -80,7 +80,7 @@ Next operation? You may use the operation 0 to clear the stack at any time. You may use q to quit the program. -{{tip| '''Tip:''' You can use the command ? to display the list of available operations. }} +{{tip|You can use the command ? to display the list of available operations. }} ==Under the Hood== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/index.wiki index fe4ae588..6da9f556 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/console-samples/index.wiki @@ -1,8 +1,5 @@ [[Property:title|Console Samples]] [[Property:weight|1]] [[Property:uuid|3f2c704c-9784-06a5-4cad-02ad58433b2c]] -* [[Calculator: console|Calculator]] - - - +Console application samples. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/index.wiki index 17c5aa68..cd4d94da 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/index.wiki @@ -5,30 +5,3 @@ In this chapter you will find a series of examples that will permit to you to un However, you should be familiar with Object-Oriented programming model. Almost all other examples can also be built for .NET if the dotnet target is choosen instead of classic. -==Console sample== -* [[Calculator: console|Calculator]] - -==Threads Samples== -* [[Pools|Pools]] -* [[Timers|Timers]] - -==ADO.NET sample== -* [[ADO.NET Sample|ADO.NET]] - -==Windows Form samples== - -The following samples are classified from the easiest to the most complex one. So, some notions are introduced in the few first samples and will not be explained again in the complex samples! -* [[Simple Hello world form sample|Hello world form]] -* [[Message Box|Message box]] -* [[Date Time Picker|Calendar and dates]] -* [[Progress bar sample|Progress bar]] -* [[Menus|Adding Menu to a Form]] -* [[MDI|Writing MDI Applications]] -* [[Tree view|Tree view]] -* [[Calculator: winform|Calculator]] -* [[GDI plus - text|Text (gdi plus)]] -* [[Simple data binding|Simple data binding]] - - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/index.wiki index 5f5ca372..5d6dcef8 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/index.wiki @@ -1,9 +1,5 @@ [[Property:title|Threads Samples]] [[Property:weight|2]] [[Property:uuid|62e36a4c-0afd-e143-9a1f-98eab4022e6b]] -* [[Pools|Pools]] -* [[Timers|Timers]] - - - +Samples using .NET threading technology. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/pools.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/pools.wiki index ff4dcc90..b7f1f536 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/pools.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/pools.wiki @@ -1,5 +1,6 @@ [[Property:title|Pools]] [[Property:weight|0]] +[[Property:uuid|ace044b0-1fb7-22a0-6c18-880281ed3b6d]] This sample demonstrates use of the THREAD_POOL (ThreadPool) class. The sample queues up an asynchronous method call that is executed by a thread from the thread pool managed by the Common Language Runtime. The method "does some work" and then sets an event indicating that the work has finished. The main thread waits on the event and then exits. ==Compiling== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/timers.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/timers.wiki index 088e2801..2bd477de 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/timers.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/threads-samples/timers.wiki @@ -1,5 +1,6 @@ [[Property:title|Timers]] [[Property:weight|1]] +[[Property:uuid|325ac6e6-9660-891c-2605-dbeb621649f0]] This sample consist in a command line demonstrating the use of the TIMER (Timer) class to generate a periodic callback to a method. The sample creates a TIMER object and passes to it a delegate object. When the TIMER fires, the delegate is invoked, and a static method is called asynchronously by a worker thread in the thread pool. ==Compiling== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/calculator-winform.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/calculator-winform.wiki index cd2e6205..2deda22d 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/calculator-winform.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/calculator-winform.wiki @@ -1,5 +1,6 @@ [[Property:title|Calculator: winform]] [[Property:weight|-8]] +[[Property:uuid|9d064b1c-e109-35e8-70d5-73feec59fca1]]
[[Image:calculator|Calculator]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/date-time-picker.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/date-time-picker.wiki index dd548b01..3ea8936b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/date-time-picker.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/date-time-picker.wiki @@ -25,7 +25,9 @@ After launching the application, you will see a window displayed with a similar Clicking on the "Change font" button and a change font dialog box will appear. [[Image:change-font-dialog|change font dialog box]] . -Clicking on the "Change color" button and a dialog_box will appear. [[Image:dotnet-samples--date-time-picker-change-color-dlg|dialog box]] It will permit you to customize the color appearance of the calendar though a color dialog box [[Image:dotnet-samples--date-time-picker-change-color-dlg|color dialog box]] . +Clicking on the "Change color" button and a dialog_box will appear. [[Image:dotnet-samples--date-time-picker-change-color-dlg|dialog box]] + +It will permit you to customize the color appearance of the calendar though a color dialog box [[Image:dotnet-samples--date-time-picker-change-color-dlg|color dialog box]] . @@ -49,10 +51,3 @@ This sample contains the following classes: This sample is translated from the example located in the QuickStart\winforms\samples\controlReference\dateTimePicker sub-directory of the .NET Framework SDK samples directory of Microsoft Visual Studio .NET. - - - - - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/gdi-plus-text.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/gdi-plus-text.wiki index da6fed7b..0297b437 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/gdi-plus-text.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/gdi-plus-text.wiki @@ -36,10 +36,3 @@ This sample contains the following class: This sample is translated from the example located in the QuickStart\winforms\samples\gdiplus subdirectory of the .NET Framework SDK samples directory of Microsoft Visual Studio.NET. - - - - - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/index.wiki index a0bdc9f3..61482c4b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/index.wiki @@ -1,17 +1,5 @@ [[Property:title|Winform Samples]] [[Property:weight|3]] [[Property:uuid|24cbeb3c-ba2b-1fea-ccec-89600bbf3256]] -The following examples are classified from the easiest to the most complex one. So, some notions are introduced in the few first examples and will not be explained again in the complex examples! -==Getting started== -* [[Simple Hello world form sample|Hello world form]] -* [[Message Box|Message box]] -* [[Menus|Adding Menu to a Form]] -* [[MDI|Writing MDI Applications]] - -==Building applications== -* [[Calculator: winform|Calculator]] -* [[GDI plus - text|Text (gdi plus)]] - - - +The following examples are classified generally from the easiest to the most complex. So, some notions are introduced in the few first examples and will not be explained again in the more complex examples! diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/index.wiki index 583ad5e3..3a15362e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/index.wiki @@ -1,5 +1,6 @@ [[Property:title|MDI]] [[Property:weight|-9]] +[[Property:uuid|d1cb553c-8394-9f27-4d75-8d69f8582e49]]
[[Image:mdi|Hello world form]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/mdi-details.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/mdi-details.wiki index 10763740..fb347e69 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/mdi-details.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/mdi/mdi-details.wiki @@ -1,5 +1,6 @@ [[Property:title|MDI Details]] [[Property:weight|0]] +[[Property:uuid|f39b5ac5-64ae-781d-8d43-305954ae8d28]] Multiple Document Interface (MDI) applications have a single, primary window (the parent window) that contains a set of windows within its client region (child windows). Each child window is a form that is constrained to appear only within the parent. Children typically share the menu bar, tool bar, and other parts of the parent's interface. Secondary windows like dialog boxes are not constrained to the parent window's client region. ==Creating an MDI Application== diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/index.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/index.wiki index 62f8a26a..7da6bb6b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/index.wiki @@ -1,5 +1,6 @@ [[Property:title|Menus]] [[Property:weight|-10]] +[[Property:uuid|5a32fed4-0b46-51f8-a6b6-fc3eac70a844]]
[[Image:menu-principal|Hello world form]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/menu-details.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/menu-details.wiki index 9ee94f76..83310104 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/menu-details.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/menus/menu-details.wiki @@ -1,5 +1,6 @@ [[Property:title|Menu Details]] [[Property:weight|0]] +[[Property:uuid|81ae03a0-387d-f776-17b9-f4a83c49b75f]] Windows Forms supports menus and context menus. Main menus are displayed on a menu bar that is located immediately below the title bar of a form. The menu bar contains top-level menu items that are used to group related submenu items. For example, by clicking a '''File''' top-level menu item, you can display menu items that are related to file operations. Menu items typically appear as commands for your application (such as '''New''' and '''Open'''),but they can also appear as separator bars and submenu items. You can display a check mark next to a menu item to display the state of a command or a the state of a feature in your application. In Windows Forms, main menus are represented by the '''MainMenu''' control. Context menus can be displayed for a specific control or area of your form. They are typically accessed by clicking the right mouse button. In Windows Forms, context menus are represented by the '''ContextMenu''' control. diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/message-box.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/message-box.wiki index a5d2045f..3ba43120 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/message-box.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/message-box.wiki @@ -1,5 +1,6 @@ [[Property:title|Message Box]] [[Property:weight|-11]] +[[Property:uuid|cbc37679-43b0-99b8-b8c7-1be8be49882e]]
[[Image:hello-world|Hello world form]]
[[Image:message-box|Hello world form]] diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/progress-bar-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/progress-bar-sample.wiki index 979b0f70..32ed98d8 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/progress-bar-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/progress-bar-sample.wiki @@ -39,10 +39,3 @@ This sample contains the following classes: This sample is translated from the example located in the QuickStart\winforms\samples\controlReference\ProgressBar sub-directory of the .NET Framework SDK samples directory of Microsoft Visual Studio .NET. - - - - - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-data-binding.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-data-binding.wiki index d2919eaa..192b1c57 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-data-binding.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-data-binding.wiki @@ -46,10 +46,3 @@ This sample contains the following class: This sample is translated from the example located in the QuickStart\winforms\samples\dataBinding subdirectory of the .NET Framework SDK samples directory of Microsoft Visual Studio.NET. - - - - - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-hello-world-form-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-hello-world-form-sample.wiki index 5dc18550..e209d9cf 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-hello-world-form-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/simple-hello-world-form-sample.wiki @@ -1,5 +1,6 @@ [[Property:title|Simple Hello world form sample]] [[Property:weight|-12]] +[[Property:uuid|f4f924a5-20a2-403b-ee1d-a39c77fbb8fd]]
[[Image:simple-hello-world|Hello world form]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/tree-view.wiki b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/tree-view.wiki index beabbf8c..54b3f4a8 100644 --- a/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/tree-view.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/net/samples/winform-samples/tree-view.wiki @@ -40,10 +40,3 @@ This sample contains the following classes: This sample is translated from the example located in the QuickStart\winforms\samples\ControlReference\TreeView subdirectory of the .NET Framework SDK samples directory of Microsoft Visual Studio .NET. - - - - - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/resourcebench/features.wiki b/documentation/current/platform-specifics/microsoft-windows/resourcebench/features.wiki index c8dc64bb..f4b2e1af 100644 --- a/documentation/current/platform-specifics/microsoft-windows/resourcebench/features.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/resourcebench/features.wiki @@ -1,6 +1,7 @@ [[Property:title|Features]] [[Property:weight|0]] [[Property:uuid|3f6c7915-7e08-fc2b-f25a-7d98dff38631]] +==ResourceBench Features== * Parse any resource file (created by Microsoft Developer Studio or Borland Resource Workshop). * Show resources by using a tree view control. * Display some resource's informations. diff --git a/documentation/current/platform-specifics/microsoft-windows/resourcebench/index.wiki b/documentation/current/platform-specifics/microsoft-windows/resourcebench/index.wiki index be60b019..d60e9dca 100644 --- a/documentation/current/platform-specifics/microsoft-windows/resourcebench/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/resourcebench/index.wiki @@ -6,11 +6,5 @@ Platform: Any
Version: 5.4
Availability: Basic Package -See: -* [[Features|What does ResourceBench do?]] -* [[Tour|How to use ResourceBench]] -* [[Troubleshooting|Troubleshooting]] - - diff --git a/documentation/current/platform-specifics/microsoft-windows/resourcebench/tour.wiki b/documentation/current/platform-specifics/microsoft-windows/resourcebench/tour.wiki index db4e81e7..39c6de57 100644 --- a/documentation/current/platform-specifics/microsoft-windows/resourcebench/tour.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/resourcebench/tour.wiki @@ -1,5 +1,6 @@ [[Property:title|Tour]] [[Property:weight|1]] +[[Property:uuid|5990eda2-2eac-6a40-8e99-5a0c5e9fc15f]] 1 - Launch the Resource Bench application. This small dialog box will appear for the initialization process: [[Image:retriev]] Then you get the main window of Resource Bench: diff --git a/documentation/current/platform-specifics/microsoft-windows/resourcebench/troubleshooting.wiki b/documentation/current/platform-specifics/microsoft-windows/resourcebench/troubleshooting.wiki index 91d24e67..eada5ab7 100644 --- a/documentation/current/platform-specifics/microsoft-windows/resourcebench/troubleshooting.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/resourcebench/troubleshooting.wiki @@ -1,5 +1,6 @@ [[Property:title|Troubleshooting]] [[Property:weight|2]] +[[Property:uuid|775c2f23-7138-c830-4e14-4d9898043229]] If you have problems when you parse a resource file, you can first try to remove the grammar file (its name is "rb.gram"), and then re-launch Resource Bench. It creates again the grammar file to allow parsing resource files (on a Pentium 120 it takes less than one minute). diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/index.wiki index a063a530..37b526a6 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/index.wiki @@ -10,6 +10,6 @@ WEL is an encapsulation of the Win32 Application Programming Interface (API), an ==Getting started with WEL== -If you are new to WEL, then the best place to begin is the [[Tutorial|tutorial]] which is a series of samples demonstrating the development of a simple WEL system. +If you are new to WEL, then the best place to begin is the [[WEL Tutorial|tutorial]], which consists of a series of samples demonstrating the development of a simple WEL system. Also take a look at [[WEL Common Concepts|WEL common concepts]] for details of some common concepts used in WEL programming. diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-class-reference.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-class-reference.wiki new file mode 100644 index 00000000..87a18fe7 --- /dev/null +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-class-reference.wiki @@ -0,0 +1,5 @@ +[[Property:title|WEL Class Reference]] +[[Property:weight|3]] +[[Property:uuid|a7745f7c-48e0-342b-8eeb-c0aad7553e29]] +==View the [[ref:libraries/wel/reference/index|WEL Class Reference]]== + diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/common-message-hooks.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/common-message-hooks.wiki index 51b8c472..1398c13e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/common-message-hooks.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/common-message-hooks.wiki @@ -11,12 +11,12 @@ Each WEL library component implements a set of routines for processing the most An on_paint message corresponds to the Wm_paint message generated by Windows whenever it needs to re-paint a window, and if you look at the feature, you can see that the arguments are a [[ref:libraries/wel/reference/wel_paint_dc_chart|WEL_PAINT_DC]] and a[[ref:libraries/wel/reference/wel_rect_chart| WEL_RECT]] . which are relevant to this message. By redefining this feature (and others as required), your code will be able to respond appropriately to windows events. -{{note| '''Note'''. See [[Tutorial Step 2|step2]] in the [[WEL Tutorial|tutorial]] for a simple demonstration involving the re-definition of on_left_button_down. }} +{{note|. See [[Tutorial Step 2|step2]] in the [[WEL Tutorial|tutorial]] for a simple demonstration involving the re-definition of on_left_button_down. }} For different messages received by a control, the arguments will differ (sometimes there are none), but those arguments will always be relevant to the message. For example, on_menu_command from [[ref:libraries/wel/reference/wel_composite_window_chart|WEL_COMPOSITE_WINDOW]] has an INTEGER as an argument, the value of which is a unique menu identifier.
-{{note| '''Note'''. Not all windows events have a corresponding `on_' message hook defined in WEL. If you wish to process a Windows message that does not correspond to one of the available features, you will need to redefine process_message.
+{{note|. Not all windows events have a corresponding `on_' message hook defined in WEL. If you wish to process a Windows message that does not correspond to one of the available features, you will need to redefine process_message.
}} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/index.wiki index f77da112..4cc93b43 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/index.wiki @@ -1,12 +1,6 @@ [[Property:title|WEL Common Concepts]] [[Property:weight|0]] [[Property:uuid|f2486cae-0ce5-7360-d40f-aea5f2766ebd]] -Some useful WEL concepts are listed below: -* [[Inheriting WEL_APPLICATION|Inheriting WEL_APPLICATION]] -* [[Redefining main_window|Redefining main_window]] -* [[Redefining `init_application'|Redefining init_application]] -* [[Common message hooks|Common message hooks]] - - +WEL concepts you should understand. diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/inheriting-wel-application.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/inheriting-wel-application.wiki index 92ecfc2b..5563d13e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/inheriting-wel-application.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/inheriting-wel-application.wiki @@ -3,7 +3,7 @@ [[Property:uuid|e6b092c9-dfb1-7bf1-67fc-647d047b6a01]] For most WEL applications that you write, you will need to inherit [[ref:libraries/wel/reference/wel_application_chart|WEL_APPLICATION]] . -{{note| '''Note'''. See [[Tutorial Step 1|step1]] in the [[WEL Tutorial|tutorial]] for a simple demonstration of how to do this }} +{{note|. See [[Tutorial Step 1|step1]] in the [[WEL Tutorial|tutorial]] for a simple demonstration of how to do this }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-init-application.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-init-application.wiki index 0aa8f445..530356b9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-init-application.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-init-application.wiki @@ -3,6 +3,3 @@ [[Property:uuid|95d9b971-7470-9191-3023-b99c22354e8f]] [[ref:libraries/wel/reference/wel_application_chart|WEL_APPLICATION]] contains a feature init_application which does nothing by default, but is called before the application is started. This can be redefined to execute tasks that must be performed before the application is running. A common redefinition is to allow the loading of common dll's, see [[List View|list_view]] sample for a demonstration of this technique. - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-main-window.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-main-window.wiki index 16f255be..2cd9a802 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-main-window.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-common-concepts/redefining-main-window.wiki @@ -3,7 +3,7 @@ [[Property:uuid|f7bfd5d0-86ef-5387-ba79-5461a516bcf6]] When you inherit [[ref:/libraries/wel/reference/wel_application_chart|WEL_APPLICATION]] , you will need to implement the deferred feature main_window as a once function. This will be the main window of your application, and can be any descendent of [[ref:libraries/wel/reference/wel_composite_window_chart|WEL_COMPOSITE_WINDOW]] . -{{note| '''Note'''. See [[Tutorial Step 2|step2]] in the [[WEL Tutorial|tutorial]] for a simple demonstration of how to do this. }} +{{note|. See [[Tutorial Step 2|step2]] in the [[WEL Tutorial|tutorial]] for a simple demonstration of how to do this. }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/index.wiki index 1b47b0c2..ef828e2b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/index.wiki @@ -5,7 +5,7 @@ A Control is a window which provides a means of interacting with the application. For example, the [[ref:libraries/wel/reference/wel_edit_chart|WEL_EDIT]] control provides a user with the means of entering and modifying text. There are many common controls available within this cluster, each with a specific use. -{{note| '''Note:''' Each control inherits from [[ref:libraries/wel/reference/wel_control_chart|WEL_CONTROL]] which is a descendent of [[ref:libraries/wel/reference/wel_window_chart|WEL_WINDOW]] This provides the control with a large number of general features (including full window functionality). Each control also provides its own feature set which give access to specific properties of that control. }} +{{note|Each control inherits from [[ref:libraries/wel/reference/wel_control_chart|WEL_CONTROL]] which is a descendent of [[ref:libraries/wel/reference/wel_window_chart|WEL_WINDOW]] This provides the control with a large number of general features (including full window functionality). Each control also provides its own feature set which give access to specific properties of that control. }} ==Creating controls== diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-check-box-3-state.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-check-box-3-state.wiki index 2e863dbc..35200d91 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-check-box-3-state.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-check-box-3-state.wiki @@ -14,7 +14,7 @@ A indeterminate [[ref:libraries/wel/reference/wel_check_box_3_state_chart|WEL_CH [[Image:wel-check-box-3-state-indeterminate|wel_check_box_3_state_indeterminate]]

-{{seealso| '''See also'''
+{{seealso|
[[WEL_CHECKBOX|WEL_CHECK_BOX]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-checkbox.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-checkbox.wiki index b726de6c..468f680b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-checkbox.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-checkbox.wiki @@ -9,7 +9,7 @@ A [[ref:libraries/wel/reference/wel_check_box_chart|WEL_CHECK_BOX]]

A checked [[ref:libraries/wel/reference/wel_check_box_chart|WEL_CHECK_BOX]]
[[Image:wel-check-box-checked|wel_check_box_checked]] -{{seealso| '''See also'''
+{{seealso|
[[WEL_CHECK_BOX_3_STATE|WEL_CHECK_BOX_3_STATE]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-down-control.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-down-control.wiki index 1392cc8c..7b2aa4af 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-down-control.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-down-control.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_UP_DOWN_CONTROL]] [[Property:weight|15]] +[[Property:uuid|71cbdf70-3bf0-a087-6859-30c1564c27a4]] A [[ref:libraries/wel/reference/wel_up_down_control_chart|WEL_UP_DOWN_CONTROL]] consists of a pair of arrows which are used to increment or decrement a value. Using set_buddy_window, a window of type [[ref:libraries/wel/reference/wel_window_chart|WEL_WINDOW]] can be linked to this control, and is commonly used to display the current value. ==Appearance== [[Image:wel-up-down-control|wel_up_down_control]] diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-group-box.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-group-box.wiki index 8a89a077..94fef84b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-group-box.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-group-box.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_GROUP_BOX]] [[Property:weight|2]] +[[Property:uuid|9ef874da-4d1f-b3f4-9645-9b50b1718daf]] A [[ref:libraries/wel/reference/wel_group_box_chart|WEL_GROUP_BOX]] is used to enclose other controls, and certain controls such as a [[WEL_RADIO_BUTTON|WEL_RADIO_BUTTON]] have special behavior when parented in a [[ref:libraries/wel/reference/wel_group_box_chart|WEL_GROUP_BOX]] . ==Appearance== diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-list-view.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-list-view.wiki index 2f7d6c68..e3e56645 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-list-view.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-list-view.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_LIST_VIEW]] [[Property:weight|3]] +[[Property:uuid|730f6b22-f858-816f-090e-c32ec1bebfd9]] A [[ref:libraries/wel/reference/wel_list_view_chart|WEL_LIST_VIEW]] control is an encapsulation of the Windows List View control and provides several ways of displaying a collection of items. Each item can consist of a text and an icon. Certain styles allow additional information to be displayed in columns to the right of the icon and label. ==Appearance== A [[ref:libraries/wel/reference/wel_list_view_chart|WEL_LIST_VIEW]] with the Lvs_report style.
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-line-edit.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-line-edit.wiki index 3841ada0..afd42194 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-line-edit.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-line-edit.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_MULTIPLE_LINE_EDIT]] [[Property:weight|4]] +[[Property:uuid|752a587f-4c17-f8bf-0f16-c0cf9f69bdc6]] A [[ref:libraries/wel/reference/wel_multiple_line_edit_chart|WEL_MULTIPLE_LINE_EDIT]] is used to display multiple lines of text. Using set_read_only, the text can be made non-editable. ==Appearance== diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-selection-list-box.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-selection-list-box.wiki index f5681d4a..897a46f0 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-selection-list-box.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-multiple-selection-list-box.wiki @@ -7,7 +7,7 @@ A [[ref:libraries/wel/reference/wel_multiple_selection_list_box_chart|WEL_MULTIP [[Image:wel-multiple-selection-list-box|wel_multiple_selection_list_box]]

-{{seealso| '''See also'''
+{{seealso|
[[WEL_SINGLE_SELECTION_LIST_BOX|WEL_SINGLE_SELECTION_LIST_BOX]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-owner-draw-button.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-owner-draw-button.wiki index a913552a..9014d819 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-owner-draw-button.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-owner-draw-button.wiki @@ -7,7 +7,7 @@ A [[ref:libraries/wel/reference/wel_owner_draw_button_chart|WEL_OWNER_DRAW_BUTTO There is no sample appearance for this control. -{{seealso| '''See also'''
+{{seealso|
[[WEL_PUSH_BUTTON|WEL_PUSH_BUTTON]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-progress-bar.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-progress-bar.wiki index 63c55ec8..2641836c 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-progress-bar.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-progress-bar.wiki @@ -3,7 +3,7 @@ [[Property:uuid|6c8b5b4c-2d55-9635-1c29-361c28f09b14]] A [[ref:libraries/wel/reference/wel_progress_bar_chart|WEL_PROGRESS_BAR]] control is an encapsulation of the Win32 progress bar. It can be used to display the progress of a lengthy operation. -{{note| '''Note:''' By specifying the style Pbs_vertical, the progress bar will be displayed vertically. }} +{{note|By specifying the style Pbs_vertical, the progress bar will be displayed vertically. }} ==Appearance== A [[ref:libraries/wel/reference/wel_progress_bar_chart|WEL_PROGRESS_BAR]] .
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-push-button.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-push-button.wiki index c5c1e239..301b97eb 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-push-button.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-push-button.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_PUSH_BUTTON]] [[Property:weight|8]] +[[Property:uuid|186eb349-b7c9-9944-285e-34dd9968c4e0]] A [[ref:libraries/wel/reference/wel_push_button_chart|WEL_PUSH_BUTTON]] is a control that the user can click to provide notification to the application. ==Appearance== [[Image:wel-push-button|wel_push_button]] diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-radio-button.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-radio-button.wiki index 7e032145..7e9dd4aa 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-radio-button.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-radio-button.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_RADIO_BUTTON]] [[Property:weight|9]] +[[Property:uuid|ce7c3bfb-7950-95fb-0f92-7e33abdefa3b]] A [[ref:libraries/wel/reference/wel_radio_button_chart|WEL_RADIO_BUTTON]] control can take two states, checked or unchecked. By placing more than one of these in a [[ref:libraries/wel/reference/wel_group_box_chart|WEL_GROUP_BOX]] , they will become grouped, and only one may be checked at once. ==Appearance== diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-scroll-bar.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-scroll-bar.wiki index 01be9cfa..22c7066a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-scroll-bar.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-scroll-bar.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_SCROLL_BAR]] [[Property:weight|10]] +[[Property:uuid|74da6cc8-0398-0b51-885b-d73b7ec104e0]] A [[ref:libraries/wel/reference/wel_scroll_bar_chart|WEL_SCROLL_BAR]] control is an encapsulation of the Windows scroll bar control and is often used to specify which portion of a large control that cannot be viewed completely, is currently visible. ==Appearance== diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-line-edit.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-line-edit.wiki index 6e2969de..cbaffbdf 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-line-edit.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-line-edit.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_SINGLE_LINE_EDIT]] [[Property:weight|11]] +[[Property:uuid|69694ef8-a422-7f46-d97b-d42a16bfe838]] A [[ref:libraries/wel/reference/wel_single_line_edit_chart|WEL_SINGLE_LINE_EDIT]] is a control used to input a single line of text. ==Appearance== [[Image:wel-single-line-edit|wel_single_line_edit]] diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-selection-list-box.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-selection-list-box.wiki index 7a7370e3..2bac9e9e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-selection-list-box.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-single-selection-list-box.wiki @@ -7,7 +7,7 @@ A [[ref:libraries/wel/reference/wel_single_selection_list_box_chart|WEL_SINGLE_S [[Image:wel-single-selection-list-box|wel_single_selection_list_box]]

-{{seealso| '''See also'''
+{{seealso|
[[WEL_MULTIPLE_SELECTION_LIST_BOX|WEL_MULTIPLE_SELECTION_LIST_BOX]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-tooltip.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-tooltip.wiki index 4cee355a..ec64c5dd 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-tooltip.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-tooltip.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_TOOLTIP]] [[Property:weight|13]] +[[Property:uuid|2eb53721-d1a8-cec0-5c6a-692e9dc58755]] A [[ref:libraries/wel/reference/wel_tooltip_chart|WEL_TOOLTIP]] is an encapsulation of the Win32 tooltip control, and controls pop-up windows which display text. Each tooltip may control multiple pop-up windows, which are added to the tooltip using add_tool. ==Appearance== [[Image:wel-tooltip|wel_tooltip]] diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-track-bar.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-track-bar.wiki index 968f62bf..c5dcefb8 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-track-bar.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/controls-cluster/wel-track-bar.wiki @@ -1,5 +1,6 @@ [[Property:title|WEL_TRACK_BAR]] [[Property:weight|14]] +[[Property:uuid|ceb2589f-4caf-686c-b19f-6f2769b0edcb]] A [[ref:libraries/wel/reference/wel_track_bar_chart|WEL_TRACK_BAR]] control has a sliding pointer and optional tick marks. ==Appearance== diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/index.wiki index 381f0bf9..42f9e245 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/index.wiki @@ -17,6 +17,3 @@ The WEL library includes the following clusters: * structs cluster which contains classes for data structures required by Win32 * support cluster which contains many supporting classes - - - diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/index.wiki index 3c4852cd..8342ad45 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/index.wiki @@ -1,5 +1,4 @@ -[[Property:title|Standard Dialogs]] -[[Property:link_title|stddlgs cluster]] +[[Property:title|stddlgs cluster]] [[Property:weight|2]] [[Property:uuid|0af8dcbf-ed31-51d7-885c-c677090f0633]] This cluster contains different standard dialogs provided by WEL. diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-color-dialog.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-color-dialog.wiki index 813f538c..daa12e2a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-color-dialog.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-color-dialog.wiki @@ -7,7 +7,7 @@ The [[ref:libraries/wel/reference/wel_choose_color_dialog_chart|WEL_CHOOSE_COLOR [[Image:wel-choose-color-dialog|wel_choose_color_dialog]]

-{{seealso| '''See also'''
+{{seealso|
[[stddlgs cluster|Standard dialogs]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-folder-dialog.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-folder-dialog.wiki index 2f4144b8..5c4850d2 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-folder-dialog.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-folder-dialog.wiki @@ -7,7 +7,7 @@ The [[ref:libraries/wel/reference/wel_choose_folder_dialog_chart|WEL_CHOOSE_FOLD [[Image:wel-choose-folder-dialog|wel_choose_folder_dialog]]

-{{seealso| '''See also'''
+{{seealso|
[[stddlgs cluster|Standard dialogs]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-font-dialog.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-font-dialog.wiki index e62cb7db..d2118f92 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-font-dialog.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-choose-font-dialog.wiki @@ -7,7 +7,7 @@ The [[ref:libraries/wel/reference/wel_choose_font_dialog_chart|WEL_CHOOSE_FONT_D [[Image:wel-choose-font-dialog|wel_choose_font_dialog]]

-{{seealso| '''See also'''
+{{seealso|
[[stddlgs cluster|Standard dialogs]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-open-file-dialog.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-open-file-dialog.wiki index 077a853f..374f0074 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-open-file-dialog.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-open-file-dialog.wiki @@ -7,7 +7,7 @@ The [[ref:libraries/wel/reference/wel_open_file_dialog_chart|WEL_OPEN_FILE_DIALO [[Image:wel-open-file-dialog|wel_open_file_dialoG]]

-{{seealso| '''See also'''
+{{seealso|
[[stddlgs cluster|Standard dialogs]]
[[WEL_SAVE_FILE_DIALOG|WEL_SAVE_FILE_DIALOG]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-print-dialog.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-print-dialog.wiki index ae44ce52..3758cda8 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-print-dialog.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-print-dialog.wiki @@ -7,7 +7,7 @@ The [[ref:libraries/wel/reference/wel_print_dialog_chart|WEL_PRINT_DIALOG]] is [[Image:wel-print-dialog|wel_print_dialog]]

-{{seealso| '''See also'''
+{{seealso|
[[stddlgs cluster|Standard dialogs]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-save-file-dialog.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-save-file-dialog.wiki index 860b4da4..bf8b1763 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-save-file-dialog.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/stddlgs-cluster/wel-save-file-dialog.wiki @@ -7,7 +7,7 @@ The [[ref:libraries/wel/reference/wel_save_file_dialog_chart|WEL_SAVE_FILE_DIALO [[Image:wel-save-file-dialog|wel_save_file_dialoG]]

-{{seealso| '''See also'''
+{{seealso|
[[stddlgs cluster|Standard dialogs]]
[[WEL_OPEN_FILE_DIALOG|WEL_OPEN_FILE_DIALOG]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/windows-cluster.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/windows-cluster.wiki index 1304b526..2ef9777f 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/windows-cluster.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-interface-content/windows-cluster.wiki @@ -14,7 +14,7 @@ The following effective window types are available: * [[ref:/libraries/wel/reference/wel_frame_window_chart|WEL_FRAME_WINDOW]] * [[ref:/libraries/wel/reference/wel_control_window_chart|WEL_CONTROL_WINDOW]] -{{note| '''Note:''' A WEL application must contain at least one window. See the [[WEL Tutorial]] for details of how to set up your first window within a [[ref:/libraries/wel/reference/wel_application_chart|WEL_APPLICATION]] . }} +{{note|A WEL application must contain at least one window. See the [[WEL Tutorial]] for details of how to set up your first window within a [[ref:/libraries/wel/reference/wel_application_chart|WEL_APPLICATION]] . }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/bmpview.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/bmpview.wiki index 63128637..6b77b88b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/bmpview.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/bmpview.wiki @@ -24,7 +24,7 @@ This sample contains the following classes: * CHILD_WINDOW * APPLICATION_IDS -{{seealso| '''See Also'''
+{{seealso|
[[WEL_OPEN_FILE_DIALOG|WEL_OPEN_FILE_DIALOG]]
[[MDI (Multiple Document Interface)|Mdi sample]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/brushes.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/brushes.wiki index fd3a585e..a6a66e62 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/brushes.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/brushes.wiki @@ -18,7 +18,7 @@ To compile the example: After launching the program you will see a window displayed containing three push buttons marked "Brushes", "Rectangles" and "3D". Clicking "Brushes" will open a new window demonstrating different brushes available. Clicking "Rectangles" will open a new window within which many different shaped and colored rectangles will be drawn. Clicking"3D" will open a new window demonstrating the use of multiple bitmaps for animation. ==Under the Hood== Each of the three windows that are opened from the programs MAIN_WINDOW inherit [[ref:libraries/wel/reference/wel_frame_window_chart|WEL_FRAME_WINDOW]] and contains code for generating their output. BRUSHES_DEMO redefines idle_action to force a re-draw on the applicable windows. -{{note| '''Note'''. If enable_idle_action is not called, then idle_action is never executed. }} +{{note|. If enable_idle_action is not called, then idle_action is never executed. }} This sample contains the following classes: * APPLICATION_IDS diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/commands.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/commands.wiki index d6c35ef9..0bfb80d6 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/commands.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/commands.wiki @@ -18,7 +18,7 @@ To compile the example: After launching the program, you will see a window displayed with a similar appearance to the one illustrated above. Please follow the instructions displayed in the window. ==Under the Hood== MAIN_DIALOG inherits [[ref:libraries/wel/reference/wel_main_dialog_chart|WEL_MAIN_DIALOG]] which provides the feature put_command, used to associate a [[ref:libraries/wel/reference/wel_command_chart|WEL_COMMAND]] to a Windows message received by the window. A [[ref:libraries/wel/reference/wel_command_chart|WEL_COMMAND]] contains a deferred feature, execute which is executed when the command is fired. SHOW_COMMAND_INFORMATION, SHOW_MOUSE_BUTTON_INFORMATION and SHOW_MOVE_INFORMATION all inherit [[ref:libraries/wel/reference/wel_command_chart|WEL_COMMAND]] . -{{note| '''Note '''execute has an argument of type ANY which is used to pass any additional information required. }} +{{note|execute has an argument of type ANY which is used to pass any additional information required. }} This sample contains the following classes: * APPLICATION_IDS diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/common-controls.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/common-controls.wiki index 520c07d2..05eed728 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/common-controls.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/common-controls.wiki @@ -1,5 +1,6 @@ [[Property:title|Common Controls]] [[Property:weight|-13]] +[[Property:uuid|d50d633a-2ba5-995e-637c-6694cee8bf55]] [[Image:comctrls|comctrls]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/controls-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/controls-sample.wiki index 8dc84c45..7f6f450d 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/controls-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/controls-sample.wiki @@ -26,7 +26,7 @@ This sample contains the following classes: * CONTROLS * MAIN_WINDOW -{{seealso| '''See Also'''
+{{seealso|
[[WEL_LIST_VIEW|WEL_LIST_VIEW]]
[[ref:/libraries/wel/reference/wel_combo_box_chart|WEL_COMBO_BOX]]
[[WEL_PUSH_BUTTON|WEL_PUSH_BUTTON]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/ctlcolor.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/ctlcolor.wiki index 61455e71..54c68ffd 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/ctlcolor.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/ctlcolor.wiki @@ -1,5 +1,6 @@ [[Property:title|Ctlcolor]] [[Property:weight|-10]] +[[Property:uuid|0f9f5155-1c21-dd20-4810-32c105eeb02a]] [[Image:ctlcolor|ctlcolor]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/cursors.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/cursors.wiki index 5e9eb7da..7bbf6c39 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/cursors.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/cursors.wiki @@ -1,5 +1,6 @@ [[Property:title|Cursors]] [[Property:weight|-9]] +[[Property:uuid|2f1abcdd-182f-3fdf-27b9-861d1c2e2167]] [[Image:cursors|cursors]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/disk-space.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/disk-space.wiki index 3ecc6a28..e79c0ed9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/disk-space.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/disk-space.wiki @@ -1,5 +1,6 @@ [[Property:title|Disk Space]] [[Property:weight|-8]] +[[Property:uuid|09c90710-45c8-f674-376c-30ed0da738cd]] [[Image:diskspace|diskspace]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fontenum.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fontenum.wiki index d2b44d98..fd5b2b74 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fontenum.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fontenum.wiki @@ -1,5 +1,6 @@ [[Property:title|Fontenum]] [[Property:weight|-7]] +[[Property:uuid|7dbb5e5c-3e00-e4f6-9fc6-29ba4f2476d9]] [[Image:fontenum|fontenum]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fun.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fun.wiki index b4548073..cb5bf3aa 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fun.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/fun.wiki @@ -1,5 +1,6 @@ [[Property:title|Fun]] [[Property:weight|-6]] +[[Property:uuid|ad05362e-76a3-db98-a58d-d49f9f2b5f2a]] [[Image:fun|fun]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/header-control.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/header-control.wiki index ea11a021..caa28fb5 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/header-control.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/header-control.wiki @@ -1,5 +1,6 @@ [[Property:title|Header Control]] [[Property:weight|-5]] +[[Property:uuid|9b2bee5f-8676-4f9f-c6e0-e00b44b3bef4]] [[Image:header-ctrl|header_ctrl]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki index afd64bea..08d2691b 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki @@ -37,7 +37,7 @@ This sample contains the following classes: * MAIN_WINDOW -{{seealso| '''See Also'''
+{{seealso|
[[Tutorial Step 3|Tutorial Step3]]
[[Common message hooks|Common message hooks]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/index.wiki index 3ad498d9..010fd334 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/index.wiki @@ -3,6 +3,6 @@ [[Property:uuid|f6df9869-52b7-0d10-dd0c-52796f631998]] There are a large number of samples provided with the WEL library, each designed to demonstrate different functionality. The samples available are listed below. -{{note| '''Note''': If you are new to WEL programming, the recommended place to start is the set of samples called the [[WEL Tutorial]]. }} +{{note|If you are new to WEL programming, the recommended place to start is the set of samples called the [[WEL Tutorial]]. }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/list-view.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/list-view.wiki index 6f7edef7..a64b8510 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/list-view.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/list-view.wiki @@ -30,7 +30,7 @@ This sample contains the following classes: * LISTVIEW_DEMO * APPLICATION_IDS -{{seealso| '''See Also'''
+{{seealso|
WEL_LIST_VIEW }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/magnify.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/magnify.wiki index d979447c..b6d9ae9a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/magnify.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/magnify.wiki @@ -1,5 +1,6 @@ [[Property:title|Magnify]] [[Property:weight|-2]] +[[Property:uuid|2c50fccc-2481-6f2d-d223-b4b246398636]] [[Image:magnify|MAGNIFY]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/mdi-multiple-document-interface.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/mdi-multiple-document-interface.wiki index e5239bc5..e9acc377 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/mdi-multiple-document-interface.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/mdi-multiple-document-interface.wiki @@ -23,7 +23,7 @@ This sample contains the following classes: * MAIN_WINDOW * MDI_DEMO -{{seealso| '''See Also'''
+{{seealso|
[[Bmpview|Bmpview]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/minimal.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/minimal.wiki index 6314c67c..dee53bf2 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/minimal.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/minimal.wiki @@ -22,7 +22,7 @@ This sample contains only one class: * MINIMAL_DEMO -{{seealso| '''See Also'''
+{{seealso|
[[Tutorial Step 1|tutorial step 1]]
[[ref:/libraries/wel/reference/wel_frame_window_chart|WEL_FRAME_WINDOW]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/pizza.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/pizza.wiki index e774ddf4..02357152 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/pizza.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/pizza.wiki @@ -1,5 +1,6 @@ [[Property:title|Pizza]] [[Property:weight|2]] +[[Property:uuid|5375fdad-ab5e-7f6e-ef44-a4f34d137231]] =Pizza Sample= [[Image:pizza|pizza]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/printer.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/printer.wiki index 01b65a82..8d36f706 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/printer.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/printer.wiki @@ -25,7 +25,7 @@ This sample contains the following classes: * MAIN_WINDOW * PRINTER_DEMO -{{seealso| '''See Also'''
+{{seealso|
[[WEL_PRINT_DIALOG|WEL_PRINT_DIALOG]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/rich-edit.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/rich-edit.wiki index abc3498f..4b7267b2 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/rich-edit.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/rich-edit.wiki @@ -28,7 +28,7 @@ This sample contains the following classes: * MAIN_WINDOW * RICHEDIT_DEMO -{{seealso| '''See Also'''
+{{seealso|
[[ref:/libraries/wel/reference/wel_rich_edit_chart|WEL_RICH_EDIT]]
[[WEL_PRINT_DIALOG|WEL_PRINT_DIALOG]]
[[WEL_SAVE_FILE_DIALOG|WEL_SAVE_FILE_DIALOG]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/split-area.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/split-area.wiki index 45f20484..2604a4f9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/split-area.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/split-area.wiki @@ -26,7 +26,7 @@ This sample contains the following classes: * WEL_SPLIT_AREA -{{seealso| '''See Also'''
+{{seealso|
[[ref:/libraries/wel/reference/wel_rich_edit_chart|WEL_RICH_EDIT]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/standard-dialogs-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/standard-dialogs-sample.wiki index 58098bd6..a83ce65d 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/standard-dialogs-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/standard-dialogs-sample.wiki @@ -23,7 +23,7 @@ This sample contains the following classes: * MAIN_WINDOW * STDDLG_DEMO -{{seealso| '''See Also'''
+{{seealso|
[[WEL_OPEN_FILE_DIALOG|WEL_OPEN_FILE_DIALOG]]
[[WEL_CHOOSE_FONT_DIALOG|WEL_CHOOSE_FONT_DIALOG]]
[[WEL_CHOOSE_COLOR_DIALOG|WEL_CHOOSE_COLOR_DIALOG]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/timer.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/timer.wiki index 957302a8..f0be5f88 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/timer.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/timer.wiki @@ -1,5 +1,6 @@ [[Property:title|Timer]] [[Property:weight|7]] +[[Property:uuid|ec5895ca-5d09-292f-f5dc-4787d3495bae]] [[Image:timer|timer]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/tree-view-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/tree-view-sample.wiki index 352ae725..3ffa2eb4 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/tree-view-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/tree-view-sample.wiki @@ -27,7 +27,7 @@ This sample contains the following classes: * TREEVIEW_DEMO * APPLICATION_IDS -{{seealso| '''See Also'''
+{{seealso|
[[ref:/libraries/wel/reference/wel_tree_view_chart|WEL_TREE_VIEW]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/unicode-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/unicode-sample.wiki index 1b10a846..75280aff 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/unicode-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/unicode-sample.wiki @@ -1,5 +1,4 @@ -[[Property:title|Wel Sample: Unicode]] -[[Property:link_title|Unicode Sample]] +[[Property:title|Unicode Sample]] [[Property:weight|9]] [[Property:uuid|9905de6c-3f13-1c31-2f8c-efddd71abc6d]] [[Image:unicode|unicode]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/wel-sample-menus.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/wel-sample-menus.wiki index e23ace55..522d066e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/wel-sample-menus.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/wel-sample-menus.wiki @@ -1,5 +1,6 @@ [[Property:title|Wel Sample: Menus]] [[Property:weight|0]] +[[Property:uuid|9cd62273-3624-fc6c-44d5-c42150d9b684]] [[Image:menus|menus]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/windows-sample.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/windows-sample.wiki index 5b72adce..00d87ef9 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/windows-sample.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/windows-sample.wiki @@ -1,5 +1,4 @@ -[[Property:title|Wel Sample: Windows]] -[[Property:link_title|Windows Sample]] +[[Property:title|Windows Sample]] [[Property:weight|10]] [[Property:uuid|3ace1338-c85b-c7d8-faaf-52e9fb4e157e]] [[Image:windows|windows]]
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xcell.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xcell.wiki index 63ed491b..2e864281 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xcell.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xcell.wiki @@ -1,5 +1,6 @@ [[Property:title|Xcell]] [[Property:weight|11]] +[[Property:uuid|b48ed2d1-d91f-e288-5705-7a6bfa612c29]] [[Image:xcell|xcell]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xy-co-ordinates.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xy-co-ordinates.wiki index 0d3d697a..b1a4deea 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xy-co-ordinates.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/xy-co-ordinates.wiki @@ -25,7 +25,7 @@ This sample contains the following classes: * MAIN_WINDOW -{{seealso| '''See Also'''
+{{seealso|
[[Tutorial Step 3|tutorial_step3]]
[[WEL_PUSH_BUTTON|WEL_PUSH_BUTTON]]
}} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/index.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/index.wiki index 424ea30c..2f6df39e 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/index.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/index.wiki @@ -1,5 +1,4 @@ -[[Property:title|Tutorial]] -[[Property:link_title|WEL Tutorial]] +[[Property:title|WEL Tutorial]] [[Property:weight|2]] [[Property:uuid|68faa545-c658-ad5e-ca6f-ab693a7aabf8]] WEL is shipped with a tutorial among its sample programs. This tutorial shows you how to develop a simple WEL application and contains eight different samples listed below: diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki index a636b5dc..7607fb54 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki @@ -27,7 +27,7 @@ Although this system does nothing except create and display a [[ref:/libraries/w This sample only contains one class, TUTORIAL_STEP1 which inherits [[ref:/libraries/wel/reference/wel_application_chart|WEL_APPLICATION]] and redefines main_window -{{seealso| '''See Also'''
+{{seealso|
[[Inheriting WEL_APPLICATION|Inheriting WEL application]]
[[Redefining main_window|Redefining main_window]] }} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-2.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-2.wiki index c3b4b11a..29efee42 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-2.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-2.wiki @@ -29,7 +29,7 @@ This sample contains the following classes: * MAIN_WINDOW -{{seealso| '''See Also'''
+{{seealso|
[[WEL Common Concepts|Common message hooks]]
}} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-3.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-3.wiki index 057408ec..d5c4765a 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-3.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-3.wiki @@ -27,7 +27,7 @@ This sample contains the following classes: * MAIN_WINDOW -{{seealso| '''See Also'''
+{{seealso|
[[Common message hooks|Common message hooks]]
}} diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-4.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-4.wiki index 0ff1ef09..555e1698 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-4.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-4.wiki @@ -19,7 +19,7 @@ This sample builds on the knowledge learned in the previous tutorials ( [[Tutori After launching the sample, you will see a [[ref:libraries/wel/reference/wel_frame_window_chart|WEL_FRAME_WINDOW]] displayed. By holding down the left mouse button, and moving the mouse (Within the client area of the window), you will be able to draw on the client area of the window. Pressing the right mouse button within the window will clear the client area of the window. ==Under the Hood== -This system is an improvement over tutorial [[Tutorial Step 3|step3]] and only uses WEL techniques demonstrated in previous [[Tutorial|tutorials]] to allow you to draw on the client DC of the window. +This system is an improvement over tutorial [[Tutorial Step 3|step3]] and only uses WEL techniques demonstrated in previous tutorials to allow you to draw on the client DC of the window. This sample contains the following classes: * TUTORIAL_STEP4 diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-5.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-5.wiki index b9797b07..2c2c613d 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-5.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-5.wiki @@ -1,5 +1,6 @@ [[Property:title|Tutorial Step 5]] [[Property:weight|4]] +[[Property:uuid|05145328-5d2a-4d48-68cc-746ddf66b68f]] The sample builds on tutorial [[Tutorial Step 4|step 4]] and also demonstrates the use of a [[ref:libraries/wel/reference/wel_modal_dialog_chart|WEL_MODAL_DIALOG]] . The output is shown below: [[Image:step5|step5]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-6.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-6.wiki index a1c82c8c..63f22342 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-6.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-6.wiki @@ -1,5 +1,6 @@ [[Property:title|Tutorial Step 6]] [[Property:weight|5]] +[[Property:uuid|90d557e1-c4a6-e6ff-ff19-95a44c99f0ae]] This sample builds on tutorial [[Tutorial Step 5|step 5]] by preventing the loss of the drawing when Windows re-draws the client area of the [[ref:libraries/wel/reference/wel_frame_window_chart|WEL_FRAME_WINDOW]] . The output is shown below: [[Image:step6|step6]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-7.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-7.wiki index 4ab4e382..529a69d6 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-7.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-7.wiki @@ -1,5 +1,6 @@ [[Property:title|Tutorial Step 7]] [[Property:weight|6]] +[[Property:uuid|751a492d-6902-838e-7468-38b67e40f4e2]] This sample builds on tutorial [[Tutorial Step 6|step 6]] , and also demonstrates the use of a [[ref:libraries/wel/reference/wel_menu_chart|WEL_MENU]] . The output is shown below: [[Image:step7|step7]]

diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-8.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-8.wiki index c2b5990d..b3bbaa66 100644 --- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-8.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-8.wiki @@ -30,7 +30,7 @@ This sample contains the following classes: * LINES * LINE -{{seealso| '''See Also'''
+{{seealso|
[[ref:/libraries/wel/reference/wel_save_file_dialog_chart|Save file dialog]]
[[ref:/libraries/wel/reference/wel_open_file_dialog_chart|Open file dialog]] }}