Archive

Posts Tagged ‘configuration’

Release 0.3!

November 23, 2011 Leave a comment

Whew! It’s been a while but my 0.3 has now been released! In this release, I’ve been working on Paladin/configurator subsystem. By now, it has become quite mature and achieves all required functionality. Also being used is IndexedDB as the load/store backend. Also important is that the codebase has now been brought up-to-date with the rest of the engine.

Changelog:

  • Added comments to all of the Configurator tests that didn’t have any. Improved some of the comments that were there before as well as improving some test structures slightly.
  • Removed Cookie.js from the engine. Cookies are no longer used as load/store backend, now replaced with IndexedDB.
  • Many functions had vague local variable names; their names have been improved.
  • load/store are now both asynchronous.
  • Added config/default.js for local configurations that need to be baked into the engine.
  • Configurator now uses gameID to load/save configurations.
  • Brought Configurator codebase up-to-date.

commit: a94ea288daabd84ea222a5a08da78ec4095479b3

issue thread: https://github.com/alankligman/gladius/issues/21

pull request: https://github.com/alankligman/gladius/pull/52

I also have some work to do for XSS Me but that has taken a back-seat to the work on Paladin. Currently, the plan is to dedicate most of 0.4 towards XSS Me. We’ll see how this all pans out.

Configuration Registry 0.2

October 29, 2011 Leave a comment

I am now calling the 0.2 version of the configuration registry released! The configuration registry is now almost completely useable. In this revision, I’ve implemented loading/storing to local browser storage ( ie a cookie ); as well, clearing and JSON serialization were implemented in this revision. The new features are backed up by rigorous ( more or less 🙂 ) unit tests.

The only thing left to implement is loading using xhr. Due to the lack of a good way to unit test xhr, I’ve been hesitant to start writing this feature in. Version 0.3 of this bug will include xhr loading.

Since only xhr loading is left, I plan to start working on other bugs/other projects for the 0.3 release.

I look forward to my code being reviewed. If you have the time, come over to the pull request thread and drop a word or two 🙂

Pull request: https://github.com/alankligman/gladius/pull/52#issuecomment-2563950
Issue thread: https://github.com/alankligman/gladius/issues/21

Configuration Registry, Rel 0.1

September 29, 2011 Leave a comment

For the past little while, I’ve been working on a particular issue in Paladin’s issue tracking system. That issue proposes the creation of a configuration registry subsystem that will someday determine which Gladius subsystems execute and with which options.

At the moment, setting configuration options in Gladius is a bit of a mixed bag; this new subsystem should improve the state of things.

Tonight is my first milestone in the creation of this subsystem. I’ve written my ideas on how the subsystem will be designed and will operate, ( https://github.com/northWind87/gladius/wiki/Issue-21—Configurator-Registry-Design )
and I’ve also written the bulk of the unit tests that will tell us when the subsystem is more or less ready for primetime ( https://github.com/northWind87/gladius/blob/develop_issue_21/test/core/Configurator.js ).

Guys, humph, take a look and tell me what you think. I’d very much like someone to tell me in which specific ways my tests are terrible, I think that I would appreciate that a lot 🙂

I’ve always liked the TDD approach (http://en.wikipedia.org/wiki/Test-driven_development ) and hopefully the many scanning eyes of the internet can tell me where I can improve!

Cheers guys and good luck with all of your 0.1 releases!