mattmccray

 
« Monstas of the Lil' V… | Home | Comatose and PostgreS… »

Comatose, TNG

» Published July 18, 2006 under Comatose, Rails, Software

The response I’ve gotten on Comatose is somewhat overwhelming. I’m glad so many of you have found it useful!

Hopefully I won’t annoy you guys too much with the next release… It has quite a lot of updates, and changes. Enough to warrant this post on it as a kind of ‘heads up’.

If you’ve made customizations to the admin, and if you have used an svn:external to keep up to date with Comatose — you may want to remove the external and commit the current version (0.5) into your plugin directory… Otherwise you will need to tweak some things when I commit the next version.

In the next release, what is now the ComatoseController is going to be broken down into two separate controllers. There will still be a ComatoseController, it’s purpose will be rendering and caching pages. A new ComatoseAdminController will be the home for all of the administration tools. They will each have a before_filter that calls #authorize for authentication purposes.

The way layouts are handled internally has changed too. The controllers will now extend your ApplicationController, so you should be able to use partials and application helpers in your content layouts.

The biggest change, however, is in the page processing. Liquid will be the new default text processor. Don’t panic — ERB will still be available as a configuration option. But I really want a safer way to support content processing. To go along with that, I’m adding a simple method for adding custom functions to the processors that’ll work for both Liquid and ERB. Also, Liquid will be packaged with the plugin, so you won’t have to worry about having it as a dependency.

There are, at this point, no schema changes — so there won’t be a need for new migrations. There’s quite a few more changes I could talk about, but these are the main things that are some-what breaking changes.

I’ll be releasing the new version later this week.


7 comments

07.18.06 @ 14:41 mikkel said...
... The controllers will now extend your ApplicationController…
YAY! I had to resort to an ajax hack to show partial and hack a bit in ComatoseController

Some stuff:

  • Add created_on to the ComatoseBinding

  • Do NOT mess with updated_on with reordering



thanks…

I am looking forward to TNG...
07.18.06 @ 14:53 M@ said...
Hmm… I may go ahead and add the created_on field. It would definitely make sense for sites like yours that use comatose for ‘News’ and things where the date is important.

I’m going to have to look at preventing reordering from updating the updated_on field. I’m not doing anything explicitly for it… It’s part of Rails magic. I may have to resort to using straight SQL to update it… But I haven’t looked into it too deeply yet.

Thanks for the suggestions.
07.18.06 @ 14:53 manuel said...
Wow! That was fast.

Keep up the good work!
07.18.06 @ 23:39 mikkel said...
m@: I would rather use a created_on than updated_on for sorting of news…so there is two solutions to the problem ;-)

anyways…im going to add a created_on field in my installation….
07.19.06 @ 02:48 Martin Wulffeld said...
Looks great. Matt, do you have a project page for this somewhere?
07.19.06 @ 14:18 M@ said...
Actually, I’m in the process of creating a rubyforge project for Comatose. If/When it’s approved, I’ll post a link to it.
07.23.06 @ 11:42 M@ McCray » Comatose v0.6 said...
[...] Turns out I spoke too soon in my earlier post, there is a schema change. So if you’re upgrading you’ll need to run: [...]

No trackbacks

Trackback link:

Please enable javascript to generate a trackback url


You may use Textile, or simple html tags (B,I). Feel free to use Emoticons too. Oh, and please limit yourself to only five links per comment. Anything more and you'll probably get detained by the spam police.