|
|
|
WebRenderer
Swing Edition supports many third-party plugins through standard
browser plugin architecture.
An example of a third-party
plugin that runs with WebRenderer is Macromedia Flash. Flash should
work with the Swing Edition if it is set up to run in Firefox, as
WebRenderer Swing Edition utilizes the plugin finder from the Mozilla
engine to detect the Flash plugin.
However the following
steps can be taken if the Flash or other plugins are not functioning:
1.
Un-jar the corecomponents-swing-xxx.jar 2. add Flash plugin files
(download and extract the Flash plugin) to the corecomponents/plugins
directory 3. JAR the 'corecomponents' directory back-up creating
a new version of corecomponents-swing-xxx.jar
The Flash plugin
will now deploy within WebRenderer Mozilla instance.
Please
note; if you have already run WebRenderer then the corecomponents-swing-xxx.jar
will not extract and run with your plugin, and you therefore have
to force WebRenderer to extract these. This can be done by altering
the versionxxxx ("xxxx" denotes the version number) and
calling the BrowserFactory setCorecomponentsExtractOn method.
Example:
1)
Alter the versionxxxx filename to mycustomdeploy 2) Call BrowserFactory.setCorecomponentsExtractOn("mycustomdeploy");
The
corecomponents-swing-xxx.jar will now deploy with your plugin. The
corecomponents-swing-xxx.jar will only extract if it does not find
the versionxxxx file (in the example "mycustomdeploy"),
thus preventing performance penalties (a slight delay on start-up)
encountered with the extraction process.
An alternative
to the above instructions is to place the plugin into the WebRenderer
profile directory located at:
<user home>/.webrendererswing/<platform>/corecomponents/plugins
Although
third party plugins can be used with WebRenderer we cannot make
any assurances regarding the quality of third party plugins or the
interoperability with WebRenderer.
|