source: trunk/doc/html/netscape-plugin.html@ 190

Last change on this file since 190 was 190, checked in by rudi, 14 years ago

reference documentation added

File size: 5.4 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/extensions/nsplugin/doc/index.doc:14 -->
3<html>
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
6<title>Qt Netscape Plugin Extension</title>
7<style type="text/css"><!--
8fn { margin-left: 1cm; text-indent: -1cm; }
9a:link { color: #004faf; text-decoration: none }
10a:visited { color: #672967; text-decoration: none }
11body { background: #ffffff; color: black; }
12--></style>
13</head>
14<body>
15
16<table border="0" cellpadding="0" cellspacing="0" width="100%">
17<tr bgcolor="#E5E5E5">
18<td valign=center>
19 <a href="index.html">
20<font color="#004faf">Home</font></a>
21 | <a href="classes.html">
22<font color="#004faf">All&nbsp;Classes</font></a>
23 | <a href="mainclasses.html">
24<font color="#004faf">Main&nbsp;Classes</font></a>
25 | <a href="annotated.html">
26<font color="#004faf">Annotated</font></a>
27 | <a href="groups.html">
28<font color="#004faf">Grouped&nbsp;Classes</font></a>
29 | <a href="functions.html">
30<font color="#004faf">Functions</font></a>
31</td>
32<td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Qt Netscape Plugin Extension</h1>
33
34
35<p> <!-- index Netscape --><a name="Netscape"></a>
36<p> The Qt Netscape Plugin software makes it easy to write browser plugins
37that can be used on both Unix/Linux and MS-Windows, in Netscape,
38Mozilla, and any other web browser supporting Netscape's LiveConnect
39protocol. Modern versions of MSIE do not support this protocol. Use
40the <a href="activeqt.html#ActiveQt">ActiveQt</a> Framework to develop plugins for these browsers.
41<p> <h2> Information
42</h2>
43<a name="1"></a><p> The Netscape Plugin Extension consists of the follow classes:
44<ul>
45<li> <a href="qnplugin.html">QNPlugin</a>
46<li> <a href="qnpinstance.html">QNPInstance</a>
47<li> <a href="qnpwidget.html">QNPWidget</a>
48<li> <a href="qnpstream.html">QNPStream</a>
49</ul>
50<p> <h2> How-to
51</h2>
52<a name="2"></a><p> <ol type=1>
53<li> Download the
54<a href="http://home.netscape.com/comprod/development_partners/plugin_api/index.html">Plugin SDK from Netscape</a>, and copy the following files from there to
55<tt>$QTDIR/extensions/nsplugin/src</tt>
56<ul>
57<li> <tt>common/npwin.cpp</tt>
58<li> <tt>common/npunix.c</tt>
59<li> <tt>include/npapi.h</tt>
60<li> <tt>include/npupp.h</tt>
61<li> <tt>include/jri.h</tt>
62<li> <tt>include/jri_md.h</tt>
63<li> <tt>include/jritypes.h</tt>
64</ul>
65<li> Build the Netscape Plugin extension library, found in the
66<tt>extensions/nsplugin/src</tt> directory of your Qt distribution.
67This produces a static library to be linked with your plugin code.
68<li> Read the <a href="qnplugin.html">plugin class documentation</a>, and
69examine the <a href="nsplugin-examples.html">example plugins</a>.
70<li> Do most of your development as a stand-alone Qt application - debugging
71Netscape Plugins is cumbersome. You may want to use <tt>signal(2)</tt>
72in your plugin to enable core-dumps if your browser disables them.
73<li> Note the platform-specific build steps below.
74<li> Read about the raw plugin interface
75<a href="http://developer.netscape.com/docs/manuals/communicator/plugin/index.htm">in Netscape's handbook.</a>
76<li> If files viewed by a plugin are provided by an HTTP server
77(using a <a href="http://...">http://...</a> URL) then
78the server must be configured to send the correct MIME type
79for the file, e.g. by editing Apache's <tt>mime.types</tt> file.
80If the files are viewed via a <a href="file://...">//...</a>
81URL, then the browser will use the filename extension to decide
82the file type (and hence the plugin to load) - the user may need
83to set the filename extension in the Helpers or Applications
84section of their browser preferences.
85</ol>
86<p> <h3> Building under X11
87</h3>
88<a name="2-1"></a><p> <ul>
89<li> The Makefiles in the examples are appropriate for UNIX/X11.
90<li> The user must install the resulting Shared Object in the Plugins
91directory of the browser.
92</ul>
93<p> <h3> Building under Windows
94</h3>
95<a name="2-2"></a><p> <ul>
96<li> For Netscape plugins to work, Qt needs to be in the system DLL
97path or be compiled into the plugin as a static library.
98<li> Plugins must be named <tt>np</tt><em>name</em><tt>.dll</tt>,
99or the browser will ignore them.
100<li> The link step must include:
101<ul>
102<li> <tt>/def:</tt><em>name</em><tt>.def</tt>
103<li> <tt>/dll</tt>
104<li> a compiled resource file defining the
105file/MIME types accepted by the plugin.
106</ul>
107<li> The user must install the resulting DLL in the Plugins directory
108of the browser.
109</ul>
110<p> <h2> Known Bugs and Limitations
111</h2>
112<a name="3"></a><p> The Qt-based LiveConnect Plugin binding code has a number of bugs and
113limitations, but is sufficiently stable for many production
114applications.
115<p> <ul>
116<li> Keyboard input only works in secondary windows (e.g. dialogs created by the plugin).
117<li> You should not expect modality between the plugin and the browser to work.
118<li> Netscape 4.78 on Unix/X11 tends to terminate with a bus error.
119<li> Opaque resize behaviour is erratic due to browser behavior.
120</ul>
121<p>
122<!-- eof -->
123<p><address><hr><div align=center>
124<table width=100% cellspacing=0 border=0><tr>
125<td>Copyright &copy; 2007
126<a href="troll.html">Trolltech</a><td align=center><a href="trademarks.html">Trademarks</a>
127<td align=right><div align=right>Qt 3.3.8</div>
128</table></div></address></body>
129</html>
Note: See TracBrowser for help on using the repository browser.