JDisplay

JDisplay displays Java, HTML, bat, SQL, ini, csv, xml, mft

properties... files a variety of colours, fonts, sizes

and weights to help make them more presentable and readable.

Why would you use it? For the same sorts of reasons you use

colours and fonts in an IDE like IntelliJ or Eclipse. They

make the code much easier to understand.

There is no server-side code used. Java utilities parse the

code snippets into compact binary tokens, assigning colours,

fonts, sizes and weights to each token. Then the tokens can

be rendered three ways:

1. using a Java Applet. This is usually best for very

large listings.

2. as piece of CSS style-decorated HTML code you include in

your html as an iframe. This is usually best for

intermediate listings.

3. inline in your HTML. This is usually best for short

listings. The problem, in the process of editing the html

it is fairly easy to damage the generated listings. They

must be regenerated before every upload.

I have been using the JDisplay suite of utilities for many

years. I did not write it for public use. I offer it on an

as-is basis. The code itself in well documented, but there

is no step-by-step documentation on getting it to work.

I presume the user is familiar with bat and ant files and

Java building.

I have not included the enormous HTML static macros package

which I use for deciding the sizes and display rendering

method for each snippet, though I did include the code to

make those decisions hooked into your own framework.

The parsers are rough and ready. They need to work on code

snippets and erroneous code, not perfect code the way a

standard parser does. If improve the parsers, or add new

ones, please pass them along for the public distribution.

JDisplay is enormously more complicated than it appears on

the surface. You can spelunk and discover all manner of

interesting code you can cannibalise.