FR: multiple scheduling of one item?

FR: multiple scheduling of one item?

[Adam Spiers]

Imagine I have a single project or task which I know will require
several sessions to complete.  Before I get to the stage of analysing
it closely and breaking it down into sub-tasks, it would be good to
reserve some diary time in advance, so that I don't accidentally
accept other commitments for that time and overstretch myself.

However, this is different from booking a normal diary appointment, in
the sense that I am not making a commitment to other people to be in a
particular place at a particular time: the commitment is only to
myself and is directly associated with a particular project or task.

Therefore it sounds like it would be useful to be able to schedule the
same task for multiple slots.  It turns out that the org-agenda code
already handles this beautifully; if you do:

* Long task/project not yet broken down into sub-tasks
  SCHEDULED: <2008-01-07 Mon>
  SCHEDULED: <2008-01-08 Tue>

and it appears in both places in an agenda view, and you can jump back
to the item in the normal way.  The only downside is that C-c C-s
doesn't currently support entering it:

  (org-schedule &optional REMOVE)

  Insert the SCHEDULED: string with a timestamp to schedule a TODO item.
  With argument REMOVE, remove any scheduling date from the item.

How about doing the usual trick of comparing different prefix argument
values (e.g. 4 vs. 16) to allow adding a new scheduled slot?

Re: FR: multiple scheduling of one item?

[Carsten Dominik]

On Dec 31, 2007, at 4:21 PM, Adam Spiers wrote:

> Imagine I have a single project or task which I know will require
> several sessions to complete.  Before I get to the stage of analysing
> it closely and breaking it down into sub-tasks, it would be good to
> reserve some diary time in advance, so that I don't accidentally
> accept other commitments for that time and overstretch myself.
>
> However, this is different from booking a normal diary appointment, in
> the sense that I am not making a commitment to other people to be in a
> particular place at a particular time: the commitment is only to
> myself and is directly associated with a particular project or task.
>
> Therefore it sounds like it would be useful to be able to schedule the
> same task for multiple slots.  It turns out that the org-agenda code
> already handles this beautifully; if you do:
>
> * Long task/project not yet broken down into sub-tasks
>  SCHEDULED: <2008-01-07 Mon>
>  SCHEDULED: <2008-01-08 Tue>
>
> and it appears in both places in an agenda view, and you can jump back
> to the item in the normal way.  The only downside is that C-c C-s
> doesn't currently support entering it:
>
>  (org-schedule &optional REMOVE)
>
>  Insert the SCHEDULED: string with a timestamp to schedule a TODO  
> item.
>  With argument REMOVE, remove any scheduling date from the item.
>
> How about doing the usual trick of comparing different prefix argument
> values (e.g. 4 vs. 16) to allow adding a new scheduled slot?


This could be done of course - but I am not sure how common your use  
case is.
And I quess it is nearly as easy to got to the entry and type  
`SCHDEULED: C-c .'
for the few cases where you need it?

If I nt forward to implement this, should the extra SCHEDULED stamp
be in the same second line of the entry, or in an extra line?  Any
other votes on this issue?

- Carsten

Re: FR: multiple scheduling of one item?

[Adam Spiers]

On Thu, Jan 03, 2008 at 08:44:08AM +0100, Carsten Dominik wrote:
> On Dec 31, 2007, at 4:21 PM, Adam Spiers wrote:
> >Therefore it sounds like it would be useful to be able to schedule the
> >same task for multiple slots.  It turns out that the org-agenda code
> >already handles this beautifully; if you do:

[snipped]

> This could be done of course - but I am not sure how common your use  
> case is.

Admittedly not very common, and this is probably the lowest priority
of any of the requests I have made recently.

> And I quess it is nearly as easy to got to the entry and type  
> `SCHDEULED: C-c .'
> for the few cases where you need it?

Nearly - although presumably an implementation would also have the
effect of allowing setting it from an agenda buffer?

> If I nt forward to implement this, should the extra SCHEDULED stamp
> be in the same second line of the entry, or in an extra line?  Any
> other votes on this issue?

I don't really mind - whatever would work best for scaling out to 3 or
more SCHEDULED stamps.

Re: Re: FR: multiple scheduling of one item?

[Giovanni Ridolfi]

On Thu, Jan 03, 2008 at 08:44:08AM +0100, Carsten Dominik wrote:
>
> On Dec 31, 2007, at 4:21 PM, Adam Spiers wrote:
>
>> * Long task/project not yet broken down into sub-tasks
>>  SCHEDULED: <2008-01-07 Mon>
>>  SCHEDULED: <2008-01-08 Tue>
>>
>> and it appears in both places in an agenda view, and you can jump back
>> to the item in the normal way.  The only downside is that C-c C-s
>> doesn't currently support entering it:
>>
>>  (org-schedule &optional REMOVE)
>>
>
> If I nt forward to implement this, should the extra SCHEDULED stamp
> be in the same second line of the entry, or in an extra line?  Any
> other votes on this issue?

