I agree mostly: I don't expect an official 'branch' would work for many reasons, so the only way I imagined is to just say forget about it, won't be resolved, and someone make their own task manager which may have familiarity but also needs written for the purposes we're talking about. Needs to be capable of being improved by community because nobody has resources to make every feature that is requested. "by the community, for the community" so to speak.
There is one thing I remember we were encouraged to do: work directly with the XML structure that saves our tasks. That might allow some manipulation and ability to do something like print my tree in the form I like. It's still very limiting when I'm not sure the rules for the XML format, and of course you could not edit it without having to reload later from MLO to see changes. On Wednesday, April 3, 2024 at 3:35:43 AM UTC-6 Wolfgang wrote: > I wouldn't go as far as a branch or even asking for them interfacing with > e.g. Python. But, we already have a trigger for task completion and we have > code for operations "clear flag" and "un-star". How much effort can it be > to add actions for operations that are already available through the user > interface? > > imajeff schrieb am Freitag, 22. März 2024 um 21:16:25 UTC+1: > >> I've not heard of them making a decision to change anything which already >> works a certain way. That's why people said MLO 6 was not really different >> than 5. Maybe time for a branch--if a different team could take the essence >> and start with a new approach to be scriptable and get the other needs >> reasonable. >> >> I get part of the reasoning to not change how something specific works, >> but maybe that means it's time to have a branch where some of us actually >> don't want it to be so tedious with features but not quite useful because >> of how hard it is to get the results that I need when life keeps >> progressing. >> >> I still hope someone will chime in saying, "sure we are working on it" >> >> On Tuesday, March 19, 2024 at 3:26:47 AM UTC-6 Wolfgang wrote: >> >> Is there any progress on that? >> >> For instance, I use the "Starred" column to select actions from my (GTD) >> list of active actions to be done today. For recurring tasks, the star/flag >> needs to be reset upon completion. I also sympathize with the idea of a >> scripting language or similar feature, now that we have the "Triggers and >> Actions" function, but nothing useful to do with it. >> >> imajeff schrieb am Montag, 14. März 2022 um 22:58:56 UTC+1: >> >> I've wanted many improvements to recurrence for over 10 years, and what >> would help most is first implement a scripting language that has control of >> manipulating everything. Scripts could be triggered by many events, and >> therefore could help define exactly what kind of recurrence I need in my >> organization. >> Then, when people make useful scripts, they can be shared. >> >> -- 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/73438599-c52b-45c3-aa50-a0742b9ffeb6n%40googlegroups.com.
