RE: [Pyatcron-devel-list] Complete rewrite of the mainwin module

[NICOLOVICI Xavier]

Julien,

I do not have idea of how the time and date schedule widget should be 
organized. I'm used to work with Webmin to manage my Crontab (until PyAtCron is 
ready of course ;-) and I've found their interface quite easy to use.

Now, one word about the [X] recurrence checkbox. In my mind, I think that 
depending on this checkbox, the widgets presented to the user should change. 
Think about a panel with the recurrence checkbox on the top, and below, widgets 
for non-recurrent Task or recurrent one.

For non-recurrent one, I see simple drop-down single value select box (one for 
each schedule values), and for recurrent one, multi-select list of values for 
each field.

About the "run every Wednesday" approach, I let you work on it, because it's a 
GUI problem and for sure it is not an easy task ;-) Anyway, this might be 
released in a future version. I think it would be good to release an 0.1 the 
soonest as possible, in order to announce it to the Fedora community.


One word on the RC files, they are usually located in the home directory of the 
user (~/.pyatcronrc), but we could also think of having a file structure in a 
subfolder of the home dir (~/.pyatcron/inactive_task/*). I have no particular 
preference for the moment, instead that an .pyatcronrc file might not be a good 
choice to store data as it is usually used as config file.

Bye, and thanks for the corrected patch, I will apply it in the following hours.

Xavier

-----Original Message-----
From: address@hidden on behalf of Julien Olivier
Sent: Thu 4/29/2004 12:23 PM
To: address@hidden
Subject: RE: [Pyatcron-devel-list] Complete rewrite of the mainwin module
 
On Thu, 2004-04-29 at 10:34, NICOLOVICI Xavier wrote:
> Good, thanks Juliem, I will install your patch against my development tree 
> and commit changes.
> 
> My dev tree has also evolved a lot as I'm coding the saving feature for the 
> Cron system. I've been also forced to make some changes to various classes 
> definitions and implementations. Hope there is not too much conflict with 
> your patch, if not, my responsability to solve conflicts ;-)
> 

OK, thanks for that.

> Ok, there is something that I did not look at, is the Scheduler widgets pane 
> of the Scheduler property. Do you have already think about a design for that 
> Julien?

I've thought of about a bit.

There are 2 options:

 1) Whether we present a table of checkboxes for each minute, hour, day,
month and weekday and let users check the ones they want. This would
also have a "[X] recurrent" checkbox. This is ugly and cluttered, but it
covers all the options.

 2) Or, we use pre-defined templates, like "Every [Monday | Tuesday |
Wednesday | Thursday...]", "Every [ ]th day of the month", "Every day at
[ ]:[ ]", and "On the [  ]/[  ] at [  ]:[  ]  - [Once | Each year]".

 3) Or, we use the templates in 2), and we add another template called
"custom". If you select custom, it lets you choose your schedule using
the checkboxes mentioned in 1) 

I think 3) is the best solution.

What do you think ? Do you like those templates ? Would you like
more/different templates ?

> For information, I've added a new status to Scheduler objects, the recurrence 
> one. Then, if a Scheduler is recurrent, then it will map to the Cron system, 
> and if it's not, then it will map to At. What do u think? If you feel OK with 
> that, the Scheduler widget should reflect this state with something like a 
> checkbox, I think.
> 

See my answer above.

> One remark, if the Scheduler is inactive (no matter if it's recurrent or 
> not), it will be saved into a PyAtCron RC file. That way, we are able to 
> store inactive task without adding comments or stuff like that in Cron system 
> files.
> 

OK, but where will the RC file be saved ? We have to ensure it's never
lost.

-- 
Julien Olivier <address@hidden>


_______________________________________________
Pyatcron-devel-list mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/pyatcron-devel-list




This e-mail contains proprietary information some or all of which may be 
legally privileged. It is intended for the recipient only. If an addressing or 
a transmission error has misdirected this e-mail, please notify the author by 
replying to the e-mail. If you are not the intended recipient you must not use, 
disclose, distribute, copy, print, or rely on this e-mail.
We take reasonable precautions to ensure our e-mails are virus free. However, 
we cannot accept responsibility for any virus transmitted by us and recommend 
that you subject any incoming e-mail to your own virus checking procedures.

<<winmail.dat>>