Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

How should I go about continuing from a project that's a mess?

Recommended Posts

A few years ago I took the Boom 2.02 source, and I ported it to use Open Watcom instead of DGJPP. I even went as far as getting it to compile for Windows.


Here's some of the stuff I remember doing with it:

  1. For DOS removed Allegro.
  2. Rewrote input code and tried unify keyboard and mouse inputs.
  3. For DOS used audiolib from the Rise of the Triad source release for sound. (Even though the RoTT code release is GPL, I've always had my doubts about the audio library).
  4. For Windows used SDL.
  5. For Windows used a GLSL 1.2 shader for rendering (mostly used for scaling, but I also played with a 24bit color map).
  6. Make files were reverse engineered from the Heretic and Hexen source release.
  7. Removed a massive amount of comments, reformatted source files and moved functions/variables around.


Unfortunately due to inexperience the code repository is a complete mess. I can't even provide a detailed explanation of what's going on because I honestly have no idea anymore.


Over this year I've been putting together a retro PC as well as making some small contributes to Chocolate Doom, and in doing so I am reminded of this old code. Given that I have an environment where I can run and test a DOS/Windows 98 era source port, it seems like it'd be a loss not to continue with this.


Should I begin the process again from the Boom 2.02 source, using my existing code as a reference, or should I try and salvage it somehow?

Share this post

Link to post

A bit of both in my opinion.


Surely, you had some ideas in your head at that time and tried to apply them to your repository. Take one bit of code that you wrote, analyse it and try to find out what it does. Once you do, write it down.



"removing a stupid bug by using shortening the number of if...else statements"




• remove this bug


Create a list like this and then start your work, focusing on only one point at a time. I have a similar for DeuTex :P 


Share this post

Link to post

Use git. Start by creating two branches: one for the original BOOM source, and one for what you did with it. Diff, merge, and refer back and forth as needed.

Share this post

Link to post

Yeah. I think that's what I'll do.


New repo with only the Boom source. Diff the two repos and redo everything step by step.


Thanks. :)

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now