From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tom Breton (Tehom)" Subject: Re: Advice sought on managing decision alternatives. Date: Fri, 6 Feb 2009 15:07:05 -0500 (EST) Message-ID: <1036.24.63.0.170.1233950825.squirrel@mail.panix.com> References: <20090101170227.C707734803@mail2.panix.com> <1131.66.30.178.137.1230850437.squirrel@mail.panix.com> <1371.66.30.178.137.1232336005.squirrel@mail.panix.com> <1057.24.63.22.246.1233375672.squirrel@mail.panix.com> Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LVWyi-00030R-QZ for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 15:07:08 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LVWyh-00030B-6V for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 15:07:08 -0500 Received: from [199.232.76.173] (port=38328 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LVWyh-000308-02 for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 15:07:07 -0500 Received: from mail2.panix.com ([166.84.1.73]:53785) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LVWyg-0006VI-LO for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 15:07:06 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Cc: emacs-orgmode@gnu.org > Hi Tom, > [...] > WIth you patch, we have right now > > CHOOSE as the prefix > choseness as the interpretation > org-decision as the name of the module. > > My request would be to maybe use `choose' also as the > interpretation symbol, or, alternatively, CHOSENESS > as the prefix. Yes. I think "choose" is best; the ambiguity between "chosenness" and "choseness" just invited difficulties. Always feel free to suggest alternatives to my naming. Sometimes my initial ideas go in a funny direction. Eg, my initial thinking, which I now abandon, was: * org-DECISIONS.el because it supports decisions. * CHOSENNESS because it's the property the item has of being chosen or n= ot. As William observed, it's grammatically correct but rare. * CHOOSE because I saw that CHOSENNESS has problems. So "choose" it is. I'd like to rename the file org-choose.el as well, no= w that I think about the naming. Do you want a patch for it? > For customizing org-todo-keywords, instead of explicitly > offering `choseness', maybe we can use a symbol field > where people can type into. It's more flexible but offers less support to the user. Maybe we can hav= e the best of both worlds by restricting the choice to interpretations that available modules support. Ie, something like this: * Object: a variable that holds the names of the interpretation symbols, or of the ones that aren't built in. * Behavior: interested modules add their interpretation symbol to the li= st * Behavior: When customizing org-todo-keywords, offer the symbols from that list as choices for interpretation symbols. The primary difficulty would be getting widgets to understand that. > That would turn your patch into a generally useful system > of hooks where other ideas could be implemented as well. > > What do you think? Sounds good to me. Tom Breton (Tehom)