About Sciter.Quark

In brief: Quark is a compiler (a.k.a. assembler, packager) of compact multiplatform desktop GUI applications.

Out of the box it can build Windows (Intel and ARM),  MacOS (Intel and ARM) and Linux (Intel and ARM, e.g. Raspberry Pi) applications. Android and iOS are coming.

Quark takes a folder with HTML/CSS/script/image resources and produces monolithic executable ready to run “as it is”:

Quark workflow

Quark is an application compiled by itself.

Application produced by the Quark is a bundle that contains Sciter.JS Engine and custom resources that describe UI and logic of the application. Therefore minimal size of resulting binary is 5 MB (not compressed) that is comparable with minimal “hello world” applications using other popular UI libraries and frameworks:

  • Qt – 5 MB, but if your application needs to render HTML (QtWebKit) then the size will be around 30 MB. Note: Quark contains HTML/CSS rendering engine in its 5 MB.
  • Electron – 50 MB folder with a lot of stuff inside, 200 MB (at least) of RAM and 2 processes (at least);
  • wxWidgets (linked statically) 3 MB at least.

Sciter Engine Runtime

So what is inside of those 5mb? What functionality is available out of the box?

    • Graphics:  GPU Accelerated Graphic backends (DirectX, OpenGL) on all platforms. Supports as retained as immediate (a la ImGUI) rendering  modes.
    • HTML: parser and DOM that supports as all HTML5 constructs as extended set of input elements including:
      • <include src="..." media="..."> – client side includes to allow assembling HTML from multiple files;
      • <htmlarea> – native implementation of HTML WYSIWYG editor;
      • <plaintext> – multiline plaintext editor with native support of syntax highlighting;
      • <frameset> – can contain arbitrary content (not just <frame>s) – essentially that is so called split-view available out of the box.
      • <frame type=pager> – customizable print preview and print modules;
      • <select type="tree"> and other practical variations of standard  HTML input elements;
      • <popup>, <menu.context> and <menu.popup> – elements – out-of-canvas DOM element rendering;
      • extra HTML attributes to support desktop UI cases including decoration of windows, dialog and message boxes.
    • CSS – supports full implementation of CSS 2.1 plus some useful CSS3 modules:
      • transitions and animations;
      • flexes and grids, with different syntax more suitable for UI though, but, still, functionality is there;
      • CSS syntax extended by SaSS alike constructs @const, @mixin, @set and CSS variables.
      • CSS resident vector images – no need for separate FontAwesome and similar icon fonts.
    • JavaScript –  Sciter.JS uses QuickJS engine – standard (ES2020) conforming JavaScript implementation extended to better suit UI needs:
      • built-in data persistenceNoSQL database (a la MongoDB) integrated into the language;
      • Sciter contains and uses libUV for asynchronous I/O so pretty much all runtime of NodeJS is (or can be made) available: file I/O, file and directory monitors, Process execution objects with stdio/stderr/stdin hooks. And also HTTP, WebSockets, raw sockets communication.
      • Built-in JSX and Reactor – Sciter contains native implementation of ReactJS core and JSX built-in into script compiler.
    • Desktop UI and windowing:
      • Window.this.window(html) and Window.this.modal(JSX|html) functions – creation of native desktop windows and real modal dialogs.
      • Window.this.trayIcon() – built-in support of tray icons;
      • Window.this.windowBlurbehind – support of acrylic and behind-window blending on Windows and Macs;
      • Window.this.windowFrame – standard and custom windows frames including layered/non-rectangular windows;

Addons and native extensions

If the above functionality is not enough then Quark (Sciter’s runtime in fact) supports loading of custom modules from custom DLL’s (.dll,.dylib,.so). You can design and use:

  • Native script classes  and namespaces, for example SQLite can be used from plug-in dll;
  • Native custom DOM elements and input elements (a.k.a. native behaviors): DLL-resident DOM element implementations can handle events and do native painting using  sciter::graphics API ;
  • Native DOM elements wrapping of existing HWND, NSView, GtkWidget based components.

Start using Quark

See Samples , “hello world” in particular.