New License Agreement

[catventure]

Hi Eros,

In the new preview you mentioned about the new License Agreement allowing users to distribute thinbasic with user scripts... This sounds very good.
Could you please expand on this a little?
If I made a text adventure using my TAB program (windows program) which currently uses UI, OS and FILE modules and wanted to bundle the TAB Player program and the adventure database, exactly what TB files, dll's etc would need to be present in the distribution in order for it to run OK?
Not that I have finished writing a game yet - just interested to know. Or have I misunderstood?

Cheers,
catventure

[ErosOlmi]

Our suggestion is to execute a Setup install on the machines you need to run thinBasic scripts because this will ensure you will have all the things setup for you (some few registry keys for example) and also to avoid to have multiple thinBasic version around on the same PC.

As you know, thinBasic scripts can be executed by a double click directly from explorer. This is achieve setting up few registry keys that link thinBasic extensions (tBasic, tBasicc, tBasicx, tBasiccx) to a specific executable (thinBasic.exe or thinBasicc.exe). If you have multiple copies of thinBasic on the same machine, the last executed will overwrite this behave and will take the priority.
This is not true if you execute a script using a full command like c:\thinBasic\thinBasic.exe c:\MyScripts\Tab.tBasic because this command line exaclty specify what to run and with wich parameters.

That said, yes, you can distribute thinBasic.exe (GUI version) and/or thinBasicc.exe (Console version) and all the necessary .DLL with your scripts.

Only problem you can face is the protection we have on our main engine: thinCore.dll and thinVL.dll. They put in place a cross program check on version and crack attemp. So be sure to have the correct versions installed.

Minimum needed files:

thinBasic.exe (or thinBasicc.exe in case of console script)
thinCore.dll
thinVL.dll
thinRes.dll
thinRTE.dll
zLib.dll


All other libs (thinBasic_*.dll) are needed only if relative module is used inside the script.
For example if script uses "UI" module, you need to include thinBasic_UI.dll, if script used "TBGL" module you need to distribute thinBasic_TBGL.dll and so on.

We do not permit to distribute thinCore.dll and thinVL.dll alone without our written permission.

Ciao
Eros

[Petr Schreiber]

Eros,

maybe this is silly question but how License.rtf reflects this ?
I have viewed it many times to make me sure, but I can't find the section which says that.
Maybe this is an old version ( still ? ) of the document, because I can see "You may not: * use the parts of software separately from others". This can be understood as for "thinCore.dll and thinVL.dll". But if Catventure wants just parts, and that's what you agree in the post above, it seems it could be illegal ;).

Thanks,
Petr

P.S. You use both "thinBasic" and "ThinBasic" in the document, which one is correct :) ?

[ErosOlmi]

Download latest thinBasic preview version 1.0.11.0

[Petr Schreiber]

Hi Eros,

sorry for confusing post.
It's weird but the version with "bad" licence was dated 07-09-2006 (16:35) and I downloaded it at 20:48. How could I miss the midnight release :)

Thanks and sorry,
Petr