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

[NICOLOVICI Xavier]

Hi Julien,

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.

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.

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.

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.

Thanks to all for your help,

Xavier


-----Original Message-----
From: address@hidden on behalf of Julien Olivier
Sent: Thu 4/29/2004 9:14 AM
To: address@hidden
Subject: Re: [Pyatcron-devel-list] Complete rewrite of the mainwin module
 
On Wed, 2004-04-28 at 17:28, NICOLOVICI Xavier wrote:
> Hi everyone,
> 

Hi

> I've mostly completly rewritten the mainwin.py module to use our new 
> ScheduleListStore object.
> Quickly, major changes are:
> 
> - ScheduleList class and lib.schedulelist module not needed anymore, should 
> be removed from CVS
> - lib.mainwin module code is now lighter, no more sync stuff between 
> ScehduleList and TreeView
> 

Sounds great !

> What's next on GUI:
> - Adapt create task and edit task properties code

What do you mean by "adapt" ? The task property code is already pulled
from the task type class (both in properties and in the assistant). All
we really need is to create a common scheduler widget (to set the time
of the task), and to create more task type classes. Or am I
misunderstanding you ?

> - Limit the create task action to creating command line Task
> 

Or, better, find a way to auto-detect available task type classes...

And I'd add that we need to add a way to set a description for the tasks
(in the properties and in the assistant). This description should then
be put back in the crontab file using comments.

> What's next on core system:
> - Code the saving method of the ScheduleListStore and link it to the 
> mainmenu_save event
> 

Obviously. And perform the "crontab" command on the modified file to
"activate" it.

> When this will be done, I think that we might be ready to release a 0.1 
> release. What do u think guys?
> 

I agree.

> Please let me know on what you would like to work before I start doing 
> something.
> 

Like always, I'd like to do the GUI-related stuff :)

> You'll find attached a patch for those changes, build against the latest CVS 
> tree.
> 

:)

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