ScriptX
Loading content, please wait ...
* For those of you updating to IE9 ...
... the current release version of ScriptX (a mandatory update for IE9) is fully compatible.
* NEW!! Label and barcode ZPL/EPL raw data ...
... direct from browser-hosted content to - say - a Zebra thermal printer? Review the newly-released sample, docs & code here and here.
* Problem? Has it already been fixed? *
Check here to find out.
* ScriptX SPECIAL! *
We're still offering a generous deal on fully-loaded ScriptX + MaxiPT publishing licenses.
Find out more here.
* For the first time in eight years ...
... we have got around to asking some of our customers to describe their use of ScriptX.
Their responses are here.
* Zeepe 7.x is released today *
Check these bytes for the answer to "So what?" and then start your evaluation.
ScriptX licensing is available for various types of deployment:
Client-side licensing is required where you wish to serve fully-functional ScriptX-enabled content to your Internet, intranet and extranet users & visitors for them to print to a local or networked printer.
The only exception to this is where basic ScriptX printing functionality is sufficient for your needs. The digitally signed smsx.cab - available from the download archive - does not need 'advanced' licensing and is freely distributable for client-side deployment.
Server-side licensing is required where ScriptX is to be used with Microsoft's Internet Information Server (IIS) and Active Server Pages to print HTML documents on the server side.
An Active Server Page (ASP) may handle an HTTP GET or POST request and print a report (a different HTML page) as part of some server-side application logic. In this case, the print-out will take place on the server side and will go to a printer which is physically attached or networked to the server. The browsing user who originated the HTTP request may not ever see the printed output nor know that printing has taken place.
Application licensing is available when you wish to incorporate licensed ScriptX functionality into a single Windows (VB, VB.NET/C#, etc) executable.
The licensing schemas are different and do not interact. They -- together with MeadCo's MaxiPT custom Print Template licensing -- are described more fully in the following sections.