Dear sirs, finally I decided to make my own scheduler by using Excel via 
Visual Basic Assitant.
I admit that it was a hard work (=several nights!) and I have not finished 
it: I am adding the recurring tasks.

The idea is simple, the implementation not so much.

I made a task table containing two types of tasks:

-fixed tasks (APPOINTMENTS: date+hour and duration)
-floating tasks (only duration + eventually a not-before-than-date and 
eventually a not-after-than-date). These tasks are to be done when no 
appointments are on.

I also made a table of my personal working timeslots (different timeslots 
on each weekday).

Then, when I press the button "PLAN!", my macro generates a plan 
time-ordered table of tasks with start date and time for each task: the 
fixed tasks are simply copied with the original date. On the free pieces of 
the working timeslots (free=not occupied by fixed tasks) the program places 
the floating tasks (eventually in pieces-serie form of them) in order to 
completely fill the working timeslots. The planning order of the floating 
tasks reflects the order of the task table containing the floating tasks, 
so I can give to each floating tasks a priority, agains the other, simply 
moving a task up or down.

When the planned end datetime of a floating task exceeds its 
not-after-than-date, a red signal is added on the plan date. This signal 
suggests me to re-evaluate the priority of the floating tasks, so as to 
avoid the delays.

Now I am adding also the function of recurring floating tasks.

------

I am using this solution for work and home, with two different task lists 
and working tìmeslots. This solution is very effective for me, because I 
can really forecast the dates of each floating task and change the 
priorities by evaluating the previous plan, assuming that I get a good 
extimation of the durations of the floating tasks.

Bye.


Il giorno martedì 4 luglio 2017 00:22:01 UTC+2, Nick Clark ha scritto:
>
> One thing that I think would help with scheduling tasks is for MLO to have 
> an additional date field for Expected/Planned Do Date. This would enable 
> views to be setup that list all that's to be done on dates ahead while 
> still retaining the Due Date as the date past which the task is no longer 
> valid.
> This was discussed some years back but no conclusion was reached. It would 
> need to cater for tasks with no Due Date, and also with recurring tasks, so 
> programming would not be trivial.
> At present I tend to used Due Date for this, which is about unsatisfactory.
>

-- 
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mylifeorganized/c09d6871-590e-4806-b64d-f2448a92259f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to