Its main-purpose is, to decouple from as many MS-COM-dependencies as possible, with the goal in mind,
to achieve a self-hosting state easier later on, when the accompanying (VB6-compatible) Compiler will lift off.
And if easier to achieve platform-portability (for the Compiler and the new Class-based Runtime) is the goal,
then we need to start working with such a decoupling-framework already in the transition- and planning-phase.
So, the lib offers a modern GUI-Framework which works Vector-based, using the cairo-library under the
hood (no GDI/GDI+ or DirectX here ... and also nothing of the MS-CommonControls.dll is touched).
The other larger part, which is often needed and used within "typical VB-Applications" is easy DB-Access
(usually done over an accompanying Desktop-DB-File in *.mdb-Format). So what the framework also offers,
is an easy to use (and nearly ADO-compatible) replacement for the MS-JET-Engine. This is, what makes
up the other larger part of the accompanying satellite-binary: vb_cairo_sqlite.dll ... the SQLite-engine.
Bookmarks