More on modules

[darkone]

I decided to add generic module support for events. Config entries will look something like this:

[Scripts]
MyScript = EXEC ..\scripts\myscript.exe
MyTclScript = TCL ..\scripts\myscript.itcl
MyModule = MYMODULE MyModuleParams

I will try to get most of the important headers cleaned up.. (~30 files)

[dasOp]

that looks kinda ambiguous to me.
Is Module an event in itself or just a listing to tell io to load said module?

[darkone]

I'm not quite sure what you meant with that. But I'll try to explain briefly how it works:

-- [Modules] -->
EventModule = ..\modules\MyEventModule.dll
-- daemon start-up -->
LoadModule(szModuleFileName);
GetProcAddress("EventInit");
EventInit(lpEventModule);
-- module initialization ->
lpEventModule->szName = "MYMODULE V0.9";
lpEventModule->lpInstallEvent("DoStuff", DoStuffProc);
-- [Scripts] -->
DOSTUFF = DoStuff
DONOTHING = DoStuff DoNothing

This allows you to add new interpreters (Php, java, asp) using modules..

[dasOp]

Ah, that sure makes sense.

So in essence I could also load my module, have that module spawn a thread upon init and Run a gui in that thread?

[darkone]

Yep.. you can also use io's worker threads & io threads, if needed (hence BindCompletionPort & JobQueue functions) I might even allow use of message handler threads, as I've built nice API for those too

[dasOp]

Sounds great! This makes shell shared memory kinda redundant though. Good riddance I say!