Le jeu 13/03/2003 � 15:03, Thierry Vignaud a �crit : > > It was just a quick hack done in 5 minutes, and put into contribs so > > it could be useful to some people. It works for me, but it hasn't > > been tested, and it's very ugly (it kills the kdesktop process, then > > restarts it).
> btw, could you replace it by I am in total admiration by your perl skills. As the Capernaum Centurion would say if he had been a programmer, "I am not worthy that thou shouldest come under my roof: but speak the regexp only, and my code shall be healed." However, I am a bit deceived by your elitist attitude. By the sound of your e-mails, you seem to assume that everyone should know how to use the DrakX code. However, I haven't been able to find any information, neither on the DrakX web page, or in the drakxtools package itself, or in perl-MDK, in the twiki, in the CVS, and of course I tried Google. The only documentation I could find was: http://www.mandrakeforum.org/print.php?lang=en&sid=662 I based DrakClick on that exact same code. Re-writing the whole thing and posting new and improved code on Cooker will not help me write better code. If you could point me to some documentation, or at least comment what you have done, it will help me (and everyone reading Cooker), write new tools eventually. Jean-Michel > changelog: > - simplify, reuse existant code and do not reinvent the wheel > - kill stupid embedding code (USR1/USR2 that do not exists anymore) > - gtk+2 aware > - make it strict & diagnotics pragmas compliant > - make it perl_checker compliant > - i18n/l10n aware (though one have still to extract strings, ...) > - read current configured value > - alter config value in place instead of moving its location in [KDE] section > - shring code by 20%
