Sleek 1.0 and a New Design
Published Friday 11th of March 2011
I've started sketching out ideas for a new version of Sleek. Sleek 0.1 really didn't get very far although the foundation is pretty solid.
Version 1.0 will follow the same structure as aFramework has since the first version.
Meaning, XML-files will represent each "Page". A node in said XML-files will represent a "Module" and a collection of pages and modules will be contained within a "Site".
I want to really plan out all the classes this time around and make sure each class handles just what it's supposed to.
The plan is to have 4 core classes:
- Sleek (wraps everything up)
- Site (handles everything that has to do with a site, keeps an array of pages (among other stuff))
- Page (handles everything that has to do with a page (XML-file full of modules), keeps an array of modules (among other stuff))
- Module (will be a wrapper for a module's code and handle module-functionality).
Particularly the Site and Module-classes are semi-new to Sleek and the idea is that they should handle a lot of what the current Sleek-class handles.
I've actually started looking a little bit at Ruby (off Rails, not on) but I'm not convinced yet that I should switch my language of choice.
I'm also keen on doing a new design for AndreasLagerkvist.com and if I ever finish Sleek 1.0 and the new design I think the next step is to set up a proper portfolio.
Right now I'm too busy with work to even have the energy to work on any personal projects but I think about this stuff before I fall asleep at night :) and when I get some spare time (and perhaps a co-coder this time around) I'll start work on the latest, and hopefully final, version of Sleek.
- Tags
- Comments
- 2 comments
Bookmark this Article