MACROMEDIA DREAMWEAVER MX 2004-EXTENDING DREAMWEAVER Spécifications Page 459

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 504
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 458
C-level extensibility and the JavaScript interpreter 459
The following example shows how the MM_Init() function for the library myLibrary
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
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 librarys 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
MM_Environment structure.
NOTE
The library can be implemented in either C or C++, but the file that contains the MM_Init()
function and the
MM_STATE macro must be implemented in C. The C++ compiler garbles
function names, which makes it impossible for Dreamweaver to find the
MM_Init()
function.
Vue de la page 458
1 2 ... 454 455 456 457 458 459 460 461 462 463 464 ... 503 504

Commentaires sur ces manuels

Pas de commentaire