I think it can be done in this way:

* Long task
  SCHEDULED: <2008-01-03 gio>--<2008-01-04 ven>

Well, I've just written it (by hand ;-) and 
I've scheduled "long task" in both days (today and tomorrow) in the Agenda.

cheers,

Giovanni

Re: FR: multiple scheduling of one item?

[Adam Spiers]

On Thu, Jan 03, 2008 at 11:39:21PM +0100, Giovanni Ridolfi wrote:
> On Thu, Jan 03, 2008 at 08:44:08AM +0100, Carsten Dominik wrote:
> > On Dec 31, 2007, at 4:21 PM, Adam Spiers wrote:
> >> * Long task/project not yet broken down into sub-tasks
> >>  SCHEDULED: <2008-01-07 Mon>
> >>  SCHEDULED: <2008-01-08 Tue>
> >>
> >> and it appears in both places in an agenda view, and you can jump back
> >> to the item in the normal way.  The only downside is that C-c C-s
> >> doesn't currently support entering it:
> >>
> >>  (org-schedule &optional REMOVE)
> >
> > If I nt forward to implement this, should the extra SCHEDULED stamp
> > be in the same second line of the entry, or in an extra line?  Any
> > other votes on this issue?
> 
> I think it can be done in this way:
> 
> * Long task
>   SCHEDULED: <2008-01-03 gio>--<2008-01-04 ven>
> 
> Well, I've just written it (by hand ;-) and 
> I've scheduled "long task" in both days (today and tomorrow) in the Agenda.

That's a nice idea, but it won't cover all eventualities,
e.g. sometimes one would need:

  * Long task
    SCHEDULED: <2008-01-07 Mon 10:00-13:00>
    SCHEDULED: <2008-01-08 Tue 14:00-17:00>

Re: FR: multiple scheduling of one item?

[Bastien]

Adam Spiers <orgmode@adamspiers.org> writes:

> That's a nice idea, but it won't cover all eventualities,
> e.g. sometimes one would need:
>
>   * Long task
>     SCHEDULED: <2008-01-07 Mon 10:00-13:00>
>     SCHEDULED: <2008-01-08 Tue 14:00-17:00>

FWIW, I think it would be better to have something like this:

,----
| * Something important
|   SCHEDULED: <2008-01-06 dim 9:00-13:00>
| 
|   :PROPERTIES:
|   :SCHEDULED: <2008-01-07 lun 9:00-13:00>, <2008-01-08 mar 9:00-13:00>
|   :END:
`----

Org would first check the "SCHEDULED:" cookie, then check for further
re-schedulding (the property might also be called "RESCHEDULDED".)

BTW, there is a small bug when trying to enter the SCHEDULED property by
hand: the sequence `C-c C-x p SCHEDULED RET' will ask for a value, then
discard it and ask again for a date (thru org-read-date).  I guess it
should ask for the date only.

-- 
Bastien

Re: FR: multiple scheduling of one item?

[Adam Spiers]

On Mon, Jan 07, 2008 at 02:52:51AM +0000, Bastien wrote:
> Adam Spiers <orgmode@adamspiers.org> writes:
> 
> > That's a nice idea, but it won't cover all eventualities,
> > e.g. sometimes one would need:
> >
> >   * Long task
> >     SCHEDULED: <2008-01-07 Mon 10:00-13:00>
> >     SCHEDULED: <2008-01-08 Tue 14:00-17:00>
> 
> FWIW, I think it would be better to have something like this:
> 
> ,----
> | * Something important
> |   SCHEDULED: <2008-01-06 dim 9:00-13:00>
> | 
> |   :PROPERTIES:
> |   :SCHEDULED: <2008-01-07 lun 9:00-13:00>, <2008-01-08 mar 9:00-13:00>
> |   :END:
> `----
> 
> Org would first check the "SCHEDULED:" cookie, then check for further
> re-schedulding (the property might also be called "RESCHEDULDED".)

Whilst tracking re-scheduling might be useful, it wasn't my intention.
I wanted to be able to create a schedule in advance which spans
multiple sessions.

Re: FR: multiple scheduling of one item?

[Bastien]

Adam Spiers <orgmode@adamspiers.org> writes:

>> Org would first check the "SCHEDULED:" cookie, then check for further
>> re-schedulding (the property might also be called "RESCHEDULDED".)
>
> Whilst tracking re-scheduling might be useful, it wasn't my intention.
> I wanted to be able to create a schedule in advance which spans
> multiple sessions.

Now that I've read Sacha's article thoroughly, I better understand why
you would need such a feature.  I still think it's better not to clutter
an entry with too many SCHEDULED: cookies floating around... I'd prefer
to be able to hide them in a drawer.

-- 
Bastien => /away