Brad Thompson wrote:
How many times have we been over this?Why couldn't you treat software the same way? Translate OGC into C++ orTranslation does not obviate the need for clear identification. The output
VB? Both of there outputs are visual, and as long as you know how to
translate the pictures that pop up on your screen, you can read the OGC.
is only one aspect of the software. Simply identifying the output is not
sufficient to indicate the OGC that might exist within the code itself.
If I write all my own code, and either distribute the source as OGL (no binary)or aquire rights to distribute everyting a compiler adds in under the OGL (and have a whole-OGL set) I can go right ahead.
The problem areas are: (1) when I try and keep some of the software "not covered" (2) when I'm using libraries et al that I don't have the authority to distribute under the OGL and (3) if I want to use the d20STL.
I'm actually rather surprised that there aren't more OGC die rollers, stat managers, etc. If you're not trying anything "fancy" wtih the license and have clear right to redistribute in a copyleft license, you should be just fine.
DM
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://mail.opengamingfoundation.org/mailman/listinfo/ogf-l
