Template engines and more...
Posted: Tue Aug 15, 2006 7:15 pm
I want to start on version 2.0 of my next CMS incarnation...
This time, using everything I've learnned building a file based CMS in conjunction with my years experience using DB driven web sites...
I think I've finally solved the crux of my problem, when using a CMS, but I'll leave that for another disscussion...I will say it has been solved at a conceptual level, which is what was really holding me back, bot so much the back end or implementation specific reasons...
Anyways, I would like to eventually release as open source, but also keep it commercial...I would release under something like LGPL, but would offer dedicated hosting, etc... as original developers of the CMS. Infact I want it to be slightly more...in the sense I'd like it to also act as an advanced file manager, upload, etc...also ability to create HTACCESS files, CHMOD directories, etc...and most possibly manage emails and sub-domains, etc...
A little over the top perhaps, but I've always wanted to offer an all in one package...
Anyways, soon I will likely start posting object API's which I need developed, for instance a login API, etc...which I will submit in the volunteer forum for anyone interested in participating...first I need to hammer out some new coding conventions, as admittedly mine are somewhat antiquated and an disscussion I had with arborint a while back has made me think twice about some of my conventions...
For instance, in C++ I used hungarian notation and when I switched to PHP that idea trancended somewhat although I used less specific types...
$arr_names, $str_address, etc...
I'm considering dropping the prefix in favour of brevity...and besides "address" in todays languages kind of assume the type "string" anyways right?
So if your interested in helping me re-hash some conventions and don't mind a stubborn coot reconsidering everything you say...that would be awesome...
Anyways, right now, i'm really working on file structure, application extensability, etc...basically I spend a great deal of time planning and designing...more so than programming on most projects I undertake...
I simply can't be bothered to hack out that extra fast bit of regex when members on here are already capable of giving me a quick and efficient answer...same goes for MySQL, etc...
Ok I'm done sucking up...
Seriously, while sketching out concepts, etc...I've strongly consider using AKAPJ adodb and template lite...
The problem is, I've also been working on my own ORM for a while and would like to see if it actually works as I think it might...same with a template engine...completely different approach to rendering templates than what exists today, but this isn't even in POC state yet so I might just wait that one out...
I would ideally prefer to just use a hi level API which would be called like: create_page($id, etc...) and would sanitize incoming data, etc and create the record...using a direct call to mySQL (I have zero plans on ever using any other DB engine to be honest)
As a future open source project, if you were to help out or contribute...would you prefer AdoDB and TL???
Or could I get away with hardcoding the MySQL, knowing I'd never need anything else realistically...same goes for template engines...
I use a PHP template engine...simple and same effects, but requires discipline...as templates can quickly get ugly and fast...but has the advantage of being low in fat and easy to modify for custom caching, etc...
Have a Google for bTemplate to basically see what I use...fast, effective and crazy flexible, as you use PHP as the native template language...
Comments, opinions, etc...?
Remember, for now this is all hypothetical...I haven't coded a single line yet, but hammered out quite a few details on paper...in concept it seems pretty solid...
Cheers
This time, using everything I've learnned building a file based CMS in conjunction with my years experience using DB driven web sites...
I think I've finally solved the crux of my problem, when using a CMS, but I'll leave that for another disscussion...I will say it has been solved at a conceptual level, which is what was really holding me back, bot so much the back end or implementation specific reasons...
Anyways, I would like to eventually release as open source, but also keep it commercial...I would release under something like LGPL, but would offer dedicated hosting, etc... as original developers of the CMS. Infact I want it to be slightly more...in the sense I'd like it to also act as an advanced file manager, upload, etc...also ability to create HTACCESS files, CHMOD directories, etc...and most possibly manage emails and sub-domains, etc...
A little over the top perhaps, but I've always wanted to offer an all in one package...
Anyways, soon I will likely start posting object API's which I need developed, for instance a login API, etc...which I will submit in the volunteer forum for anyone interested in participating...first I need to hammer out some new coding conventions, as admittedly mine are somewhat antiquated and an disscussion I had with arborint a while back has made me think twice about some of my conventions...
For instance, in C++ I used hungarian notation and when I switched to PHP that idea trancended somewhat although I used less specific types...
$arr_names, $str_address, etc...
I'm considering dropping the prefix in favour of brevity...and besides "address" in todays languages kind of assume the type "string" anyways right?
So if your interested in helping me re-hash some conventions and don't mind a stubborn coot reconsidering everything you say...that would be awesome...
Anyways, right now, i'm really working on file structure, application extensability, etc...basically I spend a great deal of time planning and designing...more so than programming on most projects I undertake...
I simply can't be bothered to hack out that extra fast bit of regex when members on here are already capable of giving me a quick and efficient answer...same goes for MySQL, etc...
Ok I'm done sucking up...
Seriously, while sketching out concepts, etc...I've strongly consider using AKAPJ adodb and template lite...
The problem is, I've also been working on my own ORM for a while and would like to see if it actually works as I think it might...same with a template engine...completely different approach to rendering templates than what exists today, but this isn't even in POC state yet so I might just wait that one out...
I would ideally prefer to just use a hi level API which would be called like: create_page($id, etc...) and would sanitize incoming data, etc and create the record...using a direct call to mySQL (I have zero plans on ever using any other DB engine to be honest)
As a future open source project, if you were to help out or contribute...would you prefer AdoDB and TL???
Or could I get away with hardcoding the MySQL, knowing I'd never need anything else realistically...same goes for template engines...
I use a PHP template engine...simple and same effects, but requires discipline...as templates can quickly get ugly and fast...but has the advantage of being low in fat and easy to modify for custom caching, etc...
Have a Google for bTemplate to basically see what I use...fast, effective and crazy flexible, as you use PHP as the native template language...
Comments, opinions, etc...?
Remember, for now this is all hypothetical...I haven't coded a single line yet, but hammered out quite a few details on paper...in concept it seems pretty solid...
Cheers