ScriptX.Services for Cloud
Our cloud service is free and provides for `printing` to a PDF or XPS format file which is downloaded by the user. They may open, save or print the file - think of this as an easy way to provide "download this page as a PDF/XPS document" facility on your website.
For example, click the button at the top right of this page to receive this page as a PDF document.
Leveraging current investments
The anti-polyfill will work with both classic
'.factory' based code and with
A chance to re-write is always welcome and the very flat properties/methods list of the add-on isn't the design approach that would be taken now.
Our service exposes a rich Web API for describing the parameters to use on the print and delivering the HTML content to print.
- plain text headers and footers,
- landscape or portrait orientation of the paper.
- choosing the paper size to use,
- monitoring of job progress,
- full html headers and footers,
- advanced print scaling.
If you are starting new projects now, then you might want to use your preferred library - jQuery, Angular, React, Vue, Axios etc etc to provide the library for calling a REST API and then extract relevant portions from our libraries on Github for extracting the HTML to send to the service [Swagger API Specification].
The choice is yours.
Advantages of ScriptX.Services
Device and modern browser independence; the host browser and device is not used to to print, print occurs at a server.
There is no requirement to install code on each users PC although note that on our roadmap we have a workstation version of ScriptX.Services which will require installing code on each PC.
There is no requirement for the browser user to accept and install a license - license validation occurs at the server.
The content to be printed is sent over the Internet when using our cloud based service - this could be a cause for concern with confidential information.
To be clear; the html as displayed on screen sent (securely over https:) to the server along with references to required external resources such as style sheets and images (script references are not sent). The html document is then re-assembled by the server, paginated and rendered.
This is why we have developed an On-Premise version of the server.
With an on-premise server, any printer available to the server can be used. We gain the advantage of being abe to print from any device with any browser; PC, laptop, tablet even phone but this is a significant difference from the Internet Explorer add-on.
We are working towards being able to offer a workstation configuration of the system.
At this time we are using the Internet Explorer 11 Trident Rendering engine in 'edge' mode. This is a highly capabable mode with a high degree of compatibility with modern standards HTML as might be required to be printed but clearly there will be some content that cannot be printed or will appear incorrect if it is not supported by Internet Explorer 11 in standards mode.
How to work with ScriptX.Services for Cloud
So that's the background on the evolution, read on for how to 'deploy' and use ScriptX.Services for Cloud.
Or, if hosting the service on your own servers printing to physical printers not files is what you need then look at our on-premise services.