Mar 09
7
Clay Framework: February Wrap up
Well, February has come and gone and what a difference a month makes. Clay went from a core using procedural programming and modules to [more] of an OO design, along with reduced backend.
The Sculpt template engine now occupies the tpl class, the name sculpt is only used in the namespace for its variable cache. The IAM module is no longer a module and occupies the app class, which is much slimmer. Clay still offers support for modules and is currently, mostly, static methods on the class side. Modules will likely be used for simple tasks, but can be used as a development phase for testing. I haven’t set the file structure design in stone, so things could shift around before all is said and done. Clay still works the same, minus the use of app(), api() and tpl(), along with the other functions that have moved to classes. It looks different on the file level and is easier to understand where things are coming from or going to when reading the code.
Much of the month went into shifting things around, so there isn’t a huge difference in the amount of code to show for. There has been some big improvements overall and I’ve learned a lot. Here’s to an even better March