Hey,
A while ago i’ve written here that it was unlikely that the module system would get into MageDB because i simply didn’t know how to write it. After days of testing and help of some people (someone even wrote a sample module system) i finally have the ability to make such systems. Now that this isn’t a issue anymore some parts of MageDB will make a good profit out of it. So in case you didn’t got it yet. There is gonna be a module system in MageDB and it’s gonna be on the database system and perhaps some other parts as well.
I’ve also experimented a little with a flexible caching system (MageFlexibleCache : mageflexiblecache.mageprojects.com) and nearly completed it in just a few hours. it does need some fine tuning. this is how it’s currently working:
$cache = new MageFlexibleCache;
if ($cache->LoadCache(“MyExpensiveEcho”))
{
echo $cache->loadedcache;
}
else
{
$cache->Start(“MyExpensiveEcho”);
for ($i = 1; $i <= 10; $i++)
{
echo “The time is: ” . time() . “\n”;
}
$cache->End();
}
And this is working. It now first checks if a certain part is in a cache and if it is than it will load the cache, if it aint than it will just run the php code and put it in a .cache file so it will load it from the cache the next time. All that is need to be done in this caching is making it smart.. but in order to do that i need to make the code around the caching smart and leave the cache about the same. Things like this could be in MageDB 1.0.0 otherwise it’s gonna be somewhere in the MageDB 1.x.0 releases. This caching will make MageDB alot faster and way more query friendly than my current MageDB or any other file database script (paFileDB 
).
And than there is the ADOdb Lite library. lets put it simple. it’s still to big for my taste and uses to much memory. i’m gonna make my own db wrapper with the module system that i just made. Initially i will make modules for MySQL and MySQLi so (hint hint) this will most likely mean that MageDB is gonna work on MySQL and MySQLi and i hope to make SQLite and PostgreSQL modules in later versions. I think i might release this db wrapper as well as: MageDatabaseWrapper(?) (magedatabasewrapper.mageprojects.com).
Than there is the (still) bulky Template Lite template engine. i think that it’s also to big for what i want to do with it. going the way of phpBB would be fine for me + i need it to be able to exclude certain parts in the templates (like i posted 1 or 2 posts ago).. i don’t really know if i’m gonna:
1. Modify Template Lite to my needs
2. Leave it the way it is.. (means no smart caching for MageDB (yet))
3. Drop Template Lite and make my own of this as well and perhaps call it: “MageTemplateEngine” (and : magetemplateengine.mageprojects.com)
Than last but not least.. the progress on MageDB itself at this moment.
I did do a few things but it are only layout changes. not any php coding. The public part is getting close to be done. The admin part and personal control panel are still not done (admin panel needs rewrite, personal control panel needs some bindings and more options) once the admin cp, the personal cp and the public part are either done or good enough to use than MageDB 0.1.0 Alpha will be released to the public. This release won’t have all the ajax goodies i promised earlier nor will it have all the features but than again it isn’t final as well.
I expect to release 5 alphas, 3 beta, 1 rc and 1 final
// Everything can change here
MageDB 0.1.0 = Alpha 1
MageDB 0.2.0 = Alpha 2
MageDB 0.3.0 = Alpha 3
MageDB 0.4.0 = Alpha 4
MageDB 0.5.0 = Alpha 5
// A lot can change but no major changes (ex: other them or new name etc..)
MageDB 0.6.0 = Beta 1
MageDB 0.7.0 = Beta 2
MageDB 0.8.0 = Beta 3
// This release will only feature bug fixes
MageDB 0.9.0 = RC 1
// If No bugs are found in RC 1 than this is mainly RC 1 with some cleaned code. otherwise the bugs from RC 1 are fixed in here and be released as Final.
MageDB 1.0.0 = Final version 1.0.0
That’s is for this (_long_) blog post.
Till next post.
