Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
swdev:howto:develop_a_noah_fitting_module [2010/08/06 15:51] smayr |
swdev:howto:develop_a_noah_fitting_module [2017/01/20 11:57] (current) smayr [Basic Steps] |
||
---|---|---|---|
Line 2: | Line 2: | ||
== Noah 2.0 Fitting Module == | == Noah 2.0 Fitting Module == | ||
+ | |||
=== Module Installation === | === Module Installation === | ||
* Internal Setup Program: Registering the module using the Moduleinstall.ocx Component. (Required) | * Internal Setup Program: Registering the module using the Moduleinstall.ocx Component. (Required) | ||
+ | |||
==== Internal Setup Program ==== | ==== Internal Setup Program ==== | ||
The installation is performed from within the Noah System | The installation is performed from within the Noah System | ||
Line 55: | Line 57: | ||
== Noah 3.0 Fitting Module == | == Noah 3.0 Fitting Module == | ||
+ | |||
=== Module Installation === | === Module Installation === | ||
Installation types: | Installation types: | ||
* External Setup Program: Registering the program using the module’s own Setup Program. (Required) | * External Setup Program: Registering the program using the module’s own Setup Program. (Required) | ||
* Internal Setup Program: Registering the module using the Moduleinstall.ocx Component. (Optional) | * Internal Setup Program: Registering the module using the Moduleinstall.ocx Component. (Optional) | ||
+ | |||
==== External Setup Program ==== | ==== External Setup Program ==== | ||
The module developer must program his own module setup program (for example, '' | The module developer must program his own module setup program (for example, '' | ||
Line 225: | Line 229: | ||
[Installation] | [Installation] | ||
InstallCmd2=setup.exe | InstallCmd2=setup.exe | ||
+ | |||
+ | | ||
==== Registry Keys ==== | ==== Registry Keys ==== | ||
- | Once a fitting module has been installed and registered in NOAH 3.0, these are the registry entries related to that module: | + | Once a NOAH 2.0 fitting module has been installed and registered in NOAH 3.0, these are the registry entries related to that module: |
<code delphi> | <code delphi> | ||
Windows Registry Editor Version 5.00 | Windows Registry Editor Version 5.00 | ||
Line 1322: | Line 1327: | ||
1. Create an icon file called '' | 1. Create an icon file called '' | ||
- | 2. Create a resource file '' | + | 2. Create a resource file '' |
<code delphi> | <code delphi> | ||
LOGO001 BITMAP " | LOGO001 BITMAP " | ||
Line 1358: | Line 1363: | ||
* Section 6.7.1 of the //NOAH Framework System Architecture Specification// | * Section 6.7.1 of the //NOAH Framework System Architecture Specification// | ||
* Section 3.2.5 "Sub Modules Object" | * Section 3.2.5 "Sub Modules Object" | ||
+ | |||
+ | == Tools == | ||
+ | * Install NOAH 3.x SDK | ||
+ | * Use Module Tester to test the fitting module. | ||
+ | * Login using: User initials: adm, Password: Noah30 | ||
+ | * No Login. Verify that the application icon properties have the " | ||
== Glossary == | == Glossary == | ||
+ | |||
====== ActiveX Document Server ====== | ====== ActiveX Document Server ====== | ||
An Automation Server that supports a number of specific interfaces (IPersistStorage, | An Automation Server that supports a number of specific interfaces (IPersistStorage, |