It is coming.
Here is structure of projects the Sciter is made of:
- /demos/ – group of demonstration projects that go to public SDK:
- inspector – DOM inspector, targets:
/sdk/bin/inspector32.dll
and/sdk/bin/inspector64.dll
, uses/depends-on sciter.dll - sciter – main demo, UI "player" of HTML/CSS/TIScript, targets:
/sdk/bin/sciter32.exe
and/sdk/bin/sciter64.exe
, uses/depends-on sciter.dll - /libs/ – external libraries, used "as is" by sciter.dll
- dybase – Konstantin Knizhnik’s DyBASE, used by tiscriptlib to provide persistence (Storage and Index objects). Static library, part of sciter.dll
- png – standard distribution of pnglib + animated PNG extension. Used by gool. Static library, part of sciter.dll
- zlib – standard distribution of zlib. Used by pnglib and sciter.dll. Static library, part of sciter.dll
- d2d – Direct2D and DirectWrite gfx backend, used by gool and html. Static library, part of sciter.dll
- gdi+ – GDI+ gfx backend implementation, used by gool and html. Static library, part of sciter.dll
- gool – abstract graphics layer, used by html. Static library, part of sciter.dll
- html – h-smile core – HTML/CSS engine. Static library, part of sciter.dll
- sciter.dll – the sciter engine assembly per se. targets:
/sdk/bin/sciter32.dll
and/sdk/bin/sciter64.dll
- tiscript – standalone tiscript interpretter/compiler assmbled as command line utility. Used for example to compile TIS sources to bytecodes. target:
/sdk/bin/tiscript.exe
(32bit). - tiscriptlib – TIScript core, uses /libs/dybase and tool static libraries. Static library, part of sciter.dll
- tool – collection of common primitives: string, array<T>, hash_map<T>, etc. Static library, part of sciter.dll
- win – window primitives (Windows)
So far I’ve ported /tool, /tiscript + /dybase
/gool and /html are platform independent but taking some attention.
Major things are graphics and windowing layers, they are taking most of the time at the moment.
cool andrew
hope to see it on Linux too