emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eddward DeVilla" <eddward@gmail.com>
To: Christian Egli <christian.egli@novell.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: depending TODOs, scheduling following TODOs automatically
Date: Tue, 9 Oct 2007 10:21:03 -0500	[thread overview]
Message-ID: <b71b18520710090821l52cb5e74n1f1ff740602189ca@mail.gmail.com> (raw)
In-Reply-To: <loom.20071009T072147-925@post.gmane.org>

On 10/9/07, Christian Egli <christian.egli@novell.com> wrote:
> One of org-mode biggest strengths is its simplicity. I do not want it to turn
> into a feature ridden dinosaur that is impossible to maintain.

I was hoping for something more like perl, where the easy things are
easy and the hard things are possible.  My hope for any feature in org
is that if you don't need it, it doesn't affect you and you don't need
to know it exists.

> I keep my projects simple. I plan not for the sake of planning but to get an
> overview. So for dependency tracking I usually just reorder my tasks. I don't
> want to fidget with my plan all day. I want to get things done :-)

Same here.  I'm just now in a position where I need to make sure I get
them done on time and it's starting to require some creative planning.
 A planning mistake now could really hose me 9 months from now.
Tracking complex dependency relations between tasks would go a long
way in help me see avoid such mistakes.  Obviously, not everyone is in
that boat.  I wasn't a few months ago.

> To that end my plea is to keep org mode simple. That's why John's proposal
> appeals to me. It is flexible and delegates the complexity to emacs lisp instead
> of inventing another micro language for dependency tracking.

I'm losing track of who proposed what.  I was up late last night.  I'm
liking the TRIGGER/BLOCKER idea that Bastien has been talking about,
except it lacks the ability to reference any task that isn't
immediately before, after, under or above the triggering or blocked
task.  I'm starting to think links might be to best tool in org for
identifying a task (todo item).  I'm not sold on that yet.  I may need
to give that another night.

If we go that route, I think I'd like to see a common library of code
come with org to keep us from reinvent wheels and so we can have a
subset of 'trusted' code.  (I'm security minded.  I'd hate to reinvent
the mistake of embedded VB script in documents.)

Edd

  parent reply	other threads:[~2007-10-09 15:21 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08  6:56 depending TODOs, scheduling following TODOs automatically Rainer Stengele
2007-10-08 13:26 ` Denis Bueno
2007-10-08 13:43   ` Russell Adams
2007-10-08 13:52     ` Russell Adams
2007-10-08 19:48       ` Carsten Dominik
2007-10-08 20:12         ` Russell Adams
2007-10-09 10:13           ` Carsten Dominik
2007-10-08 14:49     ` Eddward DeVilla
2007-10-08 20:55       ` Bastien
2007-10-08 20:26         ` Adam Spiers
2007-10-09  2:15           ` Bastien
2007-10-09  3:03             ` John Wiegley
2007-10-09  3:47               ` Eddward DeVilla
2007-10-09  9:27                 ` Richard G Riley
2007-10-09 14:39                   ` Eddward DeVilla
2007-10-10 17:20                     ` Bastien
2007-10-09 10:35                 ` Bastien
2007-10-09 10:32               ` Bastien
2007-10-11 14:46             ` Carsten Dominik
2007-10-11 15:53               ` pete phillips
2007-10-11 16:22                 ` Sebastjan Trepca
2007-10-11 16:37                 ` Russell Adams
2007-10-11 17:10                   ` pete phillips
2007-10-11 17:55                     ` Russell Adams
2007-10-11 18:45                       ` pete phillips
2007-10-14  1:01                         ` Charles Cave
2007-10-14  2:42                           ` Bastien
2007-10-11 19:46                       ` Bastien
2007-10-11 21:12                       ` Rainer Stengele
2007-10-11 21:19                         ` Leo
2007-10-11 23:54                           ` Piotr Zielinski
2007-10-12  3:14                             ` Eddward DeVilla
2007-10-12 13:50                               ` Bastien
2007-10-12 17:09                         ` Jason F. McBrayer
2007-10-12 17:03                 ` Jason F. McBrayer
2007-10-11 16:53               ` Bastien
2007-10-12  9:21               ` John Wiegley
2007-10-08 20:35         ` Eddward DeVilla
2007-10-09  2:42           ` Bastien
2007-10-09  2:01             ` Russell Adams
2007-10-09  3:35               ` Eddward DeVilla
2007-10-09  3:59                 ` Russell Adams
2007-10-09  4:55                   ` Eddward DeVilla
2007-10-09 10:42                   ` Bastien
2007-10-09  3:37               ` Bastien
2007-10-09  2:58             ` Eddward DeVilla
2007-10-09 10:41               ` Bastien
2007-10-09 14:53                 ` Eddward DeVilla
2007-10-11 12:44                   ` Bastien
2007-10-11 12:22                     ` Russell Adams
2007-10-11 14:03                       ` Bastien
2007-10-11 13:21                         ` Russell Adams
2007-10-11 13:31                         ` Eddward DeVilla
2007-10-12  9:13                         ` John Wiegley
2007-10-09  9:44       ` Christian Egli
2007-10-09 10:53         ` Bastien
2007-10-09 15:21         ` Eddward DeVilla [this message]
2007-10-11 12:44           ` Bastien

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 \
    --in-reply-to=b71b18520710090821l52cb5e74n1f1ff740602189ca@mail.gmail.com \
    --to=eddward@gmail.com \
    --cc=christian.egli@novell.com \
    --cc=emacs-orgmode@gnu.org \
    /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
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

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