The framework portions of Inklog are not working out as well as I would have liked them to. The framework itself is starting to become too cluttered. Additionally, the blogging module is becoming more and more difficult to use.
So, this leaves me with two choices. Continue to plan the framework in hopes that I'll figure out a way to make everything work out nicely, or drop the framework portion and continue developing the weblog application.
I'll most likely choose the second option. If that is the case, inklog will end up being very similar to Blosxom with the following differences/enhancements:
- It will use PHP instead of Perl.
- It will use Smarty for its template needs (with the ability to be pointed at another template engine.
- Throught the use of formatters, it will accept any and all document types. A default formatter will be in place for those document types than cannot be deciphered.
- An entry will be capable of existing in multiple categories.
- Configuration options and plugin settings will exist on a per-directory basis.
- Documents will not only have a flavor, but also an optional action.
- No HTML will exist outside of the template files. Even the conversion routines will merely prepare an item and then call a template allowing complete and total customization without editing any code.
Now that I'm fairly certain that the framework isn't going to fit into this, I'm not nearly as excited as I was about it on Friday. I only wish I had more programming oriented minds near by to help me figure out what I'm missing to make all of this work the way that I want it to. I'm sure it's something small that I'm just over-looking.
