ScriptX can be used by any application that supports the use of COM components. This includes desktop and console applications or even a service.
ScriptX requires that the Internet Explorer platform is available - in other words all desktop versions of Windows including Windows 8 and 10. Note that on Windows 10 the Microsoft EdgeHTML components are not used since EdgeHTML does not provide an extensibility model for 3rd parties. The consquence of this is that UWP apps using WebView will not work with ScriptX.
There are two scenarios in which ScriptX can be used with a desktop (client) application to print html content (see our Github repo for samples):
In basic use, a web browser control is embedded in the UI of the application. It is assumed that the displayed html content has no print UI elements and so the print UI is provided by the application. The displayed html content either contains the MeadCo ScriptX factory object, or it is inserted by the application when required. The application then uses the object to perform printing.
The basic application section contains more details.
Advanced (licensed) use offers more scenarios: printing the content in an embedded web browser control, printing content created on the fly or printing content from a webservice (i.e. any arbitrary html document downloaded from a a url).
Any of these scenarios require that the application is licensed as described in advanced use licensing.
Console / service applications
A console application or service can print HTML content constructed dynamically within the application or can print content from a webservice (i.e. any arbitrary html document downloaded from a url). The application must be licensed as described in advanced use licensing.
A sample console application is available on Github.
::> Basic use