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

[NICOLOVICI Xavier]

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, 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?
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.

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.

Bye, and happy coding.

Xavier




-----Original Message-----
From: address@hidden on behalf of Julien Olivier
Sent: Thu 4/29/2004 11:09 AM
To: address@hidden
Subject: RE: [Pyatcron-devel-list] Complete rewrite of the mainwin module
 
On Thu, 2004-04-29 at 08:37, NICOLOVICI Xavier wrote:
> Hi Julien,
> 

Hi Xavier.

> A few answer to your comments.
> 
> When I mean adapt, it means "make it work". Apply the patch I've sent and run 
> the app, you'll see that CreateTask and EditTask fails as they use the old 
> ScheduleList class. There is nothing more to do.
> 

Yes, I've seen that after testing the patch. I have attached a fixed
version of the patch. It should fix all those problems.

> I've proposed to limit task to the CmdLineTask one for the 0.1 release, sorry 
> if this was unclear. I agree that others should be autodetected, but for the 
> first 0.1, let keep things simple.
> 

OK, that's fine for me.

> Description of the Task should be definitely forgotten for the moment. As 
> I've already said, the crontab file must remain standard, we must not rely on 
> any comments in it for our GUI, at least for the moment. This is something 
> that we might discuss in the future. Remember, my first objective is to 
> quickly get a GUI to edit Cron and At tasks without messing up the crontab 
> files with address@hidden specific entries.
> 

OK, it's one the TODO list for the future then.

> Saving the SchedulerListStore means also "activating" changes to the system, 
> if not then it's useless ;-)
> 
> Julien, I let you hack on the GUI then, I will work on the saving and 
> activating system.
> 

Please try the attached patch. Most of the problems should already be
fixed in it.

> Thanks to all for your help,
> 

You're welcome :)

-- 
Julien Olivier <address@hidden>




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>>