100$ per person or..

#1 As it has been explained on this board again and again...and again.

$100 is per programmer, and programmer is defined as "anyone who uses/accesses the source code." Therefore, your mappers, modelers, skinners, artists, sound guys, web guys, whatever, do no access the source code (anything in the \engine directory), and they do not need the license. You can distribute everything but the \engine directory to the rest of your team, but anyone who wishes to work on the actual source code (not scripts), which is anything in \engine, needs the Torque license.

#2 So is everything, and the source, in /tools free to distribute and I can give that out to anyone?

#3 Compiled tools = Yes
Source code to those tools = (In my opinion) No

#4 "$100 is per programmer, and programmer is defined as "anyone who uses/accesses the source code." "

"So is everything, and the source, in /tools free to distribute and I can give that out to anyone?"

In my logic.
If you gave out the source to tools would that not be giving access to the source code. Wich in turn makes them a programmer under the license and that means they need to pay $100 for that access.

#5 Let me clarify basically I want to know if distrubuting code snippets from those pieces of code in /tools not the whole source code in tools. I feel by using snippets and pieces of code I can write resources that better help the community. As opposed to just saying "take my word for it, the engine does this here".

Here is a copy of some of the response I got on this subject from Tim G. If this is wrong Tim please reply since this is what I meant about giving away source. Basically I just want to open things up and write as much resources as possible as this will open up the engine to more people the less people have to dig through code and "find" out what is going on the faster than can start coding, and, hopefully contributing to the GG community:

Quote:
Sounds good to me. Having any documentation on DTS would be awesome. Though I think the long term (or even medium term) solution is to switch to a more neutral text based format.

Tim
-----Original Message-----
From: Sam C
Sent: Friday, March 29, 2002 1:32 PM
To: Tim Gift
Subject: Re: License issue


Thanks for the quick reply. So I can write a resource called DTS file format and post snippets from TSSHape::read(istream& in) and from the DTS SDK DTS::Shape::read(), just snippets, to help other follow along on how the DTS file format is built and read in? If so, that would be nice.

Sam C
----- Original Message -----
From: Tim Gift
To: Sam C
Sent: Friday, March 29, 2002 1:27 PM
Subject: RE: License issue


There's no problem making the DTS file format, or anything related to it public. It's in everyone's interest to have support for third party tools. If you write documentation or tools, please publish them :) or submit them as Resources. We basically draw the line at posting the SDK source wholesale :)

Tim


-----Original Message-----
From: Sam C
Sent: Friday, March 29, 2002 1:19 PM
To: timg@garagegames.com
Subject: License issue
Importance: High


Tim,

Sorry to email you but usually I get faster responses, in general, via email than posting on a forum. First, my name is Sam Contapay (online: SamC) and I am working on the Maya Exporter. I am close to completion but have a question concerning licensing. I wanted to do a write up on the DTS file format and post it for other developers but the writeup I use is going to point to code snippets in the DTS SDK and the TORQUE engine. Is this OK? If not, is their a private resource center for people who own a license of the TORQUE engine I can post too?

I want to start documenting some of the features of TORQUE as well as write some tools, and I just want to know where I stand as far as documentation. Plus here is a cool feature is there a way to look up on the site if a person owns a license for Torque, maybe a flag by their name or something, that way if someone requests source code, which I wanted to make publicly available anyway I can check their name and send them the source for the exporter to their "registered" email.

Thanks,

Sam C

#6 This is completely differnt then what you first posted about. Your first post had the feeling that you wanted to "distribute" source to tools to anyone that wanted it. If that was not your question, it wasn't very clear, sorry.

#7 Recap:

- Publishing source to the engine, which includes the tools, = Bad Thing.
- Publishing information about file formats used for third party tools, including supporting code snippets = Good Thing.
- Publishing the executables to tools used by artists and scripters = Good Thing.
- Writing documentation, tutorials and tools for community = Very Good Thing :)

It seems like some of the tool source code could be made public at some point, except that they all compile using engine code (I think the MS exporter might not).

Of course any stand-alone tools that you create yourself you can do what you like with, including posting all the source :)

#8 Hehe... I have a really cheesy Bitmap to bm8 converter written in Visual Basic.

#9 Bruce, no need to apologize. When it is Friday and it has been a long week at work I tend to get incoherent as Friday wears on into the evening ;)