Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
swdev:howto:develop_a_noah_fitting_module [2010/08/12 11:15]
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, ''Setup.exe'') to register module data with the //Module Installation Server// component.    The module developer must program his own module setup program (for example, ''Setup.exe'') to register module data with the //Module Installation Server// component.   
Line 225: Line 229:
   [Installation]    [Installation] 
   InstallCmd2=setup.exe   InstallCmd2=setup.exe
 +  
 +  
 ==== Registry Keys ==== ==== Registry Keys ====
 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: 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:
Line 1321: Line 1327:
 1. Create an icon file called ''logo16.bmp'' (16 colors Windows Bitmap) and ''logo256.bmp'' (256 colors Windows Bitmap).  Each module must provide its icon, or logo, to NOAH upon installation. The icon must be 88x40 pixels (some other documentation specifies 90x40 pixels) and may use up to 256 colors. 1. Create an icon file called ''logo16.bmp'' (16 colors Windows Bitmap) and ''logo256.bmp'' (256 colors Windows Bitmap).  Each module must provide its icon, or logo, to NOAH upon installation. The icon must be 88x40 pixels (some other documentation specifies 90x40 pixels) and may use up to 256 colors.
  
-2. Create a resource file ''LogoRes.RC'':+2. Create a resource file ''LogoRes.RC''.   NOTE: Do not ''#define'' the ''LOGO001'' and ''LOGO002'' resources because it then does not register the correct icon in Noah. Create file as follows:
 <code delphi> <code delphi>
 LOGO001 BITMAP "logo16.bmp" LOGO001 BITMAP "logo16.bmp"
Line 1360: Line 1366:
 == Tools == == Tools ==
   * Install NOAH 3.x SDK   * Install NOAH 3.x SDK
-  * Use Module Tester to test the fitting module. Verify that the application icon properties have the "nologin" option: <code>"C:\Program Files\HIMSA\NOAH 3.0 SDK\Tools\Module Tester\MODULETESTER.EXE" /nologin</code>+  * 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 "nologin" option to run without having to login: <code>"C:\Program Files\HIMSA\NOAH 3.0 SDK\Tools\Module Tester\MODULETESTER.EXE" /nologin</code>
  
 == Glossary == == Glossary ==
 +
 ====== ActiveX Document Server ====== ====== ActiveX Document Server ======
 An Automation Server that supports a number of specific interfaces (IPersistStorage, IPersistFile, IOleObject, IDataObject, IOleInPlaceObject, IOleInPlaceActiveObject, IOleDocument, IOleDocumentView, IOleCommandTarget (optional), IPrint (Optional)). It is made up of frames, documents and views. ((Teixeira, Steve. //COM Corner: ActiveX Documents, Part 1//.  The Delphi Magazine, February 1999.)) An Automation Server that supports a number of specific interfaces (IPersistStorage, IPersistFile, IOleObject, IDataObject, IOleInPlaceObject, IOleInPlaceActiveObject, IOleDocument, IOleDocumentView, IOleCommandTarget (optional), IPrint (Optional)). It is made up of frames, documents and views. ((Teixeira, Steve. //COM Corner: ActiveX Documents, Part 1//.  The Delphi Magazine, February 1999.))