, 24 January 2019 12:57 PM : © 2019 - Mead & Company Ltd.

How to code with ScriptX.Services for Windows PC

This page provides an introduction to using your own ScriptX.Services for Windows PC to print pages from your own web apps.

ScriptX.Services for Windows PC is a local only web server that listens on a local loopback address ( or localhost: and custom port (default 41191). Your web app will not be hosted on the same domain or server as ScriptX.Services for Windows PC.

This means that even if you know the local loopback address port for ScriptX.Services for Windows PC, calls to the server will be blocked unless a valid ScriptX client license is used.

Client PC Installation

With ScriptX.Services for Windows PC, the service must first be installed to each device (Microsoft Windows Intel x64 PC only) and a MeadCo ScriptX Client license deployed. Unlike with ScriptX.Add-on for Internet Explorer this has to be a separate process; it cannot be automated using a .cab based installer that is referenced by and delivered with the page.

Javascript can be used to detect if a service is available and if not the user then redirected to a suitable page that assists with installation of the required applications/services.

ScriptX.Services for On-Premise Devices

ScriptX.Services for On-Premise Devices is a 'one-time' install to a suitable server. Updates to the system are to the single server and client library updates are automatically delivered to client devices: all the advantages of web based delivery.

The disadvantage may be ensuring the abilility to address required printers, but if printers are centralised ScriptX.Services for On-Premise Devices may provide a compelling alternative.

Please take a look at ScriptX.Services for On-Premise Devices for more details.

If you are a SASS provider with a public website providing services to customers with several users from each customer then customers may prefer to install ScriptX.Services for On-Premise Devices at their premises. All you will need to do is to determine a way for each customer to configure the javascript client code delivered by your app with their own On-premise server address. Our samples system illustrates this.

To deliver a print experience to your users any page in your app that provides printing of the page must:

  1. Reference the ScriptX.Services javascript library and dependencies (or write your own code to use the  Web API),
  2. Add code to configure the library - including the MeadCo ScriptX Client license to use,
  3. Add code to describe required settings such as margins, headers and footers,
  4. Add a print button or other appropriate UI to your page,
  5. Connect the print button click even, or appropriate UI event to the ScriptX.Services code using your favourite technique,
  6. Done!

Steps 3,4,5 and 6 are the same as working with ScriptX.Add-on for Internet Explorer. Steps 1 & 2 are functionally the same and in coding terms are as easy as including the MeadCo Security Manager and MeadCo ScriptX factory objects on the page.

A worked example - this page

We'll do things in a slightly different order.

This page has a 'Download to PDF' button, as do other pages on the site. The download is obtained by using Cloud ScriptX.Services to `print` this document to a PDF and then provide the `printed file` as a download.

Working with ScriptX.Services for Windows PC is just (almost) the same, but with ScriptX.Services for Windows PC the printer may be a physical printer connected to the PC so there would be no need for a download to the user.

When this page starts, it connects to the ScriptX.Services for Cloud, later we will add the ability to connect to a ScriptX.Services for Windows PC installed on your Windows PC.

As the name says, this only works on a Windows PC

It would appear you are not using a PC running Microsoft Windows (we think you are using Unknown). Please take a look at ScriptX.Services for On-Premise Devices .

The UI :: the print button

The button is standard html styled with some Bootstrap css and Font Awesome:

Wire up an event handler

We won't use any library to help us though obviously we could as they all resolve to being an abstraction on the underlying DOM:

<script type="text/javascript" defer="true">
        .addEventListener("click",function(event) {
            console.log("Print button clicked");

At this point we have a button which when clicked writes an information line to the console.

Reference the ScriptX.Services javascript modules

The client part of ScriptX.Services is written entirely in javascript and is delivered to client browsers in the usual way viz. a <script /> tag with src attribute referencing the location of the script.

We have a roadmap for ScriptX along which we will add new features and classes of printing. At the moment we only have printing of HTML available but our module structure reflects the fact this will change and we want the changes and additions to re-use code as much as possible.

The MeadCo ScriptX.Print client modules are available for download from  Github . Packages are also available:  Yarn ,  Nuget .

Download and/or install a package and then add these javascript modules to the page:

<script src="/Scripts/jquery-3.1.1.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-core.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprint.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprinthtml.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprintlicensing.js"></script>

The sample code above has listed out each individual file for illustration. Your environment workflow will enable packaging these files as desired, or you may use a CDN:

CDN: <script src="https://cdn.jsdelivr.net/npm/scriptxprint-html@1.4.9/dist/meadco-scriptxservices.min.js"></script>

The whole of MeadCo.ScriptX.Print.HTML is now available to the page.

ScriptX.Services Client library dependencies

 For version 1, ScriptX.Services client depends on jQuery for ajax and some DOM manipulation services so jQuery must be referenced.

Configure ScriptX.Services

ScriptX.Services client must be configured with the MeadCo ScriptX Client license to use and the url of the ScriptX.Services for Windows PC server.

or, as synchronous behaviour is deprecated in all browsers, use an asynchronous connection to the server with a callback function to be called when the server connection is completed. Asynchronous initialisation does not block the browser UI.

Installing the license

The API calls must occur in the order illustrated as the license must be available before the HTML.connect() call can succeed.

If you re-use a ScriptX.Add-on license and the license has not already been accepted then a blocking dialogue will be created and the user asked to approve that ScriptX.Services for Windows PC can used by content delivered from the domains listed in the license. The dialogue may not be obvious and for this reason we recommend an upgrade to the license to enable silent use which by-passes the need for a dialog. All licenses purchased for use with ScriptX.Services for Windows PC have silent use enabled.

The license used here ({C4DB5D29-BE52-46B9-9DDF-46A167170F81}) is the evaluation license you can use to work with developing your own content delivered from localhost on the same machine as ScriptX.Services for Windows PC.

The value "warehouse" means the license will be downloaded from MeadCo's license service. Alternatively, provide a valid url to the location of the license file (sxlic.mlf).

Define print parameters and print

we can now put everything together to print the page to the ScriptX.Services Server default printer.


Complete the form and then print. Your form values will be included on the print.

  Cloud printing!

The print buttons on this page use the MeadCo ScriptX.Services for Cloud to print and deliver the printed output as a PDF file. The code is (almost) exactly the same as would be used to ScriptX.Services for Windows PC (the use of a license parts are a little different).

Migrating current 'Add-on' code to ScriptX.Services for Windows PC

Moving older systems to modern browsers can be a daunting task. Moving code that provided controlled printing with ScriptX.Add-on to ScriptX.Services shouldn't be daunting.

Most code that uses ScriptX.Add-on assumes the presense of an object 'window.factory'. To make sure that moving code that relied upon ScriptX.Add-on isnt daunting, we have developed an emulation of the majority of the functionality of the ScriptX.Add-on object in javascript.

To support old code, the following libraries are required:

<script src="/Scripts/jquery-3.1.1.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-core.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprint.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprinthtml.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxfactory.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprintlicensing.js"></script>

Note that the server and license identifier are included as attributes on the <script /> tag and so there is no reason to call MeadCo.ScriptX.Print.Licensing.apply() or MeadCo.ScriptX.Print.HTML.connect(). With this in place the <object /> tags required for ScriptX.Add-on (including MeadCo License Manager) can be replaced with the <script /> tags and a highly significant amount of code will `just work`.

Supporting old and new browsers

 Write once

If you can get your HTML to work with both old (before Internet Explorer 11) and modern browsers then you can use your current ScriptX code unchanged.

With our ScriptX.Services libraries you can write the code that works seemlessly with both the ScriptX.Add-on and ScriptX.Services.

Include the ScriptX.Services client libraries on the page and they will quietly do nothing when ScriptX.Add-on is available. The result is users with old browsers will be able to print to a printer connected to their workstation, users of modern browsers will be able to print to printers available to the ScriptX.Services server and which ever version of ScriptX, your users will get the same experience with consistent output.

To write once, leave the ScriptX.Add-on object on the page and add the script files. In those browseers that support ScriptX.Add-on it will be used, in those browsers that don't the emulation will be used:

<!-- MeadCo ScriptX -->
<object id="factory" style="display:none"
<script src="/Scripts/jquery-3.1.1.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-core.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprint.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprinthtml.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxfactory.js"></script>
<script src="/Scripts/MeadCo.ScriptX/meadco-scriptxprintlicensing.js"></script>

<script type="text/javascript">
function printPage() {
    factory.printing.header = "";
    factory.printing.footer = "";
    factory.printing.paperSize = "A4";
    factory.printing.Print(false); // don't prompt

MeadCoJS Library and Asynchronous functions

Many developers have made use of our MeadCoJS Script Library availabe on GitHub  MeadCoScriptXJS . Since v1.5 this library provides a complete encapsulation of using both ScriptX.Add-on and ScriptX.Services from the same code. The library (optionally) uses modern promise based coding (a promise library is required for Internet Explorer 11) and provides wrappers for implementing asynchronous functions that we provided in ScriptX.Add-on. For example, the ubiquitous factory.printing.WaitForSpoolingComplete() is implemented albeit with a different function prototype.

However, the library enables writing a single code base for printing which will work when either the Add-on or Services is used within the client browser. The library is used throughout our samples to illustrate this and allows us to write a sample just once.

More samples and illustrations

This has been a quick introduction on how to develop with ScriptX.Services for Windows PC and deliver controlled and consistent print experiences to your users.

Continue in this section with how to work with ScriptX.Services for Windows PC:

Features and futures

We do not intend to stand-still, read on for our roadmap.