Main Menu

Internal BOI

Started by root, May 27, 2026, 08:52 PM

Previous topic - Next topic

root

Working with Chris Mattson, I think I've found a compatible solution for using ScriptBasic embedded for internal BOI scripting.

When using Custom Office to create your script, write it in ScriptBasic COM and save the script with a .sb file type attribute. This is simular to using WSH .js scripts.

This will embed ScriptBasic as the scripting engine instead of instantiating MSScriptControl.ScriptControl.

I will post an example after doing some testing.

root

#1
I have abandoned the Sage forum due to petty moderation and a couple members with open source phobia.

ScriptBasic was born as an embeddable scripting engine with an object like API that is written in ANSI C which allows it to run on any OS with a C compiler. The console and Windows interpreters are examples of the ScriptBasic API in use. The webserver demonstrates the multi-threaded features and memory management.

The bulk of BOI script management is done in the SY_Maint ProvideX object. I'm going to create a ScriptBasic only version of SY_Maint eliminating all references to WSH and the scripting languages it supports. Microsoft has deprecated VBScript as a malware risk. It's not enabled in Windows 11 by default. It's eventually going to disappear.

I plan to have a script IDE that will use the SQLite extension module to store BOI event scripts.

The advantage of using ScriptBasic for BOI scripting is that it gives you full access to all ScriptBasic's extension modules. (CURL for REST should be popular)

ScriptBasic is VB Classic friendly to create OCX form controls that can callback to functions in your script. TwinBASIC is a VB Classic workalike that also generates 64 bit code and objects

When I have a proof of concept working, I'll post the code.