RE: [Pyatcron-devel-list] Scheduler Class Definition

[Childers, Matthew]

Ok, Xavier,
        I will update the file to reflect the changes.  Is there anything else 
I need to make changes to or add?  I have never done this type of 
documentation, so just let me know what needs to be added.

Thanks,
Matt

> -----Original Message-----
> From: NICOLOVICI Xavier [mailto:address@hidden
> Sent: Monday, December 08, 2003 1:51 AM
> To: address@hidden
> Subject: RE: [Pyatcron-devel-list] Scheduler Class Definition
> 
> Hi Matthew,
> 
> I'm not sure to understand why you want to make the year attribute
> different
> from every other one. If we keep in mind that this Scheduler class is an
> abstract layers, classes that inherit from it (aka CronEntry and AtEntry)
> will be responsible of dealing with those arrays.
> 
> Do not forget the GUI coding point of vue. It's much easier to have all
> methods having same prototype, difference will be done by inherited
> classes.
> 
> Bye,
> 
> Xavier
> 
> > -----Message d'origine-----
> > De : Childers, Matthew [mailto:address@hidden
> > Envoyé : vendredi, 5. décembre 2003 14:40
> > À : address@hidden
> > Objet : [Pyatcron-devel-list] Scheduler Class Definition
> >
> >
> > Hey all, I have attached a simple definition of the scheduler class.
> > I've never done any serious documentation, so just let me know what
> > needs to be added/removed.
> >
> > Also, I changed the year attribute from an integer array to integer,
> > since I figure that the year will only be used for At and
> > can't be used
> > in a cron command.
> >
> > Let me know what you think,
> > Matt
> >
> >
> 
> 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.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Pyatcron-devel-list mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/pyatcron-devel-list