RE: [Pyatcron-devel-list] Plugins and classes

[NICOLOVICI Xavier]

Hi Matthew,

Yes, I would like us to use DocBook for documentation. This will allow us to
build documentation inany kind of format (HTML,PDF,RTF,PS). There is a good
tutorial there:
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/docbook-intro.html



So, I'll let you start writing specs for the classes. But do not work on
CronCollector and AtCollector, I've already started. I'm also writing the
"At" pre-analysis, same as I've done for Cron.

Let us know what you're taking of before starting anything.

I had also some ideas about the way we could automatically load plugin
modules. Does anyone ever started working on that?


Apart from that, sorry if I'm not very active those days, but end of year
means a lot of work for me. And last but not least, I've reached the TOP50
of the best franch badminton players (in my category, of course).
Cooooool...

Bye,

Xavier

> -----Message d'origine-----
> De : Childers, Matthew [mailto:address@hidden
> Envoyé : lundi, 1. décembre 2003 15:36
> À : address@hidden
> Objet : RE: [Pyatcron-devel-list] Plugins and classes
> 
> 
> 
> 
> > -----Original Message-----
> > From: Julien Olivier [mailto:address@hidden
> > Sent: Thursday, November 27, 2003 3:58 AM
> > To: address@hidden
> > Subject: RE: [Pyatcron-devel-list] Plugins and classes
> > 
> > > All, this demonstrate that before coding we should 
> document what to
> do.
> > In software development project, coding represent 20% of 
> the time, not
> > more. And 40% is spent on documeting (requirements, specs, class
> > definitions). The rest is reserved for testing and packaging.
> > >
> > 
> > Of course you're right.
> > 
> > > So, what I would really suggest is spend some time on the PyAtCron
> > documentation first. I'm currentl working on documenting Cron and At
> > daemon to understand how they work and what could be the issues for
> our
> > project. Someone should document the class definitions 
> (name, fields,
> > methods) and what they are expected to do. This would avoid 
> questions
> like
> > Brain has.
> > > If nobody wants to take over this job, then I'll do it ;-)
> > >
> > 
> > I think you're the best for that. At least, you seem better than me
> for
> > that sort of tasks. I replied to Brian in an email about the plugin
> > architecture. Maybe you could use my answer to write a better
> > documentation ?
> > 
> 
> I don't mind doing it (if you all don't mind correcting my 
> mistakes), I
> was planning on doing it this week, but with Thanksgiving and 
> all, I got
> a little busy.  I will try and start on it by Tuesday or 
> Wednesday, but
> I have one question.  Are we using DocBook for documentation?  I have
> never used it before, so I will have to get familiar with it first.
> 
> Thanks,
> Matt
> 
> 
> > --
> > Julien Olivier <address@hidden>
> > 
> > 
> > _______________________________________________
> > Pyatcron-devel-list mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/pyatcron-devel-list
> 
> 
> 
> 
> _______________________________________________
> 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.