Skip to content
Tags give the ability to mark specific points in history as being important
  • Day6
    This is the project code as of the end of the sixth day of Devember.
    
    There are not a lot of changes here as the main feature being worked on is
    currently not in a state that I'm willing to check in; that being how entity
    properties work with regards to defaults being applied.
    
    More research needs to be done as to the best way to go about this in TypeScript
    to create type safety at compile time.
  • Day5
    This is the project code as of the end of the fifth day of Devember.
    
    The last of the Stage class refactoring has been completed. Rendering is now
    done via an interface named Render and a concrete class named CanvasRenderer.
    The stage has a .renderer property that contains all of the rendering methods as
    they used to exist.
    
    This does mean that as of now the code responsible for rendering things has an
    extra indirection.  I'm going to leave that alone for right now and see how
    things shake out speed and code beauty-wise.
  • Day4
    f4ba51fc · Enhance sample code ·
    This is the project code as of the end of the fourth day of Devember.
    
    Making up for the lack of code yesterday (since so much time was spent doing research), this
    includes a bunch of commits which are code cleanups. The cleanup is almost complete so we're
    almost ready to knock that milestone off and call the port officially done, and then move on.
    
    The code has been tightened up as far as property access is concerned. Also some other refactoring has been
    done, most notably in the Stage class.
    
    This code uses "instance functions", which are basically functions that capture the "this" context into a
    hidden variable, so that whenever they are invoked they refer to the appropriate object.
  • Day3
    This is the project code as of the end of the third day of Devember.
    
    There is not a lot of practical code change here, just a couple of things
    cleaned up.
    
    The bulk of development effort today went into researching the speed
    implications of using Object.defineProperty() to set up read only properties on
    objects, since the last phase in the initial porting effort will be to enforce
    good data isolation.
    
    The results of my benchmarks (assuming I did it correctly) indicates that there
    is no real speed degredation, so plans can continue as planned for tomorrow.
  • Day2
    This is the project code as of the end of the second day of Devember.
    
    The initial porting efforts of all classes is now complete, but more work needs
    to be done before I consider this completely done. Some of the code is a little
    dodgy in how it is written and can be cleaned up a bit.
    
    In particular, there is a real hodgepodge of private vs public going on. The
    initial code was all public and I implemented the new code as all private except
    where absolutely neccesary. However the classes should be gone over and given
    appropriate read or read/write access using property accessor methods.
    
    I want to do some investigations to see if there are any performance
    ramifications. Also I am rather unhappy with how the property accessor and the
    actual property can't have the same name because I hate "warty" members.
  • Day1
    This is the project code as of the end of the first day of Devember.
    
    Some initial porting has been completed, with some internal code notes of areas
    to focus on more once the initial porting effort is complete.
    
    These should be turned into issues to track them better, possibly added to the
    milestone.
  • Day0
    7cc9ee32 · Initial project check in ·
    This is the state of the project prior to any development being done for Devember.