The tide of refactoring

I tried, but couldn't resist...Despite being incomplete, I'm refactoring Slick into a formal framework. The difference is small on the surface, but significantly impacts Slick's internals.

Basically, where I now define functions with

function S_initialize () {...}

I will now define them in a psuedo-class structure, like so

slick.core.initialize= function () {...}

JavaScript has been able to do this since day 1. It may simply be the evolution of good JavaScript practices, but I saw this in the dojo toolkit and decided it was the best way to implement Slick.

Using a centralized object model uses a smaller namespace footprint, contextualizes the relationship between objects and better encapsulation. More so, it should make it easier for developers to understand the system, and encourage improvements.

I'll share more, on how dojo's amazing toolkit has inspired me to complete Slick. Slick 1.5 (or 2.0) will eventually use dojo to manage it's event wiring functionality.