the simple blogging engine
You are not logged in.
This is the scheduled roadmap for future versions of Kure. If you have a suggestion for a new feature, please use the Bugs / Suggestions forum. If you want to comment on, ask questions about, or suggest a modification to one of the already scheduled features below, feel free to use this thread.
(Thanks to Angeltc for the original roadmap suggestion.)
Future versions
0.8
-support for multiple administration users, including the ability to modify each user's admin privileges
Past versions
0.7
-implement templating and accompanied styles, plus the ability to choose a pair via the administration interface
0.6
-almost all administration implementations: interface, session/cookies, post editing/deleting, changing configuration variables (requires the creation of another file, but I've already got a system written on my laptop to handle this)
-continue migration to functions
0.5
-various improvements to post title and content filtering (disallow any characters that cannot be used in filenames, i.e. /:\?|)
-start the process of moving some actions into functions to increase efficiency (i.e. post filtering)
Last edited by skoh-fley (2008-11-04 08:29:38)
Offline
i would aim for theming capabilities to be added in 0.7, because the main admin interface work would be done by then and the way kure's html is set up allows for very little customization through css.
also change the prints to echos :D
Offline
Well there's the start of my own theme system ;)
All I did was basically cut out the print("") lines and put them in seperate files... That's about it.
But because of this there's still too much power in each theme file.
I wouldn't mind if the print data is put into arrays so the themes can handle any recursive printing etc...
Plus a consistent authenticated session would be helpful for 0.5 instead of 0.6.
Offline
i want to suggest two things for 0.5 actually, and really hope that we have this release really fast cause we have some prty big issues to fix
the first one is the plugin system.. and we all know that because of the way it's set up we can't have 'dynamic' plugins that change with the page. the best solution that i can see is to instead of running all plugins at the top of the page and then putting output in racks, that we put file paths to plugins in racks, and then kure runs those plugins when the rack is reached!
that way we can have dynamic plugins like a comment system.
edit: haha i forgot to write the second part
the second part is to rewrite Kure using multiple files, instead of one index file where less than 15% of the code is in use at any time.. it's also very messy and has so much duplicate code. i suggest that we go for functions in 0.5, because once we have functions theming will be much easier.
the third part is actually more realistically to be in 0.6, and thats to have a REAL theming capability. that means the ability to upload a html file with special placeholders, and have Kure replace the placeholders with data. its way more flexible if you think about it - you get to choose what appears, where, and how every element of it looks.
Last edited by Gigaman2003 (2007-10-12 01:11:10)
Offline
Im really a programmer wannabe, but the way I see plugins are implemented is messy with those dynamic outputs, however, "including" the php file in a specific place on the core, it will be actually more "ugly", I cant think about an example right now, however is just my idea of how do you suggest to implement plugins, if it works, then its totally OK.
About rewriting the code into multiple files, I dont know about it, Kure is going into a lot of changes and rewriting the code might be or might not be, a good idea, if we wait too long then rewriting the code will be too hard, if we do it too soon me might regret about it, in my personal opinion, I think we should do it before optimizating the code into functions.
Offline
Yep, higher use of functions is already in the 0.5 to-do.
If we decide that multiple files is the way to go, my opinion is that it should be done gradually, almost parallel with our other updates -- i.e. in 0.6, we'll move all the administration-related stuff out and build the admin interface around that newly-separated piece.
And I agree that the theming concept Giga was mentioning would be very nice to have; should we set that as a goal for 0.7? It's definitely something we'll want to implement after we convert completely to functions, and I don't want to delay the admin interface longer than I have to.
Offline
that means the ability to upload a html file with special placeholders
I second this!
Having PHP inside template files is not a good idea in the longer run.
It puts far too much power in the hands of the template designer...
We need some sort of tag replacement system.
Offline
i have been thinking about it, and we should really write an interface for saving data. that means that we can easily add new methods of storage if we want, and plugin writers can easily store their data like how the rest of the blog does. that means that we put ALL data retrieval/adding/editing functions inside it's own object, so that the main kure core will always look the same whether or not it uses PQL or normal flat-files
oh oh oh dooh i forgot, i should have posted a filestructure >:(
root/ admin/ index.php //Login and logout, session authentication handling post.php //Default page after logging in, same as what it is right now except with the ability to edit and delete a post. manage.php //Browse or search through data files data/ //Data gets stored here depending on the system the user chose index.php viewpost.php blank.php //This is something i'll explain further after this
if you're wondering what blank.php is, it's basically a plugin writer's joker card. it would be a file with all the hooks as usual, but a blank content area for total control. if i wanted to write a plugin that displayed a portal or something, right now i can only append stuff to the default kure code, but with blank.php, i can control the entire content area with my output!
Offline
Eksith wrote:
Blank.php would really come in handy for searching.
The sidebar search is nice, but doesn't really cut it for a long list of posts IMO.
hence the suggestion :)
i see it coming in handy for plugin admin panels too
Offline
Can you give us an estimate when you'll be releasing .6? It's basically everything that I would want added to kure :)
Last edited by Breepee (2008-01-27 13:56:42)
Offline
I'm not sure, I haven't had much free time on my hands lately. Now that finals are over I will probably be able to work on 0.5 more, but it'll probably be in small increments. 0.6 will need some serious sit-down-and-work time.
I don't want to try to guess, because it would be a really rough guess. I'm definitely going to try to dedicate as much time as I can to it over the next couple weeks, though.
Offline
bump.
should probably be updated to reflect the goal of templates in 0.7
Offline
Done :D
I'm excited about 0.6; it turns out there will be some perks for addon authors too :P
Offline
Oh you did NOT just bring the cookies into this.
edit: i meant the moist and tasty kind, not the nerd kind
Last edited by Gigaman2003 (2008-04-27 05:58:56)
Offline
Cookies! Cookies! Cookies!, I just love `em.
Im excited about authors already..
Offline
I'd like to see backward compatibility with plugins integrated, if that is at all possible (maybe for Kure 0.8).
It would also be neat to have a guest account with limited priviledges (for instance could post, but not delete not change settings). I suppose a "guest" password could suffice for that.
Offline
multi-user support could be a potential 0.8 goal
Offline
That's actually a really good idea. Along with multiple users we could have a permissions system to allow certain users to post but not change settings, or create posts but not docs, etc.
I'll put it on the roadmap; definitely something to shoot for.
EDIT: Also revamped the roadmap to be more permanent :)
Last edited by skoh-fley (2008-11-04 08:30:55)
Offline