You only have to rewrite your code if you have written code to begin with...
We thought about making a report generation toolkit plugin, so the report generation functions can be used to print a PDF. But this would invole changing standard LabVIEW VI's and enums. Perhaps the interface is even copyright protected. Also, the things the PDF format can do are very advanced compared to the HTML toolkit, and I didn't want this limitation. (If you can live with these limits, why pay for it if you have the HTML reports for free?)
I use a PDF printer myself to store word document in PDF files. I don't claim that this toolkit is a replacement for it. But if you want to make more advanced PDF files with LabVIEW, it is a good solution. If you only need a PDF with a front panel or two, I'd use CutePDF too.
As an example (perhaps I'm mistaken, I've never found a way to do this)... Printing to HTML has the disadvantage that you don't have any way to make new pages, or make footnotes, page numbering etc. The manual that's shipped with the PDF toolkit for LabVIEW was build with the toolkit. How would you do that with CutePDF Writer?
And yes, the PDF toolkit for LabVIEW only works in LabVIEW. As it turns out the Report generation functions also only work with LabVIEW, and (oh yeah I forgot), you also need cutePDF, and gostscript (and word or excel if you use that), and it only works on Windows. Compairing CutePDF with our toolkit isn't fair. CutePDF doesn't create reports. You still need a way to make them. So you have to compair the toolkit with the report generation functions in LabVIEW AND CuteFTP AND Gostscript.
The block diagrams of the 8.2 example VI are removed by mistake. This only happend with the 8.2 distibution. We will fix this soon. For now, you can use the example VI's from the 7.1 or 8.0 distibution. The professional version has password protected VI's (the free version has the diagrams removed), so upgrading to new LabVIEW versions is possible. If a paying customer has good reasons to see part of the code, we will probably cooperate. But we can't just hand out all the code. Just like you don't have the code for CutePDF...
Guess it's not up to us two anyway...
Regards,
Wiebe.