Still active?

[Steve Flinter]

Is anybody still using Comatose, or actively developing for it? The
github logs would suggest not.

If not, what have people decided to use as a plugin-type CMS module
for Rails?

[David Vrensk]

On Wed, Jan 20, 2010 at 16:15, Steve Flinter <sfli...@gmail.com> wrote:

Is anybody still using Comatose, or actively developing for it?  The
github logs would suggest not.

I'd say that despite the version number, Comatose is mature.  I've used it for years and it does its job well.

/David

[Ron Evans]

I am using Camotose in production, and it has been running really well
for some time. I have even upgraded the app itself thru a couple major
Rails revisions, and it has been great!

> --
> You received this message because you are subscribed to the Google Groups "Comatose Plugin" group.
> To post to this group, send email to comatos...@googlegroups.com.
> To unsubscribe from this group, send email to comatose-plug...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/comatose-plugin?hl=en.
>
>
>
>

--
Ron Evans
310-597-1013
ron....@gmail.com

[Paul Doerwald]

My organization, Liquid Media, is working on a micro-CMS like Comatose that we are calling "Rain". It still needs a bit more design love and documentation, but we're hoping to open source it in the next few weeks. If you or anyone else is interested in it, please let me know and I'll let you know when it's done (or you can follow @liquidmediaca for the announcement).

Paul.

[Bret Weinraub]

Maybe you can publish the release notice here?  Sounds interesting!

Can some one on the ruby side save us from this Drupal/Joomla agony!!!!!

-b

--
-Bret Weinraub
"You're going to need a bigger boat...."

[Paul Doerwald]

Oh, that is EXACTLY my plan! I don't want to be in a position where a client asks me about a problem and the honest answer is "Drupal will solve that for you better than Rails would".

Too many clients of ours need some CMS functionality, or a fair bit of CMS, but I don't want to point them at Radiant because that's not actually the best solution for their problems, and I'm not interested in working with Drupal/Joomla. Comatose is a step in the right direction, but it's not quite "there". I can't quite express where I see the shortcoming; technically Comatose is fine, but there's a user aspect that isn't completely working for my clients. Rain is intended to integrate itself more tightly with Rails as well as your app, while still being a clean and separate API (i.e. no crazy hacks, and no weird monkey patching). You add a bunch of "drops" to your page, and each one is editable via a whizzy window the zooms in. Works for whole pages as well, just like comatose.

I've uploaded a couple images that will hopefully whet your appetite. The site you're seeing is not in production yet but we hope for it to be ready in the next couple weeks.

http://liquidmedia.ca/rain/before.png

http://liquidmedia.ca/rain/rain.png

One of the major problems I still want to solve is how to handle image attachments — i.e. user wants to enter some text and associate a couple pictures with it. It's a really simple request, yet it's surprisingly difficult for a user to pull off without knowing HTML. We want to offer some simple tool that makes it easy for them to attach a picture to their document. 

I'd love feedback and input and ideas.

Rain will, of course, be fully open sourced, FYI.

Paul.

[Bret Weinraub]

You might want to form a little working group  to help you identify your requirements.  I think that's where Comatose came up short.  It should be everything you need and nothing you don't; not "most of what you need and nothing you don't".

Go for it!  

-b

[Paul Doerwald]

Good idea. Right now we're still trying to address the actual needs our clients have, which will at least keep it to everything *we* need. As for whether or not it's what *you* need, well yes, the working group should help figure out those requirements... but we'll answer the *we* case first :-).

Paul.

[Tim Uckun]

> Too many clients of ours need some CMS functionality, or a fair bit of CMS,
> but I don't want to point them at Radiant because that's not actually the
> best solution for their problems, and I'm not interested in working with
> Drupal/Joomla. Comatose is a step in the right direction, but it's not quite
> "there". I can't quite express where I see the shortcoming; technically
> Comatose is fine, but there's a user aspect that isn't completely working

There are other CMS packages out there besides radiant. BrowserCMS
seems to be pretty active,

To be honest none of them have the functionality of drupal or joomla
because as far as I can see none of them have the same plugin capacity
or the community.

[Bret Weinraub]

The piece I seemed to be missing (in both Comatose and Radiant) was menu support.  Or is that there and I just can't find it!?  How bout in BrowserCMS?  Am I right that's there's a free ruby version and also a BrowserCMS out there which is a commercial product?

--
You received this message because you are subscribed to the Google Groups "Comatose Plugin" group.
To post to this group, send email to comatos...@googlegroups.com.
To unsubscribe from this group, send email to comatose-plug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/comatose-plugin?hl=en.

[Tim Uckun]

On Thu, Jan 21, 2010 at 11:35 AM, Bret Weinraub <bretwe...@gmail.com> wrote:
> The piece I seemed to be missing (in both Comatose and Radiant) was menu
> support.  Or is that there and I just can't find it!?  How bout in
> BrowserCMS?  Am I right that's there's a free ruby version and also a
> BrowserCMS out there which is a commercial product?
>

It's open source.

One thing I should also mention is communityengine which is not a CMS
per-se but does have a plugin facility.

[Paul Doerwald]

Rain has menu support in what we're (and we're *really* stretching the metaphor :-) ) call "waterfalls".

Rain is definitely trying to be a micro-CMS like Comatose. Even going as far as Radiant is too far, and if you need the functionality of Drupal, then you should use Drupal. I find most of the time, my clients *don't* need that much power; they need some simple admin-facing content editing, plus the kind of stuff you usually do in a Rails app.

Paul.

[Tim Uckun]

On Thu, Jan 21, 2010 at 4:15 AM, Steve Flinter <sfli...@gmail.com> wrote:
> Is anybody still using Comatose, or actively developing for it?  The
> github logs would suggest not.

Looks like back in march or so bunch of people forked it and have made
changes to it. Are there any plans to incorporate those patches back
into the "official" repo?