emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Ulf Stegemann <ulf-news@zeitform.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Counter cookies and mixed checkbox lists/subtasks
Date: Thu, 16 Apr 2009 13:45:46 +0200	[thread overview]
Message-ID: <BD276E26-850C-4928-BE33-D6D5705B3790@gmail.com> (raw)
In-Reply-To: <zf.upnd4bdj7e8.fsf@zeitform.de>

On Apr 16, 2009, at 11:05 AM, Ulf Stegemann wrote:

> Hi Carsten,
> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>> there is no way currently to force a cookie either way.
>> I think the the right solution is to modify the structure, so
>> that the check boxes are only in entries without children.
>> Seems to me that this is always possible - in your case
>> you could just create a "first child" that gets the checkboxes.
> okay, as said, this is rather a minor annoyance. However, fixing this
> might nevertheless be desirable since the combination of checkboxes  
> and
> todo item is quite powerful.
> Imagine you are compiling a document where you need contributions from
> others. You could make a todo item for this with checkboxes for every
> chapter planned (or for every author you expect input from, or ...).  
> As
> soon as contributions from authors arrive, you create todo items
> preferably below the same initial todo item, indicating that you  
> have to
> integrate input. When compiling the document you finish those todo  
> items
> on the one hand and on the other hand checkboxes will eventually get
> checked as chapters are finished. Although putting the chapter
> checkboxes into its own sub-item is possible, much of the simplicity  
> and
> elegance of the original approach gets lost. What do you think?

Well, I don't really agree.

* TODO compile document
   [ ] get input from Chris
   [ ] get input from Alice
** TODO integrate input from Chris
** TODO integrate input from Alice.

You could easily do:

* TODO compile document
** Get input
    [ ] get input from Chris
    [ ] get input from Alice
** TODO integrate input from Chris
** TODO integrate input from Alice.

This is what I mean with "you can always restructure
to avoid the problem".  I think the second option is at
least as clear, maybe clearer.

I do like the simplicity of the cookies right now, adding
specifiers of what they refere to would make them less
usable in my mind.

- Carsten

  reply	other threads:[~2009-04-16 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  8:40 Counter cookies and mixed checkbox lists/subtasks Ulf Stegemann
2009-04-08 14:47 ` Carsten Dominik
2009-04-16  9:05   ` Ulf Stegemann
2009-04-16 11:45     ` Carsten Dominik [this message]
2009-04-16 13:24       ` Ulf Stegemann
2009-04-17 16:50         ` Carsten Dominik
2009-04-20  8:00           ` Ulf Stegemann
2009-04-22  4:16             ` Carsten Dominik
2009-04-22  8:08               ` Ulf Stegemann

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BD276E26-850C-4928-BE33-D6D5705B3790@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ulf-news@zeitform.de \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).