InfoViewer Plugin |
Dirk Möbius
Stephen Kost |
Introduction
Docking And Automatic Update
Frequently Asked Questions
Change Log
What's planned in the Future - TODO
License information
With the InfoViewer Plugin you can choose the preferred browser, that jEdit and assorted plugins use to display help or HTML documentation.
You can use an external browser like Firefox or Chrome, but the InfoViewer Plugin also contains a lightweight mini web-browser named InfoViewer, written in Java, utilizing builtin Swing capabilities.
InfoViewer, the lightweight mini web-browser, may be docked into jEdit's View. See Utilities>Global Options>Docking.
You can use this feature to create a two-pane layout: Dock InfoViewer to the right of the jEdit text area, making it a HTML preview pane of the current buffer. This makes jEdit similar to some well-known HTML editors.
Use the Auto-Update feature of InfoViewer to automatically update the preview pane on certain events, e.g.:
See Utilities>Global Options>Plugin Options>InfoViewer>Internal Browser for a list of options.
The built-in Swing web mini-browser, used by InfoViewer as well as the built-in HelpViewer, is circa 2003, and is for stright HTML3 only. Use an external browser if you need current things like HTML5 and JavaScript.
See Utilities - Global Options - Appearance, and select "HelpViewer/Browser font".
See Plugin Options>InfoViewer>Choose Browser. There is an option for "External browser". Enter any command in the field "External browser command".
Note: The string "$u" (without quotes) will be substituted by the URL to display. If you don't enter any "$u", the URL will be appended at the end of the command string.
In the "Edit Bookmarks" dialog, enter a new entry with dash ("-") as title.
You enabled the options "Update InfoViewer automatically" and "...periodically", but the InfoViewer pane doesn't seem to get updated when you edit the corresponding jEdit buffer.
This is a strange error. It only occurs, if the HTML document contains a Content-Type property, such as:
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
I'll have to investigate further, but it seems to be a bug in the Swing implementation. (That is, I can blame Sun for it ;-) There are two workarounds:
Copyright (c) 1999-2005 Dirk Möbius (dmoebius@gmx.net)