mirror of
https://github.com/TracksApp/tracks.git
synced 2025-12-26 20:08:51 +01:00
d5a555fbac
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. |
||
|---|---|---|
| .. | ||
| _actions.html.erb | ||
| _chart.html.erb | ||
| _contexts.html.erb | ||
| _contexts_list.html.erb | ||
| _null_list_item.html.erb | ||
| _projects.html.erb | ||
| _projects_list.html.erb | ||
| _tags.html.erb | ||
| _time_to_complete.html.erb | ||
| _totals.html.erb | ||
| actions_completion_time_data.html.erb | ||
| actions_day_of_week_30days_data.html.erb | ||
| actions_day_of_week_all_data.html.erb | ||
| actions_done_last12months_data.html.erb | ||
| actions_done_last30days_data.html.erb | ||
| actions_done_last_years.html.erb | ||
| actions_done_lastyears_data.html.erb | ||
| actions_open_per_week_data.html.erb | ||
| actions_running_time_data.html.erb | ||
| actions_time_of_day_30days_data.html.erb | ||
| actions_time_of_day_all_data.html.erb | ||
| actions_visible_running_time_data.html.erb | ||
| context_running_actions_data.html.erb | ||
| context_total_actions_data.html.erb | ||
| done.html.erb | ||
| index.html.erb | ||
| show_selection_from_chart.html.erb | ||