See: Description
Interface | Description |
---|---|
BookDataDisplay |
An interface for all components that can display BookData.
|
URIEventListener |
Implement URIEventListener to receive URIEvents whenever someone activates an
URI.
|
Class | Description |
---|---|
BookDataDisplayFactory |
Factory for OSIS renderers.
|
ProxyBookDataDisplay |
An implementation of BookDataDisplay that simply proxies all requests to an
underlying BookDataDisplay.
|
ScrolledBookDataDisplay |
An inner component of Passage pane that can't show the list.
|
URIEvent |
A URIEvent happens whenever a user selects a URI.
|
JRex (Embed Mozilla)
Very good html displayer, but probably very complex to get working and
installed, especially over WebStart. JNI+webstart anyone?
See mozdev.
Jazilla (Mozilla re-write in Java)
Interesting project, but one that seems more interested in XUL than the Java
renderer, proceeding slowly.
See their home page.
JXWB (OSS Java Browser)
Commercial software made free. Works well with Swing (includes customized
implementations of javax.swing.text.Document and javax.swing.text.EditorKit)
Things have moved on quite a bit recently.
See JXWB on SourceForge
SWT Browser Component
Don't think we could easily embed an SWT component in swing (since SWT is
heavyweight in AWT speak) and I don't particularly want to re-write the whole
app in SWT. However there are 2 projects to allow use of SWT from a swing API.
SwingWT is a swing-like proxy to
SWT and MasterCL
will allow you to dynamically swap package names to make the whole of swing use
SWT dynamically.
It is possible to use SWT from webstart -
irate radio does it although their build
scripts are not very helpful.
FOP -> PNG
FOP is XSL:FO renderer that can create PDFs and various graphics files.
Could give very slick output, but not at all dynamic, quite slow and FO is not
easy to use. Probably not one of the best ideas for normal rendering.
See FOP at Apache.
Dynamic Swing GUI
There are plenty of XML->Swing converters. JDK 1.4 even includes one.
Maybe we could write a OSIS->SwingXML converter in XSL and then render OSIS
text in swing components. Could be very fancy. XSL could be complex.