ScriptX
Loading content, please wait ...
February 03 '08:
* 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.
January 28 '08:
* Problem? Has it already been fixed? *
Check here to find out.
January 22 '08:
* ScriptX SPECIAL! *
We're still offering a generous deal on fully-loaded ScriptX + MaxiPT publishing licenses.
Find out more here.
December 4 '06:
* For those of you testing or updating to IE7 XP and Vista ...
... the current release version of ScriptX (a mandatory update for IE7) is fully compatible.
August 1 '06:
* 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.
April 11 '06:
* IE Security Update (KB912812/MS06-013) and ScriptX *
The security update for XP SP2 released on 11th April 2006 but slowly rolling out around the world is not compatible with old versions of ScriptX.
Click here for more information...
March 29 '06:
* IE update for ActiveX Control activation *
Microsoft has posted some update info here.
This change (to comply with the EOLAS judgement) applies to 'interactive' controls that render a user interface on the page.
ScriptX is a non-visual control, so works exactly the same (with no changes required to any tag or script) before or after installation of that patch.
Both our own in-depth testing and feedback from our customers confirms this.
March 10 '04:
* Zeepe 7.x is released today *
Check these bytes for the answer to "So what?" and then start your evaluation.
A basic subset of ScriptX client-side printing functionality -- header & footer settings, printed orientation, coarse control of margins and a browser window/frame printing command -- is available at no charge, and is freely distributable.
How to enable 'basic' printing
A 'basic' ScriptX-enabled document is defined as one on which the ScriptX object block appears thus:
<!-- MeadCo ScriptX --> <object id=factory style="display:none" classid="clsid:1663ed61-23eb-11d2-b92f-008048fdd814" codebase="http://[your path here]/smsx.cab#Version=6,4,438,06"> </object>
For successful operation the codebase attribute must 'point' to the correct location and version number of the smsx.cab file on your servers. That 'pointer' path can be relative to the location of the document on which the ScriptX object appears, or it can be fully qualified.
Due to abuse, the cab file is no longer available for referencing from our servers - apologies for any inconvenience this has caused.
Please note that only one ScriptX object should appear on any one document.
The copy of smsx.cab contained in the downloadable archive is updated and made freely available upon each new version release. [top]
Pre-installing the ScriptX software
System administrators wishing to pre-install ScriptX over an intranet should run smsx.exe - also contained in the downloadable archive - on each client machine. This approach is an alternative to having the control auto-download the first time a user hits a ScriptX-enabled page, and avoids the standard 'signed component' prompt with which a user is normally faced. However you will still need to reference the ScriptX object on each of your pages.
Formatting printing attributes and printing
A typical function call to set 'basic' print formatting and print a top-level document client-side could look like this:
<script>
function printWindow() {
factory.printing.header = "This is MeadCo";
factory.printing.footer = "Printing by ScriptX";
factory.printing.portrait = false;
factory.printing.leftMargin = 1.0;
factory.printing.topMargin = 1.0;
factory.printing.rightMargin = 1.0;
factory.printing.bottomMargin = 1.0;
factory.printing.Print(false);
}
</script>
Notice that we call all ScriptX functions by reference to the ID of the on-page ScriptX object - usually 'factory'. Please note that you can NOT use the ASP calls CreateObject or new ActiveXObject to call ScriptX from *any* client-side ScriptX-enabled page. [top]
An important note to licensees upgrading from long-standing 'free' use
Once you have acquired a publishing license to use ScriptX 'advanced' functionality you will no longer need to deploy the (now obsolete) ScriptX.cab and should update all of your on-page objects' Codebase attributes to refer to smsx.cab.