Application controller / application.html.erb refactoring thoughts about ifme HOT 2 CLOSED

Okay, so I began refactoring the application html and application controller, but I ran into some trouble in that the "fetch commits" method is used for multiple different things. This led me down the rabbit hole, and now I'm drawing up model-level assocations that are missing.
I think the easiest way to refactor the codebase would be the following:

• add ActiveRecord associations between models
• move logic for rendering from views to their controllers, where possible
• fetch data needed for the views through for the controllers through associations
• condense views logic where needed

The benefit of this is that it will actually reduce the complexity of the codebase, and allow for new featured to be plugged in easier. Also, if you want to change a feature, it will require you to update code in far fewer places (for example, if you wanted to change how you fetch from fetch_taxonomies, you might have to change logic in 9 files right now).

Also the nice thing about this is that it won't break anything to do any single step. If somebody refactors the db and model associations, it shouldn't affect the controller or views. That way all changes are incremental, and it's not one huge project to do it all. :)

Edit: Anyway, the way I got here is that "fetch_taxonomies" is actually just a replacement for things that ActiveRecord associations do.

from ifme.

I drew a picture. It's a little overwhelming at first so I tried to break it up using whitespace. Are other users capable of commenting on anything besides strategies? I couldn't find anywhere else on the site.

from ifme.