Ginger88895
/
warzone2100
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
warzone2100/tools
History
Giel van Schijndel c8d9336618 Update the Pygments WRF lexer for the changes done to the WRF file format in r5188:5189 
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5190 4a71c877-e1ca-e34f-864e-861f7616d084
 		2008-05-25 20:03:37 +00:00
..
3ds2pie Update the usage help for 3DS conversion tools. 2008-04-05 19:54:12 +00:00
blender * Fix the Blender import & export scripts such that they're completely compatible with eachother (i.e. import->export->import == import) 2007-08-20 15:09:13 +00:00
conversion Update the usage help for 3DS conversion tools. 2008-04-05 19:54:12 +00:00
display wzmviewer: Interpolate positions between frames for bone heap animation to 2008-03-05 20:36:43 +00:00
editworld Recreate the EditWorld project and workspace 2008-04-07 14:33:53 +00:00
lobby Set executable bit, makes running the script a bit easier. 2007-03-21 00:39:11 +00:00
lobbyserver_cpp * Mark some variables as volatile (they're shared across threads) 2008-03-27 16:30:41 +00:00
masterserver Typo in masterserver 2008-03-30 17:30:19 +00:00
pietoaster Generic cleanup. Mostly remove struct keyword where unnecessary. 2008-01-28 00:02:28 +00:00
pygments-lexers Update the Pygments WRF lexer for the changes done to the WRF file format in r5188:5189 2008-05-25 20:03:37 +00:00
tile_texpage2mipmap_tileset * Fix tile_texpage2mipmap_tileset, it now makes imagemagick output zero-padded filenames up to 2 digits (like Warzone expects) 2007-10-11 22:47:13 +00:00
README Added a directory to contain tools for Warzone 2100. (E.g. modelling/texturing stuff, some map editor maybe, etc.) 2007-01-31 19:58:49 +00:00

README 

************************************DRAFT***************************************

This directory (will) contain all sorts of Warzone 2100 related tools.

 * Each of these tools will have to be Warzone specific.
 * Every independend tool should have one directory of its own
 * No tool should depend on others for compilation or linking.
 * Each of these tools *must* have a "COPYING" file with it in its directory.
  - This file should contain the full licensing conditions applied to the entire tool.
  - If parts of this tool are licensed differently this *must* be made note of in this file.
  - Preferrably all tools should be licensed GPL (or maybe LGPL if it's easily reusable for other projects?).
  - In case the GPL is used it is best copied from /trunk/COPYING using the `svn copy` command.