search

datalogics / adobe-pdf-library-samples

Sample code for the Datalogics C++, Java, and .NET interfaces of the Adobe PDF Library
https://www.datalogics.com/adobe-pdf-library/
80 stars 62 forks source link

Feature Comparision #7

Closed sarankup closed 4 years ago

sarankup commented 6 years ago

Hi,

I want to start product development using PDF Library. I want to check with you whether any specific choice programming here (C++, .NET, JAVA) has much rich feature compare to other. If all are the same, then we can start with Java. If C++ is much superior in terms of feature, we can plan with C++.

Thanks in advance.

datalogics-pgallot commented 6 years ago

Hi, The Java and .Net interfaces (which basically have feature parity between them) have some value-added features that are not available withAPDFL's C/C++ interface, but the C/C++ interface is what the Java and .Net interfaces are based on. Not all of APDFL's features are exposed in the Java and DotNet interfaces, but easily 90% of APDFL's functionality is exposed via the Java and .Net interfaces.

All told, I would recommend starting with the Java interface, which is a bit easier to get started with versus the C/C++ interface.

sarankup commented 6 years ago

Hi,

We see the PDF Library SDK in both Adobe site and Datalogics.

Does both same? Or Datalogics is only having Java and .NET facilities?

On 3 Mar 2018 3:24 am, "Patrick Gallot" notifications@github.com wrote:

Hi, The Java and .Net interfaces (which basically have feature parity between them) have some value-added features that are not available withAPDFL's C/C++ interface, but the C/C++ interface is what the Java and .Net interfaces are based on. Not all of APDFL's features are exposed in the Java and DotNet interfaces, but easily 90% of APDFL's functionality is exposed via the Java and .Net interfaces.

All told, I would recommend starting with the Java interface, which is a bit easier to get started with versus the C/C++ interface.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/datalogics/adobe-pdf-library-samples/issues/7#issuecomment-370063685, or mute the thread https://github.com/notifications/unsubscribe-auth/AE0tHvieAslbVxNVnmQsMAW-S_UonVhhks5tab96gaJpZM4SUk19 .

datalogics-pgallot commented 6 years ago

Datalogics resells the Adobe PDF Library both as we receive it from Adobe and with our enhancements, add-ons, and fixes. The Java and .Net interfaces are add-ons from Datalogics. In general, Adobe does not directly sell the PDF Library to customers. However, it does provide an Acrobat SDK which has a very similar interface to the PDF Library, with a bit more functionality than is provided by the PDF Library. The key difference is that the Acrobat SDK requires a copy of Acrobat Pro to run while the PDF Library can be used in a stand-alone application.

coderabsolute commented 6 years ago

Is it possible to view the C# documentation and the sample program before buying, with an assumption that C# and Java interface code is 100% same and their behavior? Specifically, am looking to convert HTML to PDF programmatically...

datalogics-pgallot commented 6 years ago

@coderabsolute Just to clarify; APDFL has a Java and .Net interface that are generated from the same code base and while they are largely functionally identical, there are some minor aspects where they differ in order to better accommodate the VM-specific differences. Stream-IO comes to mind, for example.

The evaluation package does include documentation for both the DotNet and Java interfaces.

Also note that the Java interface is completely separate from our PDF Java Toolkit (PDFJT) which is pure Java from the ground up, and is not an interface to the C/C++ APDFL library.