I meant can't he just finish it and everyone stop arguing
whenever som1 releases something there always an argument.
Printable View
If you haven't noticed, he hasn't posted in this thread in ages, he probably doesn't give a flying **** about it anymore..
If he wanted to work on it, he would.. he's not going to if he doesn't want to.
------------------------
To be honest, if you don't like the arguments.. don't read them.
Most of the core classes are done.
I'll probably get started on the backend functions for each page in a week or two.
Then after that it will be a lot of frontend work, and making the UI nice.
For the record, I will be releasing it with a very basic template, as it is either going to use Smarty, which I'll implement later, or it'll use a templating system that I code myself. Probably the latter, as I can't really be bothered to learn Smarty, I can only do the basics right now.
@L?KE: I understand that it will be kinda hard, but I'm going to make the templating system very basic, as I will probably code it, so it'll be like [@user_welcome_msg], and [@page_content], and [@menu] [@menu_item]<div> ..html code for a menu item.. </div> [/@menu_item][/@menu], and that will be about it, as I don't see any need for much else.
Why use _'s and not a camel readability type system:
EX: page_content, menu_item
EX: pageContent, menuItem
and I don't really like the idea of []'s.
{@phrase-welcome} looks better imo ;P
Just don't use the version of CamelCase where the first letter has to be capitalized, excluding class names that is.