Comparison of Platforms on Size
The table below shows
- The additional functions and bytes of wssize required for each platform
(over the base of 82 fns & .5mb of common utilities).
- LinePrinter requires 111 additional fns adding .6 mb to wssize.
- NewLeaf requires 296 additional fns adding .9 mb to wssize.
- Phoenix (as yet not complete) requires 34 additional fns adding .2 mb to wssize.
- HTML requires 162 additional fns adding .7 mb to wssize.
- If fns for all 4 platforms are in the ws,
then 438 fns are added for a total of 520 fns and 1.5 mb are added to wssize.
- Most of the test datasets run on the NewLeaf and HTML compilers.
The presence of a number in the table below indicates the document can be rendered in the platform
represented by that column. The number is the size of the document; e.g.
the Mucky Duck document is 43528 chars in NewLeaf and 60689 chars in HTML.
PDF is an especially attractive report format, so we've chosen it for evaluation of our rendering engines.
All PDF documents linked in the menu below show what is intended in a reasonably good manner.
The documents with a question mark (?) have one or more aspects where we'd like to see improvement
in the rendering engine.
While only the PDF and HTML versions of documents are shown here,
the workspace pvPlayer available on a CD will enable one to see renderings for all platforms.
To see tables with quantitative data, click on the links with an asterisk.
It is important to remember that each of these documents rendered on multiple platforms
uses exactly the same source arrays. Knowledge of any software
helps in its use. One of these documents was rendered
by Jonathan Manktelow using NewLeaf,
allowing for an interesting comparison of his version with the document rendered
by pvPlayer using NewLeaf. This will provide ideas for improvements to pvPlayer.
Of the 6 documents that illustrate more work needed, here's an initial analysis of what improvements are needed.
- JobsNeeded -- improve source data (can we write a "cleansing" function).
- RenVill -- improve source data.
- RMSitePlan -- figure out how to make NewLeaf handle lists & font sizes.
- RenaVillLN -- improve source data, figure out how to make NewLeaf measure row titles.
- RenVill2 -- improve source data, figure out how to make NewLeaf measure row titles.
- SGSitePlan -- prepare data so NewLeaf will properly handle a list, figure out how to handle the following in NewLeaf: links, "break", e-mail address encoding.