DumontEXE 0.0.1
Public Member Functions
winDumontEXE Class Reference

The Main Window is the main user interface screen for the application. It is implemented as a MIDI type window. More...

#include <DumontEXE.h>

Inherits MainWindow.

List of all members.

Public Member Functions

void readSettings ()
 Read Registry Settings
.
void RegisterServer (const QUuid &clsid, const QString &progid, const QString &description, const QString &serverType, const QString &serverPath)
 Register the COM server
.
 winDumontEXE ()
void writeSettings ()
 Write Registry Settings
.

Detailed Description

The Main Window is the main user interface screen for the application. It is implemented as a MIDI type window.

Definition at line 750 of file DumontEXE.h.


Constructor & Destructor Documentation

The constructor initializes the environment for the first application.

Definition at line 490 of file DumontEXE.cpp.


Member Function Documentation

void readSettings ( )

Read Registry Settings
.

This method is used internally upon creation of the window to restore settings from the system registry. The settings include window size and placement on the desktop, placement of docking windows and so on.

See the following for the actual registry root settings:
 #define ORG_DOMAIN  "Lorimark Solutions"
 #define APP_NAME    "DumontEXE"
See also:
writeSettings

Definition at line 542 of file DumontEXE.cpp.

void RegisterServer ( const QUuid &  clsid,
const QString &  progid,
const QString &  description,
const QString &  serverType,
const QString &  serverPath 
)

Register the COM server
.

This function registers the COM server in to the Windows Registry. The windows registry is what is used to hook various programs together through the COM subsystem.

When the vbScript program performs a function such as createObject("Dumont.EXE") it is calling upon the COM subsystem to establish a connection between the vbScript program and the other program. The registry is used to establish that connection.

When an object is created by name using "Dumont.EXE", for instance, the COM system looks into the registry for an HKEY_CLASSES_ROOT/Dumont.EXE entry. If it can find this entry it then it looks to a HKEY_CLASSES_ROOT/Dumont.EXE/CLSID entry to acquire the ClassID of the object. Then the COM system looks for a HKEY_CLASSES_ROOT/CLSID/{class id of the previous call} entry. If it can find that entry then it looks for LocalServer and RemoteServer and InprocServer values to get the name of the binary file that is to be loaded. With that information, Windows is able to load the program - whatever it may be, a DLL or EXE, it doesn't matter.

Depending on a loaded DLL or EXE different things happen. If the program is an EXE, then the EXE program is launched by the system. It is up to the EXE program (server) to hook itself (register itself) in to the COM subsystem. Once the server has hooked in, then the vbScript program can call upon functions contained within it.

The registry is set up as follows:

Windows Registry Definitions
  HKEY_CLASSES_ROOT
    CLSID
      {00000000-0000-0000-0000-000000000000}   // description
        LocalServer                            // serverPath
        ProgID                                 // progid
    progid                                     // description
      CLSID                                    // clsid

Here is a typical registry organization for the Dumont project:

Windows Registry Example
  HKEY_CLASSES_ROOT
    CLSID
      {C7860C20-9B6F-4f31-8293-31CB0C1799F0}   // Dumont Commence Application Extensions
        LocalServer                            // C:/commence/Dumont/Dumont.exe
        ProgID                                 // Dumont.EXE
    Dumont.EXE                                 // Dumont Commence Application Extensions
      CLSID                                    // {C7860C20-9B6F-4f31-8293-31CB0C1799F0}
Parameters:
clsidClassID of the COM component. This number acts as a cross-reference number between the Program ID and the CLSID.

progidProgram ID ~ This is the vbScript component Name.

descriptionThis has not real functional impact on the system, but is used inside the registry to help users browse the many registry settings.

serverTypeThe values here can be 'LocalServer', or 'InprocServer' or 'RemoteServer'.

serverPathThe path to the actual program

Definition at line 1435 of file DumontEXE.cpp.

void writeSettings ( )

Write Registry Settings
.

This method is used internally upon destruction of the window to store settings into the system registry.

See also:
readSettings

Definition at line 555 of file DumontEXE.cpp.


The documentation for this class was generated from the following files:
 All Classes Namespaces Functions Variables Enumerations Enumerator Properties




~ ~ ~ ~ ~ ~
Source Code without Comments is like a Cranberry Garland
without the berries. Comment your Code!
 
Commence Database User Support Group Forum
http://newsgroup.showoff-db.org/
~ ~ ~ ~ ~ ~
Author: Mark Petryk
Lorimark Solutions, LLC
mark@lorimarksolutions.com