|
Viewer ActiveX SDK is a fully featured, ready to incorporate facsimile of the End User PDF-XChange Viewer, again embedded within a Window of the developers application, the developer is able to hide and disable most of the controls and functions within the SDK and some GUI tailoring is possible - but Tracker Software branding is present and required from the 'About' Window of the embedded viewer. The ActiveX is also more feature rich than the Viewer Simple DLL SDK method. And is included in the Viewer PRO SDK bundle. Clarion Developers have the choice of using our generic toolkits, or our Clarion specific SDKs which offer Clarion specific Help and Examples, along with comprehensive classes and templates for all versions of Clarion from C5b and up, making its major functions simple to incorporate into their project. |
Demo Limits
Evaluation versions of our SDK software are fully functional, allowing the testing and full utilization of all SDK features, Developers need to be aware that any test documents will have a demo watermark placed on every page of any PDF created or modified with the evaluation versions.
![]()
We recommend which ever option you decide is best suited for your needs - that you use the evaluation SDK's to the maximum prior to purchase to ensure satisfaction and only purchase when ready to recompile you completed application ready for distribution to your clients - with your license strings, to remove the demo watermarks restrictions.
As we do not offer refunds after issuing licensing info.
Licensing
Developer's owning existing PDF-XChange or PDF-Tools Developer SDK's are provided with the following free distribution rights to end users of their software applications:(available now) provides the developer with set of functions to create a means to View/Print PDF files within a window embedded in their software application. Both the GUI design and means of employing the provided functionality is very much left in the developer's hands and no Tracker branding is visible within the Developer's product. (available ) option is a fully featured, ready to incorporate facsimile of the End User PDF-XChange Viewer PRO, again embedded within a Window of the application, the developer is able to hide and disable most of the controls and functions within the SDK and some GUI tailoring is possible - but Tracker Software branding is present and required from the 'About' Window of the embedded viewer. The ActiveX is also more feature rich than the VIewer Simple DLL SDK method. PDF-XChange or PDF-Tools Developer SDK's are provided with the following free distribution rights to end users of their software applications:
PDF-XChange/PDF-Tools SDK Type
Viewer Client Distribution
Licenses Included
PDF-XChange Viewer Base SDK
25,000
PDF-XChange PRO SDK
7,500
PDF-XChange Drivers API SDK
2,500
PDF-Tools SDK
2,500
Once the licenses provided with the any of the above Developers SDK's have been used - prior to continuing to distribute an application utilizing the PDF-XChange Viewer, the Developer must purchase an additional client distribution License Pack (CDLP) available in 25K, 50K, 100K, 250K or 1 Million Client License pack's. For information regarding Royalty free licensing please contact sales@tracker-software.com Client Distribution If a developer does not own any of the above SDK's, the purchase of a PDF-XChange Viewer SDK Base Pack is required prior to purchasing any Client Distribution. License packs. Important : Either a PDF-XChange Viewer SDK Base Pack or one of our other PDF-XChange/PDF-Tools SDK's must be owned - prior to additional CDLP License packs being purchased.
License
Pack (CDLP)
Base PDF-XChange Viewer SDK 25K
Not required if you own our other PDF SDK's
50,000
100,000
250,000
1,000,000
Larger/Royalty Free
The PDF-XChange Viewer SDK is not a Royalty Free product as standard - however special rates may be negotiated for large Client Distribution License packs.

| Avg. Score: | 5/5 Stars |
by John Aitchison 18 Apr, 2011 09:50 AM PDT
After looking at all of the other SDK’s out there, I was on the edge of mental breakdown because I wasn’t sure we were going to find a suitable candidate for our product.