ehm..my 'complete' first email:
"Hi Fred,
I have a question about the PureBasic license and dlls created with PureBasic. After having a look at the forums I thought you were the best person to contact.
I currently own PureBasic, PowerBasic, Visual Studio 6 Professional and DarkBasic Professional. I started my project in PowerBasic and Visual Basic, then I chose to buy PureBasic because I'm interested in a language with a 3D engine, as well.
At the moment my project is to create an Ide that includes a Visual Designer and an editor. I will create the Visual Designer and the source code editor in Visual Basic, because I have more experience with it and I'd like to have something ready to show, while the gui engine (a dll) will be made in PureBasic (originally in PowerBasic). I will include functions for INI files, cryptography, registry and gui at first and later on I would like to expand my project to create a level editor for DarkBASIC Professional and Blitz3D and also add some IA. Meanwhile I will create an analogue project only for PureBasic and Ogre. At last the final product could be something like an RPG Maker (but for different kinds of games, no just for RPG).
One of the aims is to expand original the dll in PureBasic to manage everything (but the Visual Designer, Level Editor and Source Code Editor). The dll will be released inside my application but those who bought it could also use it as a standalone dll inside their DarkBasic Pro, Blitz 3D application to create forms (windows) at runtime for example, to encrypt files or strings, and so on... and one of the aims is to create just one big dll that does the most than having several small dlls.
I am also considering to let users expand my project if they have a full version of PureBasic and add new functionalities to it. Honestly I can tell you more after I start working on it and realize if there are any limits.
Those who did not buy my application could use the dll in demo mode, with limited access to its functions. Most of the functions will be expanded from the original PureBasic equivalent, for example by adding support to transparent windows, ...
According to PureBasic license:
"The PureBasic license explicitly forbids the creation of DLLs whose primary function is to serve as a 'wrapper' for PureBasic functions"
and from the PureBasic website:
"But it's not allowed to release simple "wrapper" Dlls to include PureBasic commands in other programming languages."
but should the dll I create to be considered as a simple wrapper or not, considering I will also use winapi functions or other stuff to expand it. If so what is your advice? In case the product is a good idea, I was also planning to promote it in official websites such as PureBasic, TheGameCreators, BlitzBasic and let the companies get a percentage for the promotion thing.
Once again, what is your advice?
Thanks,
Roberto"
-------------------------
Fred's first reply about my question:
As long you use the PB high level commands to manage your things for
your own langage/game creator etc, it's forbidden. You can easily
understand why, we have spend countless hours in each commands to have
them optimized for PureBasic, we don't want the others langages/game
creations tools have them for free. For example, if you use the
sprite/sprite3d to manage your sprite environment, it's forbidden. The
same for the Windows/Gadget/Requester etc. to manange your GUI. Now,
if you write everything using the API (CreateWindowEx_() etc.) or use
DirectX directly, it's no problem, but it's much more work (basically
the work we did

.
-----------------------------