The following example shows how the
might look:
void
MM_Init()
{
JS_DefineFunction("readContentsOfFile", readContentsOfFile, 1);
}
Your library must include exactly one instance of the following macro:
/* MM_STATE is a macro that expands to some definitions that are
* needed to interact with Dreamweaver. This macro must
* be defined exactly once in your library. */
MM_STATE
The library can be implemented in either C or C++, but the file that contains the
function and the
function names, which makes it impossible for Dreamweaver to find the
function.
C-level extensibility and the JavaScript
interpreter
The C code in your library must interact with the Dreamweaver JavaScript interpreter at the
following different times:
At startup, to register the library's functions
When the function is called, to parse the arguments that JavaScript is passing to C
Before the function returns, to package the return value
To accomplish these tasks, the interpreter defines several data types and exposes an API.
Definitions for the data types and functions that are listed in this section appear in the
mm_jsapi.h file. For your library to work properly, you must include the mm_jsapi.h file with
the following line at the top of each file in your library:
#include "mm_jsapi.h"
Including the mm_jsapi.h file includes, in turn, mm_jsapi_environment.h, which defines the
structure.
MM_Environment
MM_Init()
macro must be implemented in C. The C++ compiler garbles
MM_STATE
function for the library
C-level extensibility and the JavaScript interpreter
myLibrary
MM_Init()
MM_Init()
459
Need help?
Do you have a question about the DREAMWEAVER 8-EXTENDING DREAMWEAVER and is the answer not in the manual?