Configuration Directives

Server Directives
Client Directives
• ActiveX
• DefaultIconPath
• ExternalObject
• InitialUrl
• Java
• Scripting
Window Directives
Menu Directives
System Tray Directives

These directives controls the "client-side" behaviors of Wapache.

ActiveX
Description: Determines whether the web browser can load ActiveX controls
Syntax: ActiveX On|Off
Default: ActiveX On
Context: server config

By default ActiveX is enabled in Wapache. If your application does not make use of ActiveX technology, you may choose to turn it off.

Not all ActiveX controls will work properly in Wapache. Those that bypass Windows's Internet service and implement their HTTP own retrieval mechanism will not work.

If an ActiveX control is not already installed, Wapache will prompt the user to install it in a dialog box, just as it happens in Internet Explorer. The codebase attribute of the object tag must point to a file served by Wapache. A remote location (e.g. http://download.macromedia.com/.../swflash.cab) will not work.

Warning: An ActiveX control installed through Wapache will become available in Internet Explorer as well. Do not create a control that gives you full access to the computer.
DefaultIconPath
Description: Specifies the path to the default icon file
Syntax: DefaultIconPath ico-file-path
Default: DefaultIconPath (none)
Context: server config

This directive specifies the icon that appears at the upper right-hand corner of windows, in the Task Bar, the Task Switch window, and the System Tray. You can assign a specific icon to a window using the IconPath directive in a <StandardWindow> section.

Windows XP: When the Task Bar collapses multiple buttons into a single "program group" button, it obtains the icon and application name from the resource data stored in the executable file. To customize them, you need to use a Win32 resource editor.
ExternalObject
Description: Determines whether the external object is available for scripting in the web browser
Syntax: ExternalObject On|Off
Default: ExternalObject Off
Context: server config

The window.external object in Wapache provide extra functionalities to the scripting environment normally not available in a web browser. By default this is disabled. Use this directive to enable it if you need these functionalities in your appplication. See the External Object documentation for more information.

Warning: Among the things you can do through the external object is starting a program. Understand the security implicition before turning it on, especially if your application is going to display contents retrieved from the web.
InitialUrl
Description: Adds to the list of URLs that the program navigates to when it starts
Syntax: InitialUrl opener url [target]
Context: server config

Your application will likely have at least one InitialUrl statement. Otherwise no window will appear when the program starts. The program will exit immediately exit in that case–unless it has a System Tray icon.

The URLs are open in the order as they appear in the configuration file. The first InitialUrl statement should have an opener of _app, a special window name indicating the application. The target parameter provides the name of the window. Wapache uses the window name to look up its settings (height, width, etc), so it is recommended that you always provide one even through it is optional.

Example:

# open the main window
InitialUrl _app http://localhost/index.php main

# open the toolbox window
InitialUrl main http://localhost/tools.php tool

Tool windows and dialog boxes are positioned relative to their opener, so for them, it's important that the correct opener is specified.

Java
Description: Determines whether the web browser can run Java applets
Syntax: Java On|Off
Default: Java On
Context: server config

Java is enabled by default. Java applets embedded in HTML pages will only work, however, if the end user had installed the Java Runtime Environment on his/her computer.

Scripting
Description: Determines whether the web browser can run Javascript and VBScript
Syntax: Scripting On|Off
Default: Scripting On
Context: server config

Javascript and VBScript are available for use in HTML pages by default. Use this directive to turn it off if your application does not need them.

Scripting availability in Wapache is independent of Internet Explorer's settings. Even if the user has disable Active Scripting in Control Panel > Internet Options > Security, Javascript will still be available.