ref: 9ba60f243d1ae1ab14ba28eac92fca7b5891801a
parent: adc6a405ba0d2b77cf227184044186a84a971161
author: Simon Howard <[email protected]>
date: Thu Sep 25 15:46:22 EDT 2008
Update HH-TODO. Subversion-branch: /branches/raven-branch Subversion-revision: 1285
--- a/HH-TODO
+++ b/HH-TODO
@@ -1,10 +1,27 @@
* Remove all dependencies of common code on doom/
- net_client.c
- * Merge v_video.c to common version and delete duplicates
- * Merge r_draw.c to common version and delete duplicates
- * Merge ticcmd_t to common (needs netcode update)
* Split d_iwad.c into common and use for Heretic/Hexen
+ * Update netcode for new ticcmd_t fields
* Chocolate Setup to allow configuration for H/H
+ * Update docgen to generate manpages for Heretic/Hexen.
+
+Heretic:
+ * Merge r_draw.c to common version and delete duplicate
+ * Multiplayer code to use Chocolate Doom multiplayer code.
+ * WAD code to use the new locking API
+ * Save config file
+ * Frequency shifted sounds.
+ * Update input code to work properly with vanilla_keyboard_mapping
+ * Check all command line parameters
+ * Check for endianness assumptions
+ * Savegame code to write structures predictably and endianness-correct
+ * Remove NeXT and WATCOMC defines
+ * Structure packing macros for structures read from disk
+ * Title bar
+
+Hexen:
+ * Merge v_video.c to common version and delete duplicate
+ * Merge r_draw.c to common version and delete duplicate
* Remove duplicates:
- Key definitions
- Angles
@@ -13,18 +30,12 @@
- Endianness macros
- i_system
- argv
- * ENDOOM needs to be able to load ENDTEXT as well
-
-Updates needed for Raven code:
* Multiplayer code to use Chocolate Doom multiplayer code.
* WAD code to use the new locking API
* Config file code to use m_config.c (and add H/H-specific variables)
* Use the common i_sound API. Frequency shifting?
- * Video code to use screens[] - or dump screens[] and use a single variable
* Use the common cheats code
* Update input code to work properly with vanilla_keyboard_mapping
-
-Clean up Raven code:
* MAXINT -> INT_MAX, etc.
* Check for endianness assumptions (shouldn't be too bad if it was developed
on NeXT)