Was not aware of the plugin. Seems kind of complicated. I assume i solved this by smart view constructions to control the dynamics. - i think the basic structure is probably the similar - somehow devide and conquer related to the main buckets one cares about. The interesting peace is how to use various views to control the dynamics and the separation of various concerns like: - what is running ok and not-ok - what to focus on next - how to integrate linking to other repositories And especially the decision supporting views about where to focus on next and how to manage the activities in the various time spans - like day, week, month... - In summary how to control the flow by the right views and filters.... -a
Radek Pilich schrieb am Donnerstag, 25. Mai 2023 um 12:30:18 UTC+2: > The structure you propose is pretty much same as mine. > > I have t-10 top level "life area" folders, than under each there are some > inbox / project / sub-area folders for non-recurring tasks (I have launcher > shortcuts created to send new tasks into them) and below that is a section > of recurring tasks / habits grouped under some parent that somehow makes > sense to me as a conceptual bucket to fit those tasks into. > > > [image: > Screenshot_2023-05-25-12-21-40-03_2766e1764d774df27a406d6982d0ccfa.jpg] > [image: > Screenshot_2023-05-25-12-23-43-84_2766e1764d774df27a406d6982d0ccfa.jpg] > On Tuesday, 23 May 2023 at 18:02:32 UTC+2 Benny Karlson wrote: > >> Hi, >> have used MLO for many years, mainly on my Android (before that Windows >> phone), but always together with the PC-version. I have realized that >> after all development and new features my workflow seems not to work >> efficiently with all these new possibilities. >> Does anyone built a working workflow to handle a lot of tasks in >> different areas and places? Guess is about how to most efficient build your >> tree structure >> and then when to use Context when to use Flags or Texttags!? >> >> Want a quick and easy input (one click) with as many things applied >> automaticly (as context will do if copied in under a treebranch). This >> means the tree folder structure... >> >> A simple question of what you would choose... >> Different Actions... Different places... >> !Call @Computer >> !Buy for @House 1 >> !Fetch @$hopA , $hopB >> !Contact @House2 >> !Repair @Car1 >> >> Example1 Tree folders under each place >> [Folder House1] - [Folder Repair] : Task1/Task2/ Task3 >> [House1] - [Folder Buy] : Task1/Task2/ Task3 >> [House1] - [Folder Call] : Task1/Task2/ Task3 >> or >> >> Example1 Tree folders under each action >> [Folder !Repair] - [Folder @House1] : Task1/Task2/ Task3 >> [!Repair] - [Folder@House2] : Task1/Task2/ Task3 >> [!Repair] - [Folder@Car1] : Task1/Task2/ Task3 >> >> Example 1 feels more naturual when follow up things done at different >> places >> >> Any help would be greatly *appreciated* >> > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/ad0ae362-837f-4474-b37c-8efe3024ed6dn%40googlegroups.com.
