On 6/22/07, Scott Jaderholm <[EMAIL PROTECTED]> wrote:
I think it's harder to design an interface where different levels have
different columns.
Sometimes the columns will make sense on different levels so they opt
to leave them there. Also, as we see in the screenshot, they can be
used for summ
On 6/22/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
What I find a bit strange though is that it is using a hierarchy,
and every level of the hierarchy has the same columns. Columns
seem to make more sense for items with equal level, at least to me.
I think it's harder to design an interfac
On Jun 19, 2007, at 19:45, Scott Jaderholm wrote:
Carsten,
Have spreadsheet like columns for lists been discussed before, and if
so, what was the verdict?
I have seen them mentioned before but never understood
what was meant, so nothing from my side happened. Thanks
for sending the illustrat
On 6/19/07, Scott Jaderholm <[EMAIL PROTECTED]> wrote:
I see a property list under each heading as a way of doing columns,
albeit in a less user friendly way. I can see this being useful
anywhere you have hierarchal data to which you would like to add
structure. Currently, I normally transfer it
On 6/19/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
So the discussion must be about how you would like Org-mode to make
use of such data. Obviously it would be easy to write (as you
suggest) a little function that returns all this data as, say,
a property list. But then you would still need
> takes 8 hours, the second subtask should then be scheduled on the 16th?
>
> - Carsten
I hadn't considered using "workhours" logic, simply a relative time
forward from the schedule parent.
--
Russell Adams
On 6/19/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
On Jun 13, 2007, at 17:33, Eddward DeVilla wrote:
>I'm starting to wonder if it would be useful to have a general
> format for properties (or choose some other word) to be associated
> with a heading or todo item. It seems the heading
On Jun 19, 2007, at 13:21, Russell Adams wrote:
It could be nice later to schedule A, and then have each
of a1-3 show up on the agenda based on their duration.
I am not sure if I understand what you mean here.
- Carsten
I mean that the parent would be scheduled at a fixed date/time, and
th
> So the discussion must be about how you would like Org-mode to make
> use of such data. Obviously it would be easy to write (as you
> suggest) a little function that returns all this data as, say,
> a property list. But then you would still need to use it in
> some way. Are you suggesting tis
> >It could be nice later to schedule A, and then have each
> >of a1-3 show up on the agenda based on their duration.
>
> I am not sure if I understand what you mean here.
>
> - Carsten
I mean that the parent would be scheduled at a fixed date/time, and
then child entries would be in the agenda
On Jun 13, 2007, at 15:47, Russell Adams wrote:
If this feature already exists, I've missed it...
I'm planning ahead on some items, and having a way to represent the
amount of time a TODO item will take, and then having the parent total
the duration of the children would be very helpful.
* TO
On Jun 13, 2007, at 17:33, Eddward DeVilla wrote:
I'm starting to wonder if it would be useful to have a general
format for properties (or choose some other word) to be associated
with a heading or todo item. It seems the heading is getting a little
crowded.
Would it be reasonable to sa
I'm looking specificaly at project planning...
I like the idea of the key/value pairs under a heading, perhaps later
it could be used for other datatypes (TID,DEPENDS,ASSIGNED, etc).
I frequently use a tree of TODO's to describe steps in a project plan,
and check them off as they are completed.
On Jun 13, 2007, at 23:58, Scott Jaderholm wrote:
On 6/13/07, Russell Adams <[EMAIL PROTECTED]> wrote:
I'm planning ahead on some items, and having a way to represent the
amount of time a TODO item will take
On a similar note, I like using the clocktable to see how long things
have taken me
Just forwarding to the list. I forgot to.
-- Forwarded message --
From: Eddward DeVilla <[EMAIL PROTECTED]>
Date: Jun 13, 2007 8:37 PM
Subject: Re: [Orgmode] Duration Tally
To: Scott Jaderholm <[EMAIL PROTECTED]>
On 6/13/07, Scott Jaderholm <[EMAIL PROTECTED]&g
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
>We already have SCHEDULED, DEADLINE, & CLOSED that are meaningful
> to org-mode.
And CLOCK, as well.
--
+---+
| Jason F. McBrayer[EMAIL PROTECTED] |
| If someone conqu
I like that alot!
However my goal was one of simple project planning.
Thanks!
On Wed, Jun 13, 2007 at 10:33:48AM -0500, Eddward DeVilla wrote:
>I'm starting to wonder if it would be useful to have a general
> format for properties (or choose some other word) to be associated
> with a heading
On 6/13/07, Russell Adams <[EMAIL PROTECTED]> wrote:
I'm planning ahead on some items, and having a way to represent the
amount of time a TODO item will take
On a similar note, I like using the clocktable to see how long things
have taken me, but sometimes I just want to put a time value under
I'm starting to wonder if it would be useful to have a general
format for properties (or choose some other word) to be associated
with a heading or todo item. It seems the heading is getting a little
crowded.
Would it be reasonable to say that a list of non-whitespace
listing following the
If this feature already exists, I've missed it...
I'm planning ahead on some items, and having a way to represent the
amount of time a TODO item will take, and then having the parent total
the duration of the children would be very helpful.
* TODO A {6h}
** TODO a1 {2h}
** TODO a2 {2h}
** TODO a3
20 matches
Mail list logo
