pyatcron-devel-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Pyatcron-devel-list] Cron and the "*/45" entry


From: Julien Olivier
Subject: Re: [Pyatcron-devel-list] Cron and the "*/45" entry
Date: Thu, 20 Nov 2003 17:53:21 +0000

>  1) Run the task once at a given date and time
>  2) Run the task every seconds
>  3) Run the task every minutes
>  4) Run the task every hours
>  5) Run the task every days of a month at a given time
>  6) Run the task every weeks at a given week day, and at a given time
>  7) Run the task every months at a given day, and at a given time
>  8) Run the task every months at a given week, a given week day, and a
> given times (for example, the last friday of each month at 5 PM).
>  9) Run the task every years, at a given date and time (for example,
> each XMas at midnight).
> 10) Run the task every years, at a given month, a given week, a given
> week day and a given time (for example, the first monday of each year at
> 8 AM).
> 
> 2) and 3) could even be removed, as I don't why you would need them...
> 
> If anyone sees another use-case, let me know ?
> 
> My proposition of a GUI would be:
> 
>  - first, you choose between those 10 options (2 and 3 could be removed
> and some might grouped together, like 7 with 8 or 9 with 10, resulting
> in 6 options).
>  - then, you configure it, by selecting the day, week day, time etc...
> depending on the option chosen.
> 
> What do you think of that ?

Just another thought:

You should be able to add as many schedules as you want to a task. That
means that you could be able to say that you want your task to run at
XMas and on your birthday. Of course that would only work for
AtEntries... Do you think it's a good idea ? If it is, I will try to
comme up with a new class diagram to handle that. But if you don't want
me to modify the class diagram, a possibility would be to merge all the
schedules into one (simply by merging the int arrays) once you have
finished creating the task. The drawback would be that we couldn't
"un-merge" the schedules for easy modification by the user.

If we decide _not_ to authorize defining more than one schedule per
task, users may still be able to do it by creating the same task several
times, with a different schedule each time. But that's not so nice IMO.


-- 
Julien Olivier <address@hidden>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]