From f8727daf08dd0feed34872b5ef6160459d6842f1 Mon Sep 17 00:00:00 2001 From: "av%netscape.com" Date: Thu, 6 Dec 2001 02:52:06 +0000 Subject: [PATCH] Updating readme file for the Plugin SDK -- not part of the build git-svn-id: svn://10.0.0.236/trunk@109792 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/modules/plugin/tools/sdk/readme.txt | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/mozilla/modules/plugin/tools/sdk/readme.txt b/mozilla/modules/plugin/tools/sdk/readme.txt index 58b07491b16..68973c08012 100644 --- a/mozilla/modules/plugin/tools/sdk/readme.txt +++ b/mozilla/modules/plugin/tools/sdk/readme.txt @@ -1,4 +1,4 @@ -Last updated 10.02.2001 +Last updated 12.05.2001 The current version of the Netscape Plugin API is designed to help the developers to start creating plugins for Mozilla based browsers. @@ -15,10 +15,12 @@ The SDK is intended to help in creating full-blown plugins to work with Mozilla code base without actually having the whole Mozilla source tree present and built. +=============================================================== + The Common folder contains stub implementations of the NPAPI methods, there is no need to modify files in this folder, just include them into your project. This is not necessary though, some samples or plugin projects may use -there own implementations, the files in this folder are just an illustration +their own implementations, the files in this folder are just an illustration of one possible way to do that. The Samples section at this point contains the following plugin samples: @@ -36,7 +38,7 @@ This plugin example illustrates specific for Mozilla code base features. It is scriptable via JavaScript and uses services provided by the browser. Some xpcom interfaces are implemented here so the Mozilla browser is aware of its capabilities. The plugin does not draw in the native window but -rather JavaScript box is used to display the result of its work. Therefore, +rather uses JavaScript box to display the result of its work. Therefore, there are no separate projects for different platforms in this sample. 3. Scriptable plugin @@ -48,4 +50,11 @@ Scriptable samples require generation of .xpt files which should reside in the Mozilla Components directory. To make sure Mozilla is aware of the presence of the new .xpt file one may look at xpti.dat. To force Mozilla to re-scan the Components directory xpti.dat should be removed -before Mozilla is started. \ No newline at end of file +before Mozilla is started. + +=============================================================== + +Plugin developers might find it useful for debugging purporsed to turn +off the exeption catching mechanism currently implemented in Mozilla +on Windows. To do this add the following line into your prefs.js file: +user_pref("plugin.dont_try_safe_calls", true);