From: "Tom Breton (Tehom)" <email@example.com> To: Carsten Dominik <firstname.lastname@example.org> Cc: email@example.com Subject: Advice sought on managing decision alternatives. Date: Sun, 18 Jan 2009 22:33:25 -0500 (EST) [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <DDD4C54F-B799-422F-AD83-45F142B28EFC@uva.nl> On my last two requests, Carsten had better ideas and my proposal really benefitted from them. So I'm asking for advice on the design. ****** Rationale When I make a decision, in org-mode, I write down the set of reasonable alternatives that I see, each one as an item. Then I make notes about each one and then choose. Often the process is messy. I sometimes: * add a new alternative later * realize an alternative is fatally flawed and permanently reject it. * choose one but come to regret it. Then I need to unchoose it and then choose another. * Realize that what I thought was an alternative is really a distinct yes/no choice. * Add a related yes/no choice to the group - I could make a new subtree for each new related choice, but usually once I find one related choice, I soon find many, so that's a lot of restructuring for little benefit. ****** The overall idea: So I want a way of keeping track of alternatives and their state of decision. Where possible, I'd like this to automatically stay in a sensible state. Eg, if one alternative is chosen, no other is. ****** A detailed example ******* Item markings For example, each item could be marked from this set of markings: * CHOSEN * Invariant :: The other items are marked NOT CHOSEN or lower * Reaction :: If another item becomes CHOSEN, this item becomes NOT CHOSEN * Reaction :: If another item becomes LEANING TOWARDS, this item becomes MAYBE. * LEANING TOWARDS * Invariant :: The other items are marked MAYBE or lower. * Reaction :: If another item becomes LEANING TOWARDS, this item becomes MAYBE. * MAYBE * The default marking. New items in the group get this marking unless some item is marked CHOSEN, in which case new items get NOT CHOSEN. * Reaction :: If another item becomes CHOSEN, MAYBE becomes NOT CHOSEN. * NOT CHOSEN * Reaction :: If it becomes the case that no item is CHOSEN, NOT CHOSEN items become MAYBE. * If marks are to be changed by moving up and down this "scale", an item could become "NOT CHOSEN" in the course of becoming "REJECTED". This requirement keeps me from adding an invariant that if any item is NOT CHOSEN, exactly one item should be CHOSEN. * REJECTED * Remains marked REJECTED regardless what happens to other items. Notice the symmetry in the constraints: | If any | | then the other | | | item is: | | items can't be | | | | | higher than: | | |----------+---+----------------+---| | CHOSEN | 1 | NOT CHOSEN | 4 | | FAVORED | 2 | MAYBE | 3 | |----------+---+----------------+---| So there are 2 ranges of marks relating to each other in mirror image fashion. If some item is marked in the "CHOSEN" range, other items can't be marked higher than the mirror-corresponding entry in the "NOT CHOSEN" range. I believe that will keep the items collectively in a sensible state. ******* Item grouping A group of items represent alternatives in a decision just if: * they are siblings * they all have a mark from that set. There's plenty of room to expand to other means of grouping items. ****** The plan My tentative plan is this: * Use the TODO position to carry chosenness information * Is that a bad idea? Is there ever a case when an item should be both an alternative in a choice and a normal TODO item? * Re-use the usual TODO manipulation commands to manipulate these marks. * Add a new class of TODO-like mark interpretation * This interpretation is "chosenness" instead of "type" or "sequence". * The spec for it can indicate * The mark that is given to new items by default * The upper range (as above) * The lower range (as above) * Indications * "0" indicates the default mark * "-" indicates the lowest automatically managed mark. * If a low auto mark is not present, no automatic handling is wanted. * "+" indicates the counterpart of the low auto mark, to help indicate the upper range. * Defaults to the last item. * How these marks indicate ranges * the lower range is from the low auto mark to the default mark, inclusive * the upper range is from the mark above the default mark to the high auto mark, inclusive. * EXCEPT that the ranges must be the same length, so truncate the longer one. Truncate it at the default end of it. * If there's no low auto mark, there are no ranges and no automatic handling. * Examples: * (chosenness "REJECTED" "-" "NOT_CHOSEN" "0" "MAYBE" "LEANING_TOWARDS" "+" "CHOSEN") * (chosenness "NO" "0" "MAYBE" "YES") * Set up the regular expressions etc to accept these marks in TODO position. Same thing org-set-regexps-and-options does now, except: * Accept chosenness too. * Don't place chosenness marks in org-done-keywords and org-not-done-keywords * Place chosenness ranges in appropriate buffer-local variables. * In order to keep the marks consistent (as described above), use org-trigger-hook. When some item becomes marked with a mark in the upper range, demote the other items to the mark that occupies the mirror position in the lower range. * Eg, using the first example of marks, when an item is made CHOSEN, demote its siblings to NOT_CHOSEN. * Eg, using the first example of marks, when an item is made LEANING_TOWARDS, demote its siblings to MAYBE. * In order to find the correct default for such an item, add another hook. * It is called just if a default mark is wanted * It (each function on it) returns `nil' or a string. * For chosenness, it acts when * the old mark is `nil' or is from another TODO keyword set * A chosenness keyword set is to be used. ****** Impact on code * Most of this would go in a contrib module to hold the changes. * Name it "org-decisions.el" * This would define and manage the range variables described above. * When it loaded, it would add appropriately to the new variables below. * In org.el * Affecting customizations: * The org-todo-keywords customize would add an interpretation "chosenness" as alternative to "type" and "sequence". * Affecting org-todo * I'd add a hook. * Name it org-todo-get-default-hook * That hook would be called to find a default item. * Affecting org-set-regexps-and-options: * I'd add an alist that associates type to a handler that sets up the various todo variables. * Name it org-set-todo-handlers-alist. * org-set-regexps-and-options would use that list to find a handler where now it processes "type" and "sequence". * The "type" and "sequence" handlers would be the same code that is used now in `org-set-regexps-and-options', excerpted. * Alternatively, I could leave "type" and "sequence" handling where it is as special cases.
next prev parent reply other threads:[~2009-01-19 3:33 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20090101170227.C707734803@mail2.panix.com> 2009-01-01 22:53 ` Feature request and patch - blocked TODO to say BLOCKED Tom Breton (Tehom) 2009-01-09 8:16 ` Carsten Dominik 2009-01-15 2:34 ` Tom Breton (Tehom) 2009-01-17 8:01 ` Carsten Dominik 2009-01-19 3:33 ` Tom Breton (Tehom) [this message] 2009-01-22 11:15 ` Advice sought on managing decision alternatives Carsten Dominik 2009-01-31 4:21 ` Tom Breton (Tehom) 2009-01-31 5:41 ` Carsten Dominik 2009-01-31 18:36 ` Tom Breton (Tehom) 2009-02-01 15:54 ` James TD Smith 2009-02-06 13:08 ` Carsten Dominik 2009-02-06 16:16 ` William Henney 2009-02-06 20:07 ` Tom Breton (Tehom) 2009-02-07 0:18 ` Carsten Dominik 2009-02-07 20:46 ` Tom Breton (Tehom) 2009-02-08 13:06 ` Carsten Dominik 2009-02-08 20:25 ` Tom Breton (Tehom) 2009-02-09 6:42 ` Carsten Dominik 2009-02-10 3:14 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Tom Breton (Tehom) 2009-02-10 7:55 ` Carsten Dominik 2009-02-24 0:51 ` org-choose bugfix Tom Breton (Tehom) 2009-02-24 3:05 ` Manish 2009-04-07 0:13 ` Tom Breton (Tehom) 2009-04-08 13:13 ` Carsten Dominik 2009-02-24 5:51 ` Carsten Dominik 2009-02-10 8:46 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Manish 2009-02-10 9:12 ` Carsten Dominik 2009-02-10 10:26 ` Manish 2009-02-10 22:48 ` Tom Breton (Tehom) 2009-02-12 12:50 ` Manish 2009-02-12 20:13 ` Tom Breton (Tehom) 2009-02-13 4:23 ` Manish 2009-02-12 20:55 ` Patch " Tom Breton (Tehom) 2009-02-13 4:38 ` Manish 2009-02-11 1:08 ` Tom Breton (Tehom) 2009-02-11 10:34 ` Carsten Dominik 2009-02-11 21:41 ` Tom Breton (Tehom) 2009-02-11 23:38 ` Nick Dokos 2009-02-12 4:17 ` Tom Breton (Tehom) 2009-02-11 23:44 ` Carsten Dominik 2009-02-12 4:27 ` Tom Breton (Tehom) 2009-02-12 15:49 ` Nick Dokos 2009-02-12 20:32 ` Tom Breton (Tehom) 2009-02-12 21:25 ` Nick Dokos 2009-02-11 12:29 ` Carsten Dominik 2009-02-11 14:58 ` Docs submitted Bernt Hansen 2009-02-11 17:33 ` Samuel Wales 2009-02-11 15:38 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Daniel Clemente 2009-02-11 15:41 ` Carsten Dominik 2009-02-11 20:02 ` Tom Breton (Tehom) 2009-02-11 23:45 ` Carsten Dominik 2009-02-11 1:45 ` Slight fix to update-org.sh Tom Breton (Tehom) 2009-02-10 23:19 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Tom Breton (Tehom) 2009-02-11 10:34 ` Carsten Dominik 2009-02-10 22:45 ` Tom Breton (Tehom) [not found] <20090122112819.B30E12940C@mail1.panix.com> 2009-01-22 22:11 ` Advice sought on managing decision alternatives Tom Breton (Tehom)
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Advice sought on managing decision alternatives.' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).