So good to hear from you!
Regarding your message, maybe is it time to have the Xblite workbench hosted by SourceForge to ensure a future to XBLite?
I had countless happy hours of Xbliting, and I'd feel that I'd loose an old friend.
I worked on the Unicode support for Xblite, but I have a lot of problem cloning the STRING primitives from ASCII to UTF-16 LE.
However, I added the following features:
1. GRAB statement:
GRAB "text file" works just the same as my good ol' COPY "text file" REPLACING ... (from my Good Old Time as a COBOL programer).
2. STRIP directive:
STRIP removes "dead internal FUNCTIONs", and works with GRAB statements in order to weed out extraneous FUNCTIONs.
I provide also with the new folder \grab_bag, which is just a GRAB bag of code snippets!
I posted these evolutions in the Xblite Forum.
3. I actively maintain viXen (I just posted viXen circa 2019):
viXen is a project started by John "prujohn" Evans, who felt that a WYSIWYG GUI designer for XBLite would be a good addition. He started the XBLite project "XBLite GUI designer" at SourceForge in mid-2006 and proposed a beta version for
download as early as 22 July 2006 (version 0.50a).
Now, viXen can generate a GUI program for:
- XBasic XUI
- Xblite Windows ANSI APIs
- Callum Lowcay's WinX
- a primer for GTK+
with the same "VXN project".
I believe that XBLite can offer a lot as soon as it handles Unicode in the same manner as it handles ASCII.
GoAsm was promising, but I have a hard time with assembly. However, I'm not about to give up...