Category: Sciter

You can read it here (in Russian).

ENTER in that input triggers script evaluation: inspector asks the “inspectee” to execute that script in context of its selected element.

Sciter’s is getting new Inspector tool.

New Inspector is a standalone executable that communicates with the inspectable Sciter window (view) over TCP/IP using DataSockets.
There are few reasons behind such architecture:

1. Mac OSX and GTK (or QT) do not really support multiple GUI threads in the same GUI process. Inspector UI must be run independently
   from the inspectable.
2. There is a need to support remote debugging mode. Especially when Sciter runs in kiosk mode spanning whole desktop space.
3. UI Automation Testing, and UI of testing tool in particular, has to work out of inspectable application.

Each Sciter application that wants to be inspectable shall allow connection with the Inspector explicitly by calling SciterSetOption(hwnd | NULL, SCITER_SET_DEBUG_MODE, TRUE); before loading HTML into Sciter’s window. In response Sciter engine injects so called inspector peer script into the view. Inspector peer script is a small script block that establish event handlers and interceptors (e.g. stdout/stderr proxies). The script adds the following method

  function view.connectToInspector(rootEl = null, inspectorHostIP = null); 

to the view instance and registers CTRL+SHIFT+I (connect to inspector) and CTRL+SHIFT+Click (select DOM element for the inspection).
CTRL+SHIFT+I is used to connect with the inspector when it runs on the same machine.

The same Inspector instance can serve multiple windows/views, even from different processes or GUI threads.

Print and Print Preview feature will appear in upcoming Sciter versions. It uses the same architecture ( page-template -> document to print) as in S1.

Among other things it will support scriptable drawing using paintContent(gfx) and print event handlers on template level.

Sciter on Raspberry Pi 2 in kiosk mode:

Thanks to Michael Weber!

You can hear it here