Status of Comatose?

[Paul B. Adams]

What is the current status of Comatose? Is it still in active
development (The googe code pages indicate some bug activity but has
been quiet for several months) Is the svn trunk running under Rails
2.0? Will it run on the upcoming 2.1?

Also, how easy is it to restrict access to certain pages/page
hierarchies using acts_as_authenticated or similar gems?

Thanks for your patience with my pesky questions.

Regards,
Paul.

[Thibaut Barrère]

Hi Paul,

What is the current status of Comatose? Is it still in active
development (The googe code pages indicate some bug activity but has
been quiet for several months) Is the svn trunk running under Rails
2.0? Will it run on the upcoming 2.1?

I would not say that development is active. But it's actively used though. I'll try to take some time to package gem 0.9 with the current trunk (I've never done that on Comatose before though - only Matt ever released gems versions).

The trunk is compatible with Rails 2.0 thanks to Andrew fixes.

I don't know if it's compatible with Rails 2.1 (anyone ?).

 

Also, how easy is it to restrict access to certain pages/page
hierarchies using acts_as_authenticated or similar gems?

I've done that without much pain a couple of months ago. I guess it will depend on the complexity of what you need to achieve. Coarse-grained, hard-coded permissions will be very easy. Fine-grained, db-managed permissions is a bit more tricky and requires additional models and monkey patching (nothing fancy though).

Thanks for your patience with my pesky questions.

You welcome!

cheers,

Thibaut
--

[blog] http://evolvingworker.com - tools for a better day
[blog] http://blog.logeek.fr - about writing software

[zapnap]

I believe acts_as_list and acts_as_tree also need to be installed to a
Rails project before Comatose can be used? Or has this changed with
recent commits?

I'd love to see it updated to use the new view naming syntax also.
Seems to be stuck back in .rhtml land... Comatose is a great plugin
and I've used it in numerous projects, but I'd love to see it emerge
from this hibernation.

On May 3, 11:33 am, "Thibaut Barrère" <thibaut.barr...@gmail.com>
wrote:

> [blog]http://evolvingworker.com- tools for a better day

[Andrew Kuklewicz]

comatose is in hibernation - that's funny.

Anyway, we haven't bothered to change the pages from rhtml to html.erb - but that's kinda cosmetic, don't you think?
We did update them to be 2.0 compliant, using form_for and such things.

It's still getting love and there are a few committers running around answering questions, so while there are things that could be updated, I think this plugin is in a light, fitful sleep at best :^)

-Andrew

On Mon, May 5, 2008 at 2:29 PM, zapnap <npl...@gmail.com> wrote:

I believe acts_as_list and acts_as_tree also need to be installed to a
Rails project before Comatose can be used? Or has this changed with
recent commits?

Last I hear you need to get these - which I find ok - I don't want to have a version in the plugins dir and a version in comatose.
 

--
Andrew Kuklewicz

[Thibaut Barrère]

Hi Zapnap,

I'd love to see it updated to use the new view naming syntax also.
Seems to be stuck back in .rhtml land... Comatose is a great plugin
and I've used it in numerous projects, but I'd love to see it emerge
from this hibernation.

Are there specific points you'd find useful to see evolve? (feel free to talk!)

If you have patches to propose, please do as well.

cheers

-- Thibaut

[Andrew Kuklewicz]

See, that's what I like about Thibault.

That is a thoughtful and helpful response, as opposed to my amused, somewhat helpful, and slightly snide comment :)

-Andrew

--
Andrew Kuklewicz

[zapnap]

Don't get me wrong, it's all good and I definitely enjoy using
Comatose in projects. It's a great lightweight solution.

I know the rhtml vs html.erb change is largely cosmetic, but it'd
still be nice to see that push. Especially since it *is* just
cosmetic.

Also, am I wrong about acts_as_tree and acts_as_list? Shouldn't those
either be included or explicitly doc'd in the README as required
prerequisites since they've been removed from Rails 2.0.x?

Other than that, I don't see any real changes that are needed...
Everything works just fine here!

..nap

On May 5, 5:15 pm, "Andrew Kuklewicz" <kooks...@gmail.com> wrote:
> See, that's what I like about Thibault.
>
> That is a thoughtful and helpful response, as opposed to my amused, somewhat
> helpful, and slightly snide comment :)
>
> -Andrew
>

> On Mon, May 5, 2008 at 4:14 PM, Thibaut Barrère <thibaut.barr...@gmail.com>

[Thibaut Barrère]

See, that's what I like about Thibault.

That is a thoughtful and helpful response, as opposed to my amused, somewhat helpful, and slightly snide comment :)

Hehe... Glad you appreciate! And thanks for helping out as well.

I believe zapnap's opinion shows that we need to polish things a bit and release a v1.0 - one that will properly reflect the current state of the code.

One bug bugs me quite a bit. Does anyone have a fix for this? Is it ok to ship v1.0 with it, or with a work-around fix?

cheers

-- Thibaut