JDisplay displays Java, HTML, bat, SQL, ini, csv,properties... files a variety of colours, fonts, sizesand weights to help make them more presentable and readable.Why would you use it? For the same sorts of reasons you usecolours and fonts in an IDE like IntelliJ or Eclipse. Theymake the code much easier to understand.There is no server-side code used. Java utilities parse thecode snippets into compact binary tokens, assigning colours,fonts, sizes and weights to each token. Then the tokens canbe rendered three ways:1. using a Java Applet. This is usually best for verylarge listings.2. as piece of CSS style-decorated HTML code you include inyour html as an iframe. This is usually best forintermediate listings.3. inline in your HTML. This is usually best for shortlistings. The problem, in the process of editing the htmlit is fairly easy to damage the generated listings. Theymust be regenerated before every upload.I have been using the JDisplay suite of utilities for manyyears. I did not write it for public use. I offer it on anas-is basis. The code itself in well documented, but thereis no step-by-step documentation on getting it to work.I presume the user is familiar with bat and ant files andJava building.I have not included the enormous HTML static macros packagewhich I use for deciding the sizes and display renderingmethod for each snippet, though I did include the code tomake those decisions hooked into your own framework.The parsers are rough and ready. They need to work on codesnippets and erroneous code, not perfect code the way astandard parser does. If improve the parsers, or add newones, please pass them along for the public distribution.JDisplay is enormously more complicated than it appears onthe surface. You can spelunk and discover all manner ofinteresting code you can cannibalise.