warzone2100/tools
Per Inge Mathisen 0207ceb4c1 Add a tool to convert from the PIE format to the imaginary WZM format.
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@3710 4a71c877-e1ca-e34f-864e-861f7616d084
2008-02-07 14:59:53 +00:00
..
3ds2pie Make 3ds2pie tool conform to PIE standard even though the Warzone code ignores 2008-02-06 17:35:28 +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 Add a tool to convert from the PIE format to the imaginary WZM format. 2008-02-07 14:59:53 +00:00
editworld * Make Win::HWND a "strong" typedef; this guarantees that code that just assumes Win::HWND is the same type as ::HWND (from <windows.h>) will fail to compile 2008-01-24 00:43:10 +00:00
lobby Set executable bit, makes running the script a bit easier. 2007-03-21 00:39:11 +00:00
lobbyserver_cpp * s/tagWriteSeparator/tagWriteNext/g for consistency's sake (to match the tagReadNext function, which is the reading equivalent) 2008-01-04 13:37:42 +00:00
masterserver Use network byte order for struct unpacking on the lobby server (rather than native byte ordering) 2008-02-03 16:51:56 +00:00
pietoaster Generic cleanup. Mostly remove struct keyword where unnecessary. 2008-01-28 00:02:28 +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.