The release targets all of the issues listed before
CHANGELOG
FIXED: spaces in file names are escaped as dashes "-" when uploaded FIXED: various bbcode issues FIXED: scale/width bbcode/thumb issues MDFD: now thumb creates a .thumb dir for each subdir of images/ FIXED: leggero CSS FIXED: double entity encoding ADDED: (since RC1): when loggedin trying to open a non-existent static page will bring you to the "add new static" panel
Sunday, June 3, 2007 - 21:46:29
You know man, I was thinking, wouldnt it be better to use a proper framework? (I’d suggest CodeIngation)
First of all the whole development process would speed up many times.
Plus, anyone would be able to -easily- add the code that he would want to.
But anyway, its up to you… :P
Monday, June 4, 2007 - 17:05:11
I did think about that, mate, but at the time I started up there was no framework that would fit (IMO) and/or they were too big-size and/or they were too much tight to a DB back-end which, as you know, is what we wanted to avoid ;)
moreover there was much less hype about all these new MVC frameworks that are rising now, trying to follow the success if Ruby-on-Rails
By the way, if I had to start over, I would probably try to choose one of those, such as PHPCake; anyway we are slightly based on pieces of other “frameworks”, we took a bit from WordPress (so the name: we took the plugin interface and some of the library) and we’re using the well known and documented Smarty template engine
bye
Thursday, June 7, 2007 - 20:28:33
Another thought of mine, are friendly URLs, and scheduled posts. I am willing to pay a coder to do that for you if you will accept that contibution in the main core release!
URL of that style:
category/name-of-post/
and
CategoryID/postID
Thursday, June 7, 2007 - 20:54:04
friendly urls (prettyurls plugin) are *already* in the works! :) [1]
I still did not release them (and removed the plugin) as they would require some changes in the core, so I was planning to release in Crescendo+1.
As they are now, they involve too many tricks with mod_rewrite regexes; these changes would make obsolete the comments.php and statics.php files: all would be handled by a master index.php; this way mod_rewrite’s job would be only to remove “index.php” from the URL (as WP already does).
I’m still thinking about it, though, I would remove those comments.php and static.php; would you mind that? Should I add two dummies so that they redirect on index.php ? (it could be done with an .htaccess but I’m thinking about cheap hosting with no mod_rewrite enabled)
Scheduled posts would be a nice-to-have feature but it needs some thought (plugin, maybe? which hooks would we require?).
BTW, I think this summer I may have a look at those; at least for the URLs path which is almost done; really I’m mad, so probably I’ll take this occasion to do some rework on how the infrastructure currently works too.
Now we have some master classes which tell the system “which kind” of page (static, comments, etc) you’re viewing; if system will become centralized on index, this may need some rethinking.
This summer may be time to think about the way plugin will hook the control panel, a feature needed, but still not refined.
Moreover, I’d like to turn widget and plugin panels into something user-friendlier.
You see, here’s a draft of a roadmap :)
[1] well maybe not right now, exams, you know…