How are things coming along in otThreads? you might ask? I assure you that this is not a vaporware first of all. I’ve been working hard on the design, not your usual WEB DESIGN but the design of the application. So far so good though! After I started unit-testing using PHPUnit, I gotta say I’ve expanded my vision to a whole new level.
Right now I’m working on two classes, otThreads_Profile and otThreads_Utils_File (wrapped around DirectoryIterator). otThreads_Profile is quite the future of the system itself I must say, it’s simple, there are TWO types of configurations, the framework (system) configuration and the board configuration.
To put it more appealing:
System Configuration:
- Makes it flexible for the developer to specify Extensions folder and Profiles folder
- The goal is to allow the developer do some heavy-lifting in the future.
- Work with The Hub (not going into details…)
Board configuration
- Manages template paths, attachments path, board path, baseUrl
- Manages to change secret salts
- Locale
- Roots ID
- Authorization Key
- Application Run Mode (Testing, production, development)
- Provides a way to put a failsafe template path incase the path provide misses some files
- And of course, database credentials
There is still a lot of work to do, I should be getting myself started on MVC but right now there are more pressing matters, finishing these classes will help the framework to be smart. I’m changing the notion of how Routes should be managed, maybe… I don’t like reinventing the wheel, but the idea will help extension developers a LOT. Like… shared routes?
Anyway, final notes… I’ve been studying the concepts of ACL.. and I gotta say, it’s freaking annoying, do not misunderstand me though I’m not dissing ACL in any way, it’s just that I gotta cover a lot of ground. Creating the ACL classes are going to be a challenge for me.
And… dependency injection rocks.
