Mike,

It does sound reasonable, provided that you not only look into printing, but actually make it available (sans classes stuff sounds fine).

I thought that one of the advantages of HTML was that one could go back/forth between "WEB" or "regular" rather easily.

I also hope that you indicate in some way those methods which have code and those which are empty (for user usage) as well as the "default" behaviour of each.

Jim N

>Thanks Jim.
>
>FWIW, for the new version of VFE we're using Rick Strahl's HTML help builder to produce the doc, which BTW, is an absolutely fabulous tool. Right now we've got over 3000 topics and I would suspect the final number will be around 3500. That's a lot of paper! The HTML help does print out quite nicely and we're not planning on shipping printed documentation. One of the problems with providing printed docs at the stage where we're at is it would be a very large undertaking to convert the HTML help into a format that a printer could deal with. After we release we will probably look into it though. We would probably omit the class library documentation from the printed version for a couple of reasons. 1st, there's a single topic for each custom property and method of each class, which means that there would be a great deal of white space and lots of pages with very little content in printed format (without doing a great deal of typesetting work in advance. 2nd, and more important, the class
>documentation is subject to change with each update. We actually wrote a utility to produce all of the class documentation based on comments, descriptions in the classes, etc. and plan on updating this section with each new release, which would make the paper version obsolete very shortly. Does this sound reasonable to you?