Ginger88895
/
warzone2100
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
warzone2100/tools
History
Per Inge Mathisen 554bf6b380 Fix build warnings 2011-09-25 23:55:24 -04:00
..
3ds2pie 3ds2pie tool update. Belongs to #1553. 2010-03-20 16:17:48 +01:00
blender Update plugin status 2010-03-21 19:47:12 +01:00
conversion simplipie: Add warning when not all polygons in a mesh do not use the same number of frames for texture animation. 2010-12-31 22:26:45 +01:00
display Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
editworld Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
gitsvngateway Bail out when pushing to the git repository fails. 2009-11-23 18:47:00 +01:00
guidecode Delete cms.php - it appears to be superfluous. 2010-02-09 20:27:50 +01:00
html2trac Bump copyright 2009-02-10 18:01:48 +00:00
image Add IMAGE_GN_N for N up to 15. 2011-01-13 15:58:46 +01:00
map Fix build warnings 2011-09-25 23:55:24 -04: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
qwzm Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
rpl2avi rpl2avi converter by Angus Lees 2009-11-22 16:34:23 +01:00
tech-tree-chart-generator fix path 2009-09-27 19:07:01 +02: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
trac/plugins Debianize the two ticket-related Trac plugins 2010-10-04 19:39:13 +02: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.