PMC macro

[Jean-Claude Besse]

• Show table with day by day -> done, display to improve
• edit possibility in said table
• Blocks base, build, specific, race intensity, etc -> done
• Slowly grow from current CTL to desired CTL -> done
• Adapt training camp vs downtime vs B race
• Save
• Show injury risk?
• import avg CTL by day of the week to keep the user habits of workouts? (may not change the big picture, but might be nice to have as will facilitate comparison)

[Daniel Besse]

By save, do you mean to own calendar (weekly_summary) or to share? Or better, both. One default plan that goes to calendar and others can be saved privately or shared

[Jean-Claude Besse]

I planned to save somewhere else than in weekly summary (so can also save more than one etc) and have an option in pmc to load a given plan as comparison with done training, but it's debatable. Of course sharing should be allowed

[Jean-Claude Besse]

commit a2eea8e introduces blocks, CTL ramp and crude summary