diff --git a/rowers/templates/trainingplan.html b/rowers/templates/trainingplan.html index 721d6539..8a54c518 100644 --- a/rowers/templates/trainingplan.html +++ b/rowers/templates/trainingplan.html @@ -9,12 +9,6 @@ {% endblock %} {% block content %} - -
| - {{ macrocycle.0.name }} ({{ macrocycle.0.startdate }} - {{ macrocycle.0.enddate }}) - | -||||
|---|---|---|---|---|
| - | dist (m) | -t (min) | -rScore | -TRIMP | -
| plan | -{{ macrocycle.0.plandistance }} | -{{ macrocycle.0.plantime }} | -{{ maccrocycle.0.planrscore }} | -{{ macrocycle.0.plantrimp }} | -
| actual | -{{ macrocycle.0.actualdistance }} | -{{ macrocycle.0.actualtime }} | -{{ macrocycle.0.actualrscore }} | -{{ macrocycle.0.actualtrimp }} | -
| - | ||||
| - edit - / - delete - / - sessions - | -||||
| - {{ mesocycle.0.name }} ({{ mesocycle.0.startdate }} - {{ mesocycle.0.enddate }}) + {{ macrocycle.0.name }} ({{ macrocycle.0.startdate }} - {{ macrocycle.0.enddate }}) | ||||||||
|---|---|---|---|---|---|---|---|---|
| dist (m) | @@ -109,51 +57,59 @@||||||||
| plan | -{{ mesocycle.0.plandistance }} | -{{ mesocycle.0.plantime }} | -{{ mesocycle.0.planrscore }} | -{{ mesocycle.0.plantrimp }} | +{{ macrocycle.0.plandistance }} | +{{ macrocycle.0.plantime }} | +{{ maccrocycle.0.planrscore }} | +{{ macrocycle.0.plantrimp }} |
| actual | -{{ mesocycle.0.actualdistance }} | -{{ mesocycle.0.actualtime }} | -{{ mesocycle.0.actualrscore }} | -{{ mesocycle.0.actualtrimp }} | +{{ macrocycle.0.actualdistance }} | +{{ macrocycle.0.actualtime }} | +{{ macrocycle.0.actualrscore }} | +{{ macrocycle.0.actualtrimp }} | +
| - | ||||||||
| - edit + edit / - delete + delete / - sessions + sessions | ||||||||
| - {{ microcycle.name }} ({{ microcycle.startdate }} - {{ microcycle.enddate }}) + {{ mesocycle.0.name }} ({{ mesocycle.0.startdate }} - {{ mesocycle.0.enddate }}) | ||||||||
|---|---|---|---|---|---|---|---|---|
| dist (m) | @@ -163,59 +119,141 @@||||||||
| plan | -{{ microcycle.plandistance }} | -{{ microcycle.plantime }} | -{{ microcycle.planrscore }} | -{{ microcycle.plantrimp }} | +{{ mesocycle.0.plandistance }} | +{{ mesocycle.0.plantime }} | +{{ mesocycle.0.planrscore }} | +{{ mesocycle.0.plantrimp }} |
| actual | -{{ microcycle.actualdistance }} | -{{ microcycle.actualtime }} | -{{ microcycle.actualrscore }} | -{{ microcycle.actualtrimp }} | +{{ mesocycle.0.actualdistance }} | +{{ mesocycle.0.actualtime }} | +{{ mesocycle.0.actualrscore }} | +{{ mesocycle.0.actualtrimp }} | +
| - | ||||||||
| - edit + edit / - delete + delete / - sessions + sessions | ||||||||
| + {{ microcycle.name }} ({{ microcycle.startdate }} - {{ microcycle.enddate }}) + | +||||
|---|---|---|---|---|
| + | dist (m) | +t (min) | +rScore | +TRIMP | +
| plan | +{{ microcycle.plandistance }} | +{{ microcycle.plantime }} | +{{ microcycle.planrscore }} | +{{ microcycle.plantrimp }} | +
| actual | +{{ microcycle.actualdistance }} | +{{ microcycle.actualtime }} | +{{ microcycle.actualrscore }} | +{{ microcycle.actualtrimp }} | +
| + | ||||
| + edit + / + delete + / + sessions + | +||||
Click on the plan cycles to edit their names, start and end dates. The gray "filler" - cycles are generated, adjusted and deleted automatically to ensure the entire plan - duration is covered with non-overlapping cycles. - Once you edit a filler cycle, it become a user-defined cycle, which cannot be deleted - by the system.
-Filler cycles which have a filler cycle as a parent cannot be edited - or deleted. You have to edit the parent cycle first. The reason is - that children of filler cycles are not safe. They are deleted when - their parent is deleted by the system.
-Click on "Sessions" in the cycle of your interest to see details - of the individual training sessions planned for this period.
-A good way to organize the plan is to think of micro cycles as training weeks. Macro cycles - are typically used to address specific phases of preparation and to indicate the racing - season and may span several months. - Meso cycles can be used to group sequences of three to five light, medium and - hard weeks. It is recommended to work from left to right, starting with the macro cycles.
+ +Click on the plan cycles to edit their names, start and end dates. + The gray "filler" + cycles are generated, adjusted and deleted automatically to + ensure the entire plan + duration is covered with non-overlapping cycles. + Once you edit a filler cycle, it become a user-defined + cycle, which cannot be deleted + by the system.
+Filler cycles which have a filler cycle as a parent cannot be edited + or deleted. You have to edit the parent cycle first. The reason is + that children of filler cycles are not safe. They are deleted when + their parent is deleted by the system.
+Click on "Sessions" in the cycle of your interest to see details + of the individual training sessions planned for this period.
+A good way to organize the plan is to think of micro + cycles as training weeks. Macro cycles + are typically used to address specific phases of preparation + and to indicate the racing + season and may span several months. + Meso cycles can be used to group sequences of three to five + light, medium and + hard weeks. It is recommended to work from left to right, + starting with the macro cycles.
This plan starts on {{ plan.startdate }} and ends on {{ plan.enddate }}. The training plan target is: {{ plan.target.name }} on {{ plan.target.date }}.
+ +| + {{ macrocycle.0.name }} ({{ macrocycle.0.startdate }} - {{ macrocycle.0.enddate }}) + | +||||
|---|---|---|---|---|
| + | dist (m) | +t (min) | +rScore | +TRIMP | +
| plan | +{{ macrocycle.0.plandistance }} | +{{ macrocycle.0.plantime }} | +{{ maccrocycle.0.planrscore }} | +{{ macrocycle.0.plantrimp }} | +
| actual | +{{ macrocycle.0.actualdistance }} | +{{ macrocycle.0.actualtime }} | +{{ macrocycle.0.actualrscore }} | +{{ macrocycle.0.actualtrimp }} | +
| + | ||||
| + edit + / + delete + / + sessions + | +||||
| + {{ mesocycle.0.name }} ({{ mesocycle.0.startdate }} - {{ mesocycle.0.enddate }}) + | +||||
|---|---|---|---|---|
| + | dist (m) | +t (min) | +rScore | +TRIMP | +
| plan | +{{ mesocycle.0.plandistance }} | +{{ mesocycle.0.plantime }} | +{{ mesocycle.0.planrscore }} | +{{ mesocycle.0.plantrimp }} | +
| actual | +{{ mesocycle.0.actualdistance }} | +{{ mesocycle.0.actualtime }} | +{{ mesocycle.0.actualrscore }} | +{{ mesocycle.0.actualtrimp }} | +
| + | ||||
| + edit + / + delete + / + sessions + | +||||
| + {{ microcycle.name }} ({{ microcycle.startdate }} - {{ microcycle.enddate }}) + | +||||
|---|---|---|---|---|
| + | dist (m) | +t (min) | +rScore | +TRIMP | +
| plan | +{{ microcycle.plandistance }} | +{{ microcycle.plantime }} | +{{ microcycle.planrscore }} | +{{ microcycle.plantrimp }} | +
| actual | +{{ microcycle.actualdistance }} | +{{ microcycle.actualtime }} | +{{ microcycle.actualrscore }} | +{{ microcycle.actualtrimp }} | +
| + | ||||
| + edit + / + delete + / + sessions + | +||||
Click on the plan cycles to edit their names, start and end dates. + The gray "filler" + cycles are generated, adjusted and deleted automatically to + ensure the entire plan + duration is covered with non-overlapping cycles. + Once you edit a filler cycle, it become a user-defined + cycle, which cannot be deleted + by the system.
+Filler cycles which have a filler cycle as a parent cannot be edited + or deleted. You have to edit the parent cycle first. The reason is + that children of filler cycles are not safe. They are deleted when + their parent is deleted by the system.
+Click on "Sessions" in the cycle of your interest to see details + of the individual training sessions planned for this period.
+A good way to organize the plan is to think of micro + cycles as training weeks. Macro cycles + are typically used to address specific phases of preparation + and to indicate the racing + season and may span several months. + Meso cycles can be used to group sequences of three to five + light, medium and + hard weeks. It is recommended to work from left to right, + starting with the macro cycles.
+