Re: GitHub and a polygon filling routine

2012-02-11 Thread Thomas Harte
 Mine was mostly being lazy, so I don't have to managing separate source
 archives for each binary release.

Having thought about it, and especially comparing my stuff to yours, I
think I'm also going to use the excuse of it being public but not
fixed to put some serious time into cleaning and commenting. If you
compare that stuff to my latest GitHub project, Clock Signal, it's a
world of difference. I know programmers often wince when they look at
their own old code but the thing that jumped out as really
embarrassing looking back briefly after uploading was a split
infinitive.

Also, I always find going back and commenting to be a good way to get
back into a project. I might finally managed that Freescape-style game
I've always wanted to write.


Re: GitHub and a polygon filling routine

2012-02-10 Thread Simon Owen
On 10 Feb 2012, at 00:10, Thomas Harte wrote:
 started dumping a whole bunch of my old projects onto GitHub

Spookily enough, I started dumping some of my SAM+Speccy projects on there a 
few days ago!  I also added the SAM ROM source, which was converted to 
pyz80/Comet format, corrected to match the 3.0 binary, and split using the 
filenames mentioned throughout the original source.  Everything is under 
https://github.com/simonowen


 as a kind of free backup.

Mine was mostly being lazy, so I don't have to managing separate source 
archives for each binary release.


 That means that you can now find almost exactly the same 3d engine as
 I released previously at http://github.com/TomHarte/Sam-Coupe-3d

Thanks for that, I'll take a look over the weekend :)

Si