Making Chuckslist RESTful

[kyrre]

This turns out to be a lot harder than what I'd expected.

Does anybody feel like helping me?

So far I've created an ads resource in my routes. I've split the
AdsController into an AdsController, a CategoryController and a
ParentCategoryController, and given their methods proper RESTful
names. This deprecates the admin interface with :admin_required
before_filters. The user system I've replaced with that of
Technoweenie's Altered Beast. Mind y'all I've only been doing Rails
for about a month, and I could sure use some help making the actual
controller code harmonize with the changes I've made.

But yeah, this way Chuckslist would become leaner and more elegant.

Let's do this!! :)

[kyrre]

http://weblog.rubyonrails.org/2006/7/20/scott-raymond-on-refactoring-to-rest

Gonzo Rails developer Scott Raymond has written an analysis of how he
refactored IconBuffet.com using RESTful routes. It's the most cogent
and compelling description of the benefits of a CRUDdy/RESTful design
that I've seen. He reduced the number of actions in the application by
25%, and reduced the size of his routes file from 16 lines to 3. Isn't
small beautiful?

[kyrre]

I also got to move more logic to the models...

http://weblog.jamisbuck.org/2006/10/18/skinny-controller-fat-model

On Apr 25, 1:43 pm, kyrre <kyrr...@broadpark.no> wrote:
> http://weblog.rubyonrails.org/2006/7/20/scott-raymond-on-refactoring-...

[kyrre]

If anybody can help me, please send me a mail?

[kyrre]

For what it's worth, this is what I have so far: http://pastie.org/187540

-- Kyrre