Le mer 19/03/2003 � 07:06, Thierry Vignaud a �crit : > sorry if i give you such an attitude but as i receive and answer lots > of emails each day, i used to write short, sharp mails.
I know, it's the same for me, I have about 11,000 unread mails (mostly mailing lists though). My friends and family complain that I write straight-to-the-point mails too. And what's worse, is when two french-speaking people e-mail in english, sometimes it transforms what we want to say. > what's more, i was under bugs pressure and my grand father died, so i > was still more unpleasant than usual, if possible. Mes condol�ances... > sorry if you feel bad because of it[-1] I don't feel that bad, it didn't stop me from sleeping, I was just a bit concerned that I didn't do the things The Right Way(tm), and that I could not understand what was wrong. > > However, I haven't been able to find any information, > well, in fact, there's no such doc[0] :-( So I'll do some RTFS ;-) > this is not your fault since: > - there's no doc anywhere > - we have neither the ressources nor the time to write some docs, > - some developers think having perl scripts as "binary" is enough Can you explain the last point? perl scripts as "binary"? > basically, in the old days, the app used to send SIG_USR2 to drakconf > to warn mcc it was ready to display. then mcc would hide the icon > animation and display the application. > there were some obvious flaws in that design: > - if app crashed before sending SIG_USR2, mcc would keep display the > animation (unless you click on cancel or you manually did a "killall > -SIG_USR1 drakconf) Ah! I understand better now =) > there's no real doc. you can look: > - at gi/docs/interactive/* in the cvs for basic usage. > - drakedm, patched drakclick, drakxtv That's a starting point, I never thought of looking in the gi CVS. You should package the doc in the drakxtools RPM, whenever you have a minute. -- Jean-Michel Dault <[EMAIL PROTECTED]>
