ScriptX
Loading content, please wait ...
* For those of you updating to IE8 or testing Windows 7 ...
... the current release version of ScriptX (a mandatory update for IE8) 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.
In Internet Explorer 5.5 Microsoft re-wrote the browser's underlying printing architecture and introduced Print Templates. Built using scripted HTML and four job-specific element behaviors, Print Templates are designed to provide enhanced control over print & print preview behaviour, and over page layout for printing & previewing.
In his excellent introduction to IE 5.5+ print customization, Microsoft's Chuck Ainslie says this:
"The new print customization possibilities add a new layer of possibilities to Internet Explorer as a platform for application development. By creating a print template, you can control:
Because you now have extensive layout and handling control over printing, Internet Explorer can fit many new application scenarios, such as:
For those thinking about writing their own custom Print Templates, Chuck's series of articles is an excellent place to start. [top]
Print Templates, Security and ScriptX
Security considerations - in web-technology terms the template pane is a 'trusted' element - mean that custom Print Templates cannot by default be assigned and deployed freely for use in the IE browser over the Internet or intranet. Browsers from IE 5.5 and later are themselves shipped with a single default Print Template.
However by virtue of ScriptX' inherently secure licensing schema, it is uniquely possible for ScriptX licensees to deploy custom Print Templates easily and in complete security. The ScriptX templateUrl property specifies the URL of a custom Print Template for use in IE 5.5+ whilst MeadCo's Security Manager controls the permission to run templates from the URL addresses bound to a client-side publishing license. [top]
Deploying your own custom Print Template
ScriptX installs two default Print Templates of its own which are based on the versions provided with IE5.5 & IE6.x, and with IE7. These are made available on the client PC as resources from within MCMaxiPT.dll.
You can deploy your own Print Templates as part of the licensed use of ScriptX, but you will need to insert a TriPrint <object> into the <head> section of the template source thus:
<HTML XMLNS:IE>
<HEAD>
<?IMPORT namespace="ie" implementation="#default">
<!-- <TriPrint> (c) 2000 - 2010 by Mead & Co Limited <feedback@meadroid.com> -->
<object classid="clsid:1663ed6a-23eb-11d2-b92f-008048fdd814" viewastext>
<param name="__PX__template" value="true">
</object>
<!-- </TriPrint> -->
<TITLE>Print Preview</TITLE>
MeadCo's MaxiPT custom Print Template
MeadCo's MaxiPT provides printing capabilities that are significantly more flexible and powerful than Internet Explorer's standard offering. Currently MaxiPT functionality is grouped into two Feature Sets, either or both of which can be ordered for use as an optional part of a ScriptX client-side publishing license.
Feature Set #1 provides printing capabilities that are much more rich and customizable than those provided with Internet Explorer 5.5+ and are in fact much closer to Office. These include:
Feature Set #2 provides a collection of specific printing capabilities that have been requested by ScriptX licensees. These are:
A detailed description of MaxiPT, together with functional examples of both Feature Sets, can be found here. [top]