Doesn't seem likely to be possible. (The application makes use of Raize Components - a $399 add-on with a bunch of custom controls.)
Getting sick of clicking each cell individually yet? XD
If you have a close look at the text-preview window, you can see that there are only 7 vertical pixels. A 1602 of course uses character matrices that are 5x8. They also have a 1 cell gap between each row and between each letter within a row.
It seems that the help for the components are only available if you buy/try them. Only thing is, I haven't programmed in Pascal since the late 90s - but more importantly, it's a 70MB download that wont work with my (ancient) copy of TPW 1.5 - I'm not downloading a 70mb trial just in the hope I'll get the docs.
I've spent a few hours at night over the past week making a couple of native solutions. Both in win32 c (windows or wine only) and wxWidgets c++ (linux, mac, win). If it gives me enough of a kick, I'll crank out a version using MASM too.
Which brings me back to the whole reason I used html5 + javascript in the first place. It's immediately portable - requiring only a html5-capable browser. It's perfectly fine to distribute a single file that constitutes both the application and the source-code. It also means I don't have to go near the horror-show that is Java in order to run it on an Android phone.
The funny thing is, the html version may well end-up being the smallest. Ha! It's 4.7kb, with a dependancy of the browser. The ASM version will be next, likely weighing in at under 10kb without compression - with zero dependancies. Following that is the win32 C version, that is currently running at about 22kb with 1 or 2 small (sub 100kb) deps. Coming in lucky last are the wxWidgets versions - about 60kb on the Raspberry Pi, 70kb on Linux Mint x64 (dependencies installed in each by default, I think) and a whopping 1.88MB using the static-build of wx under windows. I really should get around to building a dll version of that library..
I'd vaguely considered adding the ability to define an entire font, which would come in far more useful when using a 128x160 lcd.
But currently, learning my way around wxWidgets enough to handle text-input operations in the output preview window. I'm vaguely considering making the lcd control itself editable - i.e you can click a cell to position a cursor there - editing with the keyboard in situ, rather than by a seperate edit window. But then again, I've also considered making the lcdPanel have the same member functions that the LiquidCrystal class does for positioning, custom char definition and text output. That would make a simple 'call' to lcd.print(0) --> lcd.print(7) show any of the custom chars.
Hmm. Actually, as I write this, I may have an idea.
This project is a perfect example of the 80/20 rule in play. You get 80% of the benefit for 20% of the effort. The html one isn't so nice looking, but like I said earlier - I smashed it together during the course of a lunch hour.
I've said it before offline and I'll say it again - the idea to include a preview window was really clever, and one that really dresses up the application.
I wouldv'e left my project gathering dust had it not been for the idea of a preview screen.
Anyway, I'm rambling. I only answer (instead of Aaron) since it looks like he may not be particularly keen to revisit this thread. He or someone else certainly deleted his last post, which was quite an er... ah, 'entertaining' read.