Katrina Owen d5a555fbac Encapsulate dependencies of stats index page ... This may be a bit extreme. It's modeled after the ideal "rails way". In the controller, we now know the name of a single resource. It doesn't happen to be backed by a database table, but it does know all about the task of collecting stats, leaving the controller concerned with just munging params and rendering stuff. I called the resource `IndexPage`, to avoid the temptation of trying to reuse it, which can get pretty messy. Later, if a better abstraction appears, it should be fairly painless to alter.		2013-03-02 17:35:19 -07:00
..
actions.rb	Move time to complete stats into separate class	2013-03-02 16:16:45 -05:00
chart.rb	Extract chart value object	2013-03-01 20:38:24 -05:00
contexts.rb	Group context-related pieces in a class	2013-03-02 17:21:03 -07:00
index_page.rb	Encapsulate dependencies of stats index page	2013-03-02 17:35:19 -07:00
projects.rb	Group project-related stats into a class.	2013-03-02 17:12:14 -07:00
tag_cloud.rb	Split up the font size calculation	2013-03-02 07:14:52 -05:00
tag_cloud_query.rb	Separate query from cloud	2013-03-01 13:14:27 -05:00
time_to_complete.rb	Don't round in ttc.min_sec method	2013-03-02 16:16:45 -05:00
top_contexts_query.rb	Group context-related pieces in a class	2013-03-02 17:21:03 -07:00
top_projects_query.rb	Extract top projects query object	2013-03-01 23:11:44 -05:00
totals.rb	Encapsulate counts and totals into a class.	2013-03-02 17:22:15 -07:00
user_tags_query.rb	Extract duplicated query	2013-03-01 21:27:58 -05:00