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
..
assets	fix js for contexts and add i18n keys for closed contexts	2013-03-02 16:33:38 +01:00
controllers	Encapsulate dependencies of stats index page	2013-03-02 17:35:19 -07:00
helpers	Split up the font size calculation	2013-03-02 07:14:52 -05:00
mailers	initial upgrade to rails 3.2.3	2012-04-30 13:56:33 +02:00
models	Encapsulate dependencies of stats index page	2013-03-02 17:35:19 -07:00
views	Encapsulate dependencies of stats index page	2013-03-02 17:35:19 -07:00