scheduling activity
Table of Contents
Though activity are done repeatedly, it is helpful to schedule a session at a specific time.
1. problem of using one giant activity
- giant
logbook - can’t schedule multiple instances
- notes, materials and logs of individual session would look messy.
2. Heuristic: subtree of activity sessions
* go to gym ** sessions *** TODO go to gym #1 *** TODO go to gym #2
- pro
- org-clock-report with specified maxlevel can get clock sum of all sessions; individual TODO is neat; context of each session is seperated
- con
- giant subtree, messy structure
3. Heuristic: activity #n sessions
directly have those TODOs in Tasks.org, instead of organize them in a plan subtree.
Instead, link to the activity in the plan subtree.
- pro
- neat structure(very flat)
- con
- do not have way of seeing a complete view of all sessions, do not have sum clock report.
Backlinks
activity-based plan and stage-based plan
(Activity-based plan)
Activity-based plans works analoguesly in the whole lifecyle of the plan: by performing activities.
Typically, a list of activities would be present, each of them would contribute to the objective, and all of them would be performed repeatedly thorough out until the objective is accomplished.
examples are work out plans and studying routine.
corresponding to unstructured approach