Re: Beta_Feedback
|
|
| 1 2 |
Gale (Audacity Team)
|
Thank you, I have forwarded this message to our developers' mailing list. Gale Audacity Team | From Laurent Epinat | Sat, 24 Oct 2009 10:34:26 +0200 | Subject: Beta_Feedback > Just for information, I recompile the beta 1.3.9 version on AMD64 > > and I have an assert when I open the preference dialog box at the > src/prefs/PrefsDialog.cpp line 136 : > wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog exceeds > max size")); > > I add trace on the size and my dialog had > sz.x=857 sz.y=382 > > > My screen resolution is 1920x1200 > I you need more information ... > > > Congratulation for the really good software > > > Here the system informations > > Informations système > Support de format de fichier > libmad (Importation de MP3) Activé > libvorbis (Import et Export Ogg Vorbis ) Activé > libid3tag (support des tag ID3) Activé > libflac (Import et Export FLAC) Activé > libtwolame (export MP2) Désactivé > QuickTime (Importer depuis QuickTime) Désactivé > > > Librairies > libresample > (Conversion de fréquence d'échantillonnage) > Activé > PortAudio > (Lecture et enregistrement audio) > v19 > wxWidgets 2.8.10 > (Unicode) > > Fonctions > Nyquist (Support de modules (plugins)) Activé > LADSPA (Support de modules (plugins)) Activé > Vamp (Support de modules (plugins)) Activé > Audio Units (Support de modules (plugins)) Désactivé > PortMixer (Support du mixage de la carte son) Activé > SoundTouch (Support du changement de hauteur et de tempo) Désactivé > > Informations système > Date de création du programme : Oct 18 2009 > Type de version : Debug build > Préfixe d'intallation /usr/local/ > Répertoire des réglages : /home/laurent/.audacity-data ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Ed Musgrove-2
|
Note that the problem is with width. Note that the Audacity "system
informations" is printed in French. I carefully went through both (after having just downloaded the current CVS head): audacity\src\prefs\PrefsDialog.cpp audacity\src\prefs\KeyConfigPrefs.cpp To ensure that none of the things I have played with recently were inadvertently committed -- they were not. Recently Gale made some changes to the text. I think that this dialogue initially sizes itself based on the width of the longest text string; could this be a translation issue? If possible, I would like to have the reporter comment out that line so that the dialog will open without entering the debugger, then, send me a screenshot of the mouse panel, key binding panel and the directories panel. Je parle un peut de Francais. (But my spelling and grammar are atrocious.) --Ed > -----Original Message----- > From: Gale Andrews [mailto:[hidden email]] > Sent: Sunday, October 25, 2009 1:28 AM > To: Laurent Epinat > Cc: [hidden email]; [hidden email] > Subject: Re: [Audacity-devel] Beta_Feedback > > > Thank you, I have forwarded this message to our developers' > mailing list. > > > > Gale > Audacity Team > > > > > | From Laurent Epinat > | Sat, 24 Oct 2009 10:34:26 +0200 > | Subject: Beta_Feedback > > Just for information, I recompile the beta 1.3.9 version on AMD64 > > > > and I have an assert when I open the preference dialog box at the > > src/prefs/PrefsDialog.cpp line 136 : > > wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog > > exceeds max size")); > > > > I add trace on the size and my dialog had > > sz.x=857 sz.y=382 > > > > > > My screen resolution is 1920x1200 > > I you need more information ... > > > > > > Congratulation for the really good software > > > > > > Here the system informations > > > > Informations système > > Support de format de fichier > > libmad (Importation de MP3) Activé > > libvorbis (Import et Export Ogg Vorbis ) Activé > > libid3tag (support des tag ID3) Activé > > libflac (Import et Export FLAC) Activé > > libtwolame (export MP2) Désactivé > > QuickTime (Importer depuis QuickTime) Désactivé > > > > > > Librairies > > libresample > > (Conversion de fréquence d'échantillonnage) Activé PortAudio (Lecture > > et enregistrement audio) > > v19 > > wxWidgets 2.8.10 > > (Unicode) > > > > Fonctions > > Nyquist (Support de modules (plugins)) Activé > > LADSPA (Support de modules (plugins)) Activé > > Vamp (Support de modules (plugins)) Activé > > Audio Units (Support de modules (plugins)) Désactivé > > PortMixer (Support du mixage de la carte son) Activé > > SoundTouch (Support du changement de hauteur et de tempo) > Désactivé > > > > Informations système > > Date de création du programme : Oct 18 2009 > > Type de version : Debug build > > Préfixe d'intallation /usr/local/ > > Répertoire des réglages : /home/laurent/.audacity-data > > > > > -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the > only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
|
Ed Musgrove-2
|
Is it possible that the recent commit to fr.po caused this:
Update of /cvsroot/audacity/htdocs/locale In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 Modified Files: fr.po Log Message: Updated web site translation from Olivier Humbert Index: fr.po =================================================================== RCS file: /cvsroot/audacity/htdocs/locale/fr.po,v retrieving revision 1.30 retrieving revision 1.31 diff -u -d -r1.30 -r1.31 --- fr.po 22 Sep 2009 21:23:36 -0000 1.30 +++ fr.po 25 Oct 2009 19:32:37 -0000 1.31 @@ -8,7 +8,8 @@ # Pascal Audoux <[hidden email]>, 2009. # Olivier Humbert <[hidden email]>, 2009. msgid "" -msgstr "Project-Id-Version: website-fr-20090721\n" +msgstr "" +"Project-Id-Version: website-fr-20090721\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2009-09-02 08:09+0000\n" "PO-Revision-Date: 2009-09-06 21:32+0100\n" @@ -67,15 +68,15 @@ [...2454 lines suppressed...] +#~ "Audacity. Pour pouvoir l'ouvrir dans un autre programme ou le graver sur " +#~ "CD, vous devez ouvrir le fichier \"projet.aup\" dans Audacity et utiliser " +#~ "les commandes d'exportation (dans le menu Fichier) pour l'enregistrer " +#~ "dans un format standard WAV ou AIFF.</p>" +#~ msgid "" +#~ "<p>Audacity breaks long tracks into small pieces so it can edit them more " +#~ "efficiently. When you save a project, Audacity stores all of the pieces " +#~ "in a folder with a name like b --Ed > -----Original Message----- > From: Ed Musgrove [mailto:[hidden email]] > Sent: Sunday, October 25, 2009 9:52 AM > To: [hidden email] > Subject: Re: [Audacity-devel] Beta_Feedback > > Note that the problem is with width. Note that the Audacity "system > informations" is printed in French. > > I carefully went through both (after having just downloaded the current > head): > audacity\src\prefs\PrefsDialog.cpp > audacity\src\prefs\KeyConfigPrefs.cpp > To ensure that none of the things I have played with recently were > inadvertently committed -- they were not. > > Recently Gale made some changes to the text. I think that this dialogue > initially sizes itself based on the width of the longest text string; could this be > a translation issue? > > If possible, I would like to have the reporter comment out that line so that > the dialog will open without entering the debugger, then, send me a > screenshot of the mouse panel, key binding panel and the directories panel. > > Je parle un peut de Francais. (But my spelling and grammar are atrocious.) > > --Ed > > > > -----Original Message----- > > From: Gale Andrews [mailto:[hidden email]] > > Sent: Sunday, October 25, 2009 1:28 AM > > To: Laurent Epinat > > Cc: [hidden email]; [hidden email] > > Subject: Re: [Audacity-devel] Beta_Feedback > > > > > > Thank you, I have forwarded this message to our developers' > > mailing list. > > > > > > > > Gale > > Audacity Team > > > > > > > > > > | From Laurent Epinat > > | Sat, 24 Oct 2009 10:34:26 +0200 > > | Subject: Beta_Feedback > > > Just for information, I recompile the beta 1.3.9 version on AMD64 > > > > > > and I have an assert when I open the preference dialog box at the > > > src/prefs/PrefsDialog.cpp line 136 : > > > wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog > > > exceeds max size")); > > > > > > I add trace on the size and my dialog had > > > sz.x=857 sz.y=382 > > > > > > > > > My screen resolution is 1920x1200 > > > I you need more information ... > > > > > > > > > Congratulation for the really good software > > > > > > > > > Here the system informations > > > > > > Informations système > > > Support de format de fichier > > > libmad (Importation de MP3) Activé > > > libvorbis (Import et Export Ogg Vorbis ) Activé > > > libid3tag (support des tag ID3) Activé > > > libflac (Import et Export FLAC) Activé > > > libtwolame (export MP2) Désactivé > > > QuickTime (Importer depuis QuickTime) Désactivé > > > > > > > > > Librairies > > > libresample > > > (Conversion de fréquence d'échantillonnage) Activé PortAudio > > > (Lecture et enregistrement audio) > > > v19 > > > wxWidgets 2.8.10 > > > (Unicode) > > > > > > Fonctions > > > Nyquist (Support de modules (plugins)) Activé > > > LADSPA (Support de modules (plugins)) Activé > > > Vamp (Support de modules (plugins)) Activé > > > Audio Units (Support de modules (plugins)) Désactivé > > > PortMixer (Support du mixage de la carte son) Activé > > > SoundTouch (Support du changement de hauteur et de tempo) > > Désactivé > > > > > > Informations système > > > Date de création du programme : Oct 18 2009 > > > Type de version : Debug build > > > Préfixe d'intallation /usr/local/ > > > Répertoire des réglages : /home/laurent/.audacity-data > > > > > > > > > > > > -- > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is > the > > only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and > > stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > audacity-devel mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > ---------------------------------------------------------------------------- -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the > only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
In reply to this post
by Ed Musgrove-2
| From "Ed Musgrove" <[hidden email]> | To <[hidden email]> | Subject [Audacity-devel] Beta_Feedback > Is it possible that the recent commit to fr.po caused this: > > Update of /cvsroot/audacity/htdocs/locale In directory > 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > > Modified Files: > fr.po > Log Message: > Updated web site translation from Olivier Humbert No, that is the translation for the web site, not the .po file for the software. See below. | From "Ed Musgrove" <[hidden email]> | Sun, 25 Oct 2009 09:52:08 -0700 | Subject: [Audacity-devel] Beta_Feedback > Note that the problem is with width. Note that the Audacity "system > informations" is printed in French. > > I carefully went through both (after having just downloaded the current CVS > head): > audacity\src\prefs\PrefsDialog.cpp > audacity\src\prefs\KeyConfigPrefs.cpp > To ensure that none of the things I have played with recently were > inadvertently committed -- they were not. > > Recently Gale made some changes to the text. I think that this dialogue > initially sizes itself based on the width of the longest text string; could > this be a translation issue? If the problem is specific to running Audacity in French, using the .mo file compiled from fr.po, then no, because my string changes have not yet had a French translation committed. Using a Unicode Release build from CVS a few days ago on Ubuntu 9.04 (so using the current fr.po file) the longer text seems to wrap round correctly. The preferences dialogue could in fact still be expanded a little horizontally to the full 800px width. > If possible, I would like to have the reporter comment out that line so that > the dialog will open without entering the debugger, then, send me a > screenshot of the mouse panel, key binding panel and the directories panel. > > Je parle un peut de Francais. (But my spelling and grammar are atrocious.) Ed, I've sent you the e-mail address of the person privately, so feel free to contact them off-list for more information (but don't overdo it if he isn't keen to go to a lot of trouble). :=) Thanks Gale > > -----Original Message----- > > From: Gale Andrews [mailto:[hidden email]] > > Sent: Sunday, October 25, 2009 1:28 AM > > To: Laurent Epinat > > Cc: [hidden email]; [hidden email] > > Subject: Re: [Audacity-devel] Beta_Feedback > > > > > > Thank you, I have forwarded this message to our developers' > > mailing list. > > > > > > > > Gale > > Audacity Team > > > > > > | From Laurent Epinat > > | Sat, 24 Oct 2009 10:34:26 +0200 > > | Subject: Beta_Feedback > > > Just for information, I recompile the beta 1.3.9 version on AMD64 > > > > > > and I have an assert when I open the preference dialog box at the > > > src/prefs/PrefsDialog.cpp line 136 : > > > wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog > > > exceeds max size")); > > > > > > I add trace on the size and my dialog had > > > sz.x=857 sz.y=382 > > > > > > > > > My screen resolution is 1920x1200 > > > I you need more information ... > > > > > > > > > Congratulation for the really good software > > > > > > > > > Here the system informations > > > > > > Informations système > > > Support de format de fichier > > > libmad (Importation de MP3) Activé > > > libvorbis (Import et Export Ogg Vorbis ) Activé > > > libid3tag (support des tag ID3) Activé > > > libflac (Import et Export FLAC) Activé > > > libtwolame (export MP2) Désactivé > > > QuickTime (Importer depuis QuickTime) Désactivé > > > > > > > > > Librairies > > > libresample > > > (Conversion de fréquence d'échantillonnage) Activé PortAudio (Lecture > > > et enregistrement audio) > > > v19 > > > wxWidgets 2.8.10 > > > (Unicode) > > > > > > Fonctions > > > Nyquist (Support de modules (plugins)) Activé > > > LADSPA (Support de modules (plugins)) Activé > > > Vamp (Support de modules (plugins)) Activé > > > Audio Units (Support de modules (plugins)) Désactivé > > > PortMixer (Support du mixage de la carte son) Activé > > > SoundTouch (Support du changement de hauteur et de tempo) > > Désactivé > > > > > > Informations système > > > Date de création du programme : Oct 18 2009 > > > Type de version : Debug build > > > Préfixe d'intallation /usr/local/ > > > Répertoire des réglages : /home/laurent/.audacity-data ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
After release of "stable" I propose to make the prefs panel user resizable
(restrained only by valid screen size) and the keyboard panel columns automatically size themselves (I have the code completely finished) just like the mouse prefs panel is. This will resolve most if not all such issues. Vaguely related, I gave Gale working code which makes the Help/About... panel user resizable. (it is a trivial one line change). BTW, is there a problem or reason why that was never committed (patch attached)? --Ed > -----Original Message----- > From: Gale Andrews [mailto:[hidden email]] > Sent: Sunday, October 25, 2009 7:53 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Beta_Feedback > > > | From "Ed Musgrove" <[hidden email]> To > | <[hidden email]> > | Subject [Audacity-devel] Beta_Feedback > > Is it possible that the recent commit to fr.po caused this: > > > > Update of /cvsroot/audacity/htdocs/locale In directory > > 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > > > > Modified Files: > > fr.po > > Log Message: > > Updated web site translation from Olivier Humbert > > No, that is the translation for the web site, not the .po file for the > See below. > > > | From "Ed Musgrove" <[hidden email]> > | Sun, 25 Oct 2009 09:52:08 -0700 > | Subject: [Audacity-devel] Beta_Feedback > > Note that the problem is with width. Note that the Audacity "system > > informations" is printed in French. > > > > I carefully went through both (after having just downloaded the current > CVS > > head): > > audacity\src\prefs\PrefsDialog.cpp > > audacity\src\prefs\KeyConfigPrefs.cpp > > To ensure that none of the things I have played with recently were > > inadvertently committed -- they were not. > > > > Recently Gale made some changes to the text. I think that this dialogue > > initially sizes itself based on the width of the longest text string; > > this be a translation issue? > > If the problem is specific to running Audacity in French, using the .mo > file compiled from fr.po, then no, because my string changes have not > yet had a French translation committed. > > Using a Unicode Release build from CVS a few days ago on Ubuntu 9.04 > (so using the current fr.po file) the longer text seems to wrap round > correctly. The preferences dialogue could in fact still be expanded a > little horizontally to the full 800px width. > > > > > If possible, I would like to have the reporter comment out that line so > > the dialog will open without entering the debugger, then, send me a > > screenshot of the mouse panel, key binding panel and the directories > panel. > > > > Je parle un peut de Francais. (But my spelling and grammar are > > Ed, I've sent you the e-mail address of the person privately, so feel free to > contact them off-list for more information (but don't overdo it if he > isn't keen to go to a lot of trouble). :=) > > > > Thanks > > > > Gale > > > > > > > -----Original Message----- > > > From: Gale Andrews [mailto:[hidden email]] > > > Sent: Sunday, October 25, 2009 1:28 AM > > > To: Laurent Epinat > > > Cc: [hidden email]; [hidden email] > > > Subject: Re: [Audacity-devel] Beta_Feedback > > > > > > > > > Thank you, I have forwarded this message to our developers' > > > mailing list. > > > > > > > > > > > > Gale > > > Audacity Team > > > > > > > > > | From Laurent Epinat > > > | Sat, 24 Oct 2009 10:34:26 +0200 > > > | Subject: Beta_Feedback > > > > Just for information, I recompile the beta 1.3.9 version on AMD64 > > > > > > > > and I have an assert when I open the preference dialog box at the > > > > src/prefs/PrefsDialog.cpp line 136 : > > > > wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog > > > > exceeds max size")); > > > > > > > > I add trace on the size and my dialog had > > > > sz.x=857 sz.y=382 > > > > > > > > > > > > My screen resolution is 1920x1200 > > > > I you need more information ... > > > > > > > > > > > > Congratulation for the really good software > > > > > > > > > > > > Here the system informations > > > > > > > > Informations système > > > > Support de format de fichier > > > > libmad (Importation de MP3) Activé > > > > libvorbis (Import et Export Ogg Vorbis ) Activé > > > > libid3tag (support des tag ID3) Activé > > > > libflac (Import et Export FLAC) Activé > > > > libtwolame (export MP2) Désactivé > > > > QuickTime (Importer depuis QuickTime) Désactivé > > > > > > > > > > > > Librairies > > > > libresample > > > > (Conversion de fréquence d'échantillonnage) Activé PortAudio > > > > et enregistrement audio) > > > > v19 > > > > wxWidgets 2.8.10 > > > > (Unicode) > > > > > > > > Fonctions > > > > Nyquist (Support de modules (plugins)) Activé > > > > LADSPA (Support de modules (plugins)) Activé > > > > Vamp (Support de modules (plugins)) Activé > > > > Audio Units (Support de modules (plugins)) Désactivé > > > > PortMixer (Support du mixage de la carte son) Activé > > > > SoundTouch (Support du changement de hauteur et de tempo) > > > Désactivé > > > > > > > > Informations système > > > > Date de création du programme : Oct 18 2009 > > > > Type de version : Debug build > > > > Préfixe d'intallation /usr/local/ > > > > Répertoire des réglages : /home/laurent/.audacity-data > > > > > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
resizableHelpAboutDialog.patch (695 bytes)
Vaughan Johnson
|
Ed Musgrove wrote: > After release of "stable" I propose to make the prefs panel user resizable > (restrained only by valid screen size) and the keyboard panel columns > automatically size themselves (I have the code completely finished) just > like the mouse prefs panel is. This will resolve most if not all such > issues. Please also get Leland's opinion on this before you make the change. I didn't follow it, but I'm sure there was some reason you can only resize it a certain range of sizes. - V ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
Hoping to get most active devs to at least contribute to the design stage.
--Ed > -----Original Message----- > From: Vaughan Johnson [mailto:[hidden email]] > Sent: Tuesday, October 27, 2009 3:54 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Beta_Feedback > > > > Ed Musgrove wrote: > > After release of "stable" I propose to make the prefs panel user > > resizable (restrained only by valid screen size) and the keyboard > > panel columns automatically size themselves (I have the code > > completely finished) just like the mouse prefs panel is. This will > > resolve most if not all such issues. > Please also get Leland's opinion on this before you make the change. I > follow it, but I'm sure there was some reason you can only resize it a certain > range of sizes. > > - V > > ---------------------------------------------------------------------------- -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the > only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Martyn Shaw-2
|
In reply to this post
by Ed Musgrove-2
Hi Ed
I have not been following the debate over prefs and resizing. And we have issues about non-coders committing patches that could affect other areas of code. I see no reason (on my platform), or any philosophical reason why the 'about' box shouldn't be resizable, and so I committed it (others may chose to revert). Just the sort of patch that is distracting us (me) from 2.0. It should have gone into a patch-tracker of some sort, commented on by people who tried it but maybe aren't 'committers', and not come up on -devel until later. This isn't a criticism of you or what you've done, but of the limited system that we have right now. I'm hoping that Bugzilla and it's protocols may help with this type of developer-bandwidth problem. TTFN Martyn Ed Musgrove wrote: > After release of "stable" I propose to make the prefs panel user resizable > (restrained only by valid screen size) and the keyboard panel columns > automatically size themselves (I have the code completely finished) just > like the mouse prefs panel is. This will resolve most if not all such > issues. Vaguely related, I gave Gale working code which makes the > Help/About... panel user resizable. (it is a trivial one line change). BTW, > is there a problem or reason why that was never committed (patch attached)? > > --Ed > > >> -----Original Message----- >> From: Gale Andrews [mailto:[hidden email]] >> Sent: Sunday, October 25, 2009 7:53 PM >> To: [hidden email] >> Subject: Re: [Audacity-devel] Beta_Feedback >> >> >> | From "Ed Musgrove" <[hidden email]> To >> | <[hidden email]> >> | Subject [Audacity-devel] Beta_Feedback >>> Is it possible that the recent commit to fr.po caused this: >>> >>> Update of /cvsroot/audacity/htdocs/locale In directory >>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 >>> >>> Modified Files: >>> fr.po >>> Log Message: >>> Updated web site translation from Olivier Humbert >> No, that is the translation for the web site, not the .po file for the > software. >> See below. >> >> >> | From "Ed Musgrove" <[hidden email]> >> | Sun, 25 Oct 2009 09:52:08 -0700 >> | Subject: [Audacity-devel] Beta_Feedback >>> Note that the problem is with width. Note that the Audacity "system >>> informations" is printed in French. >>> >>> I carefully went through both (after having just downloaded the current >> CVS >>> head): >>> audacity\src\prefs\PrefsDialog.cpp >>> audacity\src\prefs\KeyConfigPrefs.cpp >>> To ensure that none of the things I have played with recently were >>> inadvertently committed -- they were not. >>> >>> Recently Gale made some changes to the text. I think that this dialogue >>> initially sizes itself based on the width of the longest text string; > could >>> this be a translation issue? >> If the problem is specific to running Audacity in French, using the .mo >> file compiled from fr.po, then no, because my string changes have not >> yet had a French translation committed. >> >> Using a Unicode Release build from CVS a few days ago on Ubuntu 9.04 >> (so using the current fr.po file) the longer text seems to wrap round >> correctly. The preferences dialogue could in fact still be expanded a >> little horizontally to the full 800px width. >> >> >> >>> If possible, I would like to have the reporter comment out that line so > that >>> the dialog will open without entering the debugger, then, send me a >>> screenshot of the mouse panel, key binding panel and the directories >> panel. >>> Je parle un peut de Francais. (But my spelling and grammar are > atrocious.) >> Ed, I've sent you the e-mail address of the person privately, so feel free > to >> contact them off-list for more information (but don't overdo it if he >> isn't keen to go to a lot of trouble). :=) >> >> >> >> Thanks >> >> >> >> Gale >> >> >> >> >>>> -----Original Message----- >>>> From: Gale Andrews [mailto:[hidden email]] >>>> Sent: Sunday, October 25, 2009 1:28 AM >>>> To: Laurent Epinat >>>> Cc: [hidden email]; [hidden email] >>>> Subject: Re: [Audacity-devel] Beta_Feedback >>>> >>>> >>>> Thank you, I have forwarded this message to our developers' >>>> mailing list. >>>> >>>> >>>> >>>> Gale >>>> Audacity Team >>>> >>>> >>>> | From Laurent Epinat >>>> | Sat, 24 Oct 2009 10:34:26 +0200 >>>> | Subject: Beta_Feedback >>>>> Just for information, I recompile the beta 1.3.9 version on AMD64 >>>>> >>>>> and I have an assert when I open the preference dialog box at the >>>>> src/prefs/PrefsDialog.cpp line 136 : >>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog >>>>> exceeds max size")); >>>>> >>>>> I add trace on the size and my dialog had >>>>> sz.x=857 sz.y=382 >>>>> >>>>> >>>>> My screen resolution is 1920x1200 >>>>> I you need more information ... >>>>> >>>>> >>>>> Congratulation for the really good software >>>>> >>>>> >>>>> Here the system informations >>>>> >>>>> Informations système >>>>> Support de format de fichier >>>>> libmad (Importation de MP3) Activé >>>>> libvorbis (Import et Export Ogg Vorbis ) Activé >>>>> libid3tag (support des tag ID3) Activé >>>>> libflac (Import et Export FLAC) Activé >>>>> libtwolame (export MP2) Désactivé >>>>> QuickTime (Importer depuis QuickTime) Désactivé >>>>> >>>>> >>>>> Librairies >>>>> libresample >>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio > (Lecture >>>>> et enregistrement audio) >>>>> v19 >>>>> wxWidgets 2.8.10 >>>>> (Unicode) >>>>> >>>>> Fonctions >>>>> Nyquist (Support de modules (plugins)) Activé >>>>> LADSPA (Support de modules (plugins)) Activé >>>>> Vamp (Support de modules (plugins)) Activé >>>>> Audio Units (Support de modules (plugins)) Désactivé >>>>> PortMixer (Support du mixage de la carte son) Activé >>>>> SoundTouch (Support du changement de hauteur et de tempo) >>>> Désactivé >>>>> Informations système >>>>> Date de création du programme : Oct 18 2009 >>>>> Type de version : Debug build >>>>> Préfixe d'intallation /usr/local/ >>>>> Répertoire des réglages : /home/laurent/.audacity-data >> >> >> >> > ---------------------------------------------------------------------------- > -- >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Martyn Shaw <[hidden email]> | Sat, 31 Oct 2009 00:39:14 +0000 | Subject: [Audacity-devel] Beta_Feedback >... I see no reason (on my platform), or any philosophical reason > why the 'about' box shouldn't be resizable, and > so I committed it (others may chose to revert). > > Just the sort of patch that is distracting us (me) from 2.0. It > should have gone into a patch-tracker of some sort, commented on by > people who tried it but maybe aren't 'committers', and not come up on > -devel until later. This isn't a criticism of you or what you've > done, but of the limited system that we have right now. I'm hoping > that Bugzilla and it's protocols may help with this type of > developer-bandwidth problem. Bugzilla does not from my admittedly limited knowledge have a patch tracker. It has a patch viewer (view patches that you have attached to bugs): http://www.bugzilla.org/docs/2.18/html/patchviewer.html So as far as I can see from the test pages we've had so far, that means creating a "bug" or some other "object" for the patch, with cases where the patch actually relates to an already listed bug, and cases where the object would have to be created specifically for it (as in the above case). If we finally use Bugzilla, is the above a good idea, or are entries on a Wiki page better? Those would presumably require the submitter to actually post a short initial message to -devel (patch attached, details of what it does on the Wiki). But maybe protocol would require a short message to -devel anyway, even in the case of a "patch tracker"? Comments? Gale > Ed Musgrove wrote: > > After release of "stable" I propose to make the prefs panel user resizable > > (restrained only by valid screen size) and the keyboard panel columns > > automatically size themselves (I have the code completely finished) just > > like the mouse prefs panel is. This will resolve most if not all such > > issues. Vaguely related, I gave Gale working code which makes the > > Help/About... panel user resizable. (it is a trivial one line change). BTW, > > is there a problem or reason why that was never committed (patch attached)? > > > > --Ed > > > > > >> -----Original Message----- > >> From: Gale Andrews [mailto:[hidden email]] > >> Sent: Sunday, October 25, 2009 7:53 PM > >> To: [hidden email] > >> Subject: Re: [Audacity-devel] Beta_Feedback > >> > >> > >> | From "Ed Musgrove" <[hidden email]> To > >> | <[hidden email]> > >> | Subject [Audacity-devel] Beta_Feedback > >>> Is it possible that the recent commit to fr.po caused this: > >>> > >>> Update of /cvsroot/audacity/htdocs/locale In directory > >>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > >>> > >>> Modified Files: > >>> fr.po > >>> Log Message: > >>> Updated web site translation from Olivier Humbert > >> No, that is the translation for the web site, not the .po file for the > > software. > >> See below. > >> > >> > >> | From "Ed Musgrove" <[hidden email]> > >> | Sun, 25 Oct 2009 09:52:08 -0700 > >> | Subject: [Audacity-devel] Beta_Feedback > >>> Note that the problem is with width. Note that the Audacity "system > >>> informations" is printed in French. > >>> > >>> I carefully went through both (after having just downloaded the current > >> CVS > >>> head): > >>> audacity\src\prefs\PrefsDialog.cpp > >>> audacity\src\prefs\KeyConfigPrefs.cpp > >>> To ensure that none of the things I have played with recently were > >>> inadvertently committed -- they were not. > >>> > >>> Recently Gale made some changes to the text. I think that this dialogue > >>> initially sizes itself based on the width of the longest text string; > > could > >>> this be a translation issue? > >> If the problem is specific to running Audacity in French, using the .mo > >> file compiled from fr.po, then no, because my string changes have not > >> yet had a French translation committed. > >> > >> Using a Unicode Release build from CVS a few days ago on Ubuntu 9.04 > >> (so using the current fr.po file) the longer text seems to wrap round > >> correctly. The preferences dialogue could in fact still be expanded a > >> little horizontally to the full 800px width. > >> > >> > >> > >>> If possible, I would like to have the reporter comment out that line so > > that > >>> the dialog will open without entering the debugger, then, send me a > >>> screenshot of the mouse panel, key binding panel and the directories > >> panel. > >>> Je parle un peut de Francais. (But my spelling and grammar are > > atrocious.) > >> Ed, I've sent you the e-mail address of the person privately, so feel free > > to > >> contact them off-list for more information (but don't overdo it if he > >> isn't keen to go to a lot of trouble). :=) > >> > >> > >> > >> Thanks > >> > >> > >> > >> Gale > >> > >> > >> > >> > >>>> -----Original Message----- > >>>> From: Gale Andrews [mailto:[hidden email]] > >>>> Sent: Sunday, October 25, 2009 1:28 AM > >>>> To: Laurent Epinat > >>>> Cc: [hidden email]; [hidden email] > >>>> Subject: Re: [Audacity-devel] Beta_Feedback > >>>> > >>>> > >>>> Thank you, I have forwarded this message to our developers' > >>>> mailing list. > >>>> > >>>> > >>>> > >>>> Gale > >>>> Audacity Team > >>>> > >>>> > >>>> | From Laurent Epinat > >>>> | Sat, 24 Oct 2009 10:34:26 +0200 > >>>> | Subject: Beta_Feedback > >>>>> Just for information, I recompile the beta 1.3.9 version on AMD64 > >>>>> > >>>>> and I have an assert when I open the preference dialog box at the > >>>>> src/prefs/PrefsDialog.cpp line 136 : > >>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences dialog > >>>>> exceeds max size")); > >>>>> > >>>>> I add trace on the size and my dialog had > >>>>> sz.x=857 sz.y=382 > >>>>> > >>>>> > >>>>> My screen resolution is 1920x1200 > >>>>> I you need more information ... > >>>>> > >>>>> > >>>>> Congratulation for the really good software > >>>>> > >>>>> > >>>>> Here the system informations > >>>>> > >>>>> Informations système > >>>>> Support de format de fichier > >>>>> libmad (Importation de MP3) Activé > >>>>> libvorbis (Import et Export Ogg Vorbis ) Activé > >>>>> libid3tag (support des tag ID3) Activé > >>>>> libflac (Import et Export FLAC) Activé > >>>>> libtwolame (export MP2) Désactivé > >>>>> QuickTime (Importer depuis QuickTime) Désactivé > >>>>> > >>>>> > >>>>> Librairies > >>>>> libresample > >>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio > > (Lecture > >>>>> et enregistrement audio) > >>>>> v19 > >>>>> wxWidgets 2.8.10 > >>>>> (Unicode) > >>>>> > >>>>> Fonctions > >>>>> Nyquist (Support de modules (plugins)) Activé > >>>>> LADSPA (Support de modules (plugins)) Activé > >>>>> Vamp (Support de modules (plugins)) Activé > >>>>> Audio Units (Support de modules (plugins)) Désactivé > >>>>> PortMixer (Support du mixage de la carte son) Activé > >>>>> SoundTouch (Support du changement de hauteur et de tempo) > >>>> Désactivé > >>>>> Informations système > >>>>> Date de création du programme : Oct 18 2009 > >>>>> Type de version : Debug build > >>>>> Préfixe d'intallation /usr/local/ > >>>>> Répertoire des réglages : /home/laurent/.audacity-data > >> > >> > >> > >> > > ---------------------------------------------------------------------------- > > -- > >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA > >> is the only developer event you need to attend this year. Jumpstart your > >> developing skills, take BlackBerry mobile applications to market and stay > >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! > >> http://p.sf.net/sfu/devconference > >> _______________________________________________ > >> audacity-devel mailing list > >> [hidden email] > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > >> > >> ------------------------------------------------------------------------ > >> > >> ------------------------------------------------------------------------------ > >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA > >> is the only developer event you need to attend this year. Jumpstart your > >> developing skills, take BlackBerry mobile applications to market and stay > >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! > >> http://p.sf.net/sfu/devconference > >> > >> ------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> audacity-devel mailing list > >> [hidden email] > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
Is Audacity a professionally developed product? Is it just something that a
few people have thrown together in their spare time? Do we expect Audacity to be used primarily by those capable of compiling and understanding the source code, or are the vast majority of users audiophiles who have no desire nor ability to compile the code? Can the venerable Audacity mentors who are more focused on major problems accept the enthusiast coder who might be more comfortable starting out dealing with the little things? Any change in the code should be documented. If it is a trivial change made by a longtime developer a comment with initials and the date next to the change might be sufficient. Anything which changes the user's experience should be formally proposed, discussed and the code peer-reviewed with alpha testing by at least one developer on each major platform. I think we need a category of bug like "feature request". That way something sent to @feedback can be triaged by venerable developers into this category when appropriate. Recognized developers and hackers (like me) may also propose a "feature request" bug; someone with authorization on the bug list would need to actually enter it. --Ed > -----Original Message----- > From: Gale Andrews [mailto:[hidden email]] > Sent: Friday, October 30, 2009 9:14 PM > To: [hidden email] > Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > | From Martyn Shaw <[hidden email]> Sat, 31 Oct 2009 > | 00:39:14 +0000 > | Subject: [Audacity-devel] Beta_Feedback > >... I see no reason (on my platform), or any philosophical reason why > >the 'about' box shouldn't be resizable, and so I committed it (others > >may chose to revert). > > > > Just the sort of patch that is distracting us (me) from 2.0. It > > should have gone into a patch-tracker of some sort, commented on by > > people who tried it but maybe aren't 'committers', and not come up on > > -devel until later. This isn't a criticism of you or what you've > > done, but of the limited system that we have right now. I'm hoping > > that Bugzilla and it's protocols may help with this type of > > developer-bandwidth problem. > > Bugzilla does not from my admittedly limited knowledge have a patch > tracker. It has a patch viewer (view patches that you have attached to > http://www.bugzilla.org/docs/2.18/html/patchviewer.html > > So as far as I can see from the test pages we've had so far, that means > creating a "bug" or some other "object" for the patch, with cases where the > patch actually relates to an already listed bug, and cases where the object > would have to be created specifically for it (as in the above case). > > If we finally use Bugzilla, is the above a good idea, or are entries on a Wiki > page better? Those would presumably require the submitter to actually post > a short initial message to -devel (patch attached, details of what it does on > the Wiki). > > But maybe protocol would require a short message to -devel anyway, > even in the case of a "patch tracker"? > > Comments? > > > > Gale > > > > > Ed Musgrove wrote: > > > After release of "stable" I propose to make the prefs panel user > > > resizable (restrained only by valid screen size) and the keyboard > > > panel columns automatically size themselves (I have the code > > > completely finished) just like the mouse prefs panel is. This will > > > resolve most if not all such issues. Vaguely related, I gave Gale > > > working code which makes the Help/About... panel user resizable. (it > > > is a trivial one line change). BTW, is there a problem or reason why > was never committed (patch attached)? > > > > > > --Ed > > > > > > > > >> -----Original Message----- > > >> From: Gale Andrews [mailto:[hidden email]] > > >> Sent: Sunday, October 25, 2009 7:53 PM > > >> To: [hidden email] > > >> Subject: Re: [Audacity-devel] Beta_Feedback > > >> > > >> > > >> | From "Ed Musgrove" <[hidden email]> To > > >> | <[hidden email]> > > >> | Subject [Audacity-devel] Beta_Feedback > > >>> Is it possible that the recent commit to fr.po caused this: > > >>> > > >>> Update of /cvsroot/audacity/htdocs/locale In directory > > >>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > > >>> > > >>> Modified Files: > > >>> fr.po > > >>> Log Message: > > >>> Updated web site translation from Olivier Humbert > > >> No, that is the translation for the web site, not the .po file for > > >> the > > > software. > > >> See below. > > >> > > >> > > >> | From "Ed Musgrove" <[hidden email]> Sun, 25 Oct > 2009 > > >> | 09:52:08 -0700 > > >> | Subject: [Audacity-devel] Beta_Feedback > > >>> Note that the problem is with width. Note that the Audacity > > >>> "system informations" is printed in French. > > >>> > > >>> I carefully went through both (after having just downloaded the > > >>> current > > >> CVS > > >>> head): > > >>> audacity\src\prefs\PrefsDialog.cpp > > >>> audacity\src\prefs\KeyConfigPrefs.cpp > > >>> To ensure that none of the things I have played with recently were > > >>> inadvertently committed -- they were not. > > >>> > > >>> Recently Gale made some changes to the text. I think that this > > >>> dialogue initially sizes itself based on the width of the longest > > >>> text string; > > > could > > >>> this be a translation issue? > > >> If the problem is specific to running Audacity in French, using the > > >> .mo file compiled from fr.po, then no, because my string changes > > >> have not yet had a French translation committed. > > >> > > >> Using a Unicode Release build from CVS a few days ago on Ubuntu > > >> 9.04 (so using the current fr.po file) the longer text seems to > > >> wrap round correctly. The preferences dialogue could in fact still > > >> be expanded a little horizontally to the full 800px width. > > >> > > >> > > >> > > >>> If possible, I would like to have the reporter comment out that > > >>> line so > > > that > > >>> the dialog will open without entering the debugger, then, send me > > >>> a screenshot of the mouse panel, key binding panel and the > > >>> directories > > >> panel. > > >>> Je parle un peut de Francais. (But my spelling and grammar are > > > atrocious.) > > >> Ed, I've sent you the e-mail address of the person privately, so > > >> feel free > > > to > > >> contact them off-list for more information (but don't overdo it if > > >> he isn't keen to go to a lot of trouble). :=) > > >> > > >> > > >> > > >> Thanks > > >> > > >> > > >> > > >> Gale > > >> > > >> > > >> > > >> > > >>>> -----Original Message----- > > >>>> From: Gale Andrews [mailto:[hidden email]] > > >>>> Sent: Sunday, October 25, 2009 1:28 AM > > >>>> To: Laurent Epinat > > >>>> Cc: [hidden email]; > > >>>> [hidden email] > > >>>> Subject: Re: [Audacity-devel] Beta_Feedback > > >>>> > > >>>> > > >>>> Thank you, I have forwarded this message to our developers' > > >>>> mailing list. > > >>>> > > >>>> > > >>>> > > >>>> Gale > > >>>> Audacity Team > > >>>> > > >>>> > > >>>> | From Laurent Epinat > > >>>> | Sat, 24 Oct 2009 10:34:26 +0200 > > >>>> | Subject: Beta_Feedback > > >>>>> Just for information, I recompile the beta 1.3.9 version on > > >>>>> AMD64 > > >>>>> > > >>>>> and I have an assert when I open the preference dialog box at > > >>>>> the src/prefs/PrefsDialog.cpp line 136 : > > >>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences > dialog > > >>>>> exceeds max size")); > > >>>>> > > >>>>> I add trace on the size and my dialog had > > >>>>> sz.x=857 sz.y=382 > > >>>>> > > >>>>> > > >>>>> My screen resolution is 1920x1200 I you need more information > > >>>>> ... > > >>>>> > > >>>>> > > >>>>> Congratulation for the really good software > > >>>>> > > >>>>> > > >>>>> Here the system informations > > >>>>> > > >>>>> Informations système > > >>>>> Support de format de fichier > > >>>>> libmad (Importation de MP3) Activé > > >>>>> libvorbis (Import et Export Ogg Vorbis ) Activé > > >>>>> libid3tag (support des tag ID3) Activé > > >>>>> libflac (Import et Export FLAC) Activé > > >>>>> libtwolame (export MP2) Désactivé > > >>>>> QuickTime (Importer depuis QuickTime) Désactivé > > >>>>> > > >>>>> > > >>>>> Librairies > > >>>>> libresample > > >>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio > > > (Lecture > > >>>>> et enregistrement audio) > > >>>>> v19 > > >>>>> wxWidgets 2.8.10 > > >>>>> (Unicode) > > >>>>> > > >>>>> Fonctions > > >>>>> Nyquist (Support de modules (plugins)) > > >>>>> LADSPA (Support de modules (plugins)) Activé > > >>>>> Vamp (Support de modules (plugins)) Activé > > >>>>> Audio Units (Support de modules (plugins)) Désactivé > > >>>>> PortMixer (Support du mixage de la carte son) Activé > > >>>>> SoundTouch (Support du changement de hauteur et de tempo) > > >>>> Désactivé > > >>>>> Informations système > > >>>>> Date de création du programme : Oct 18 2009 > > >>>>> Type de version : Debug build > > >>>>> Préfixe d'intallation /usr/local/ > > >>>>> Répertoire des réglages : /home/laurent/.audacity-data > > >> > > >> > > >> > > >> > > > -------------------------------------------------------------------- > > > -------- > > > -- > > >> Come build with us! The BlackBerry(R) Developer Conference in SF, > > >> CA is the only developer event you need to attend this year. > > >> Jumpstart your developing skills, take BlackBerry mobile > > >> applications to market and stay ahead of the curve. Join us from > November 9 - 12, 2009. Register now! > > >> http://p.sf.net/sfu/devconference > > >> _______________________________________________ > > >> audacity-devel mailing list > > >> [hidden email] > > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > >> > > >> ------------------------------------------------------------------- > > >> ----- > > >> > > >> ------------------------------------------------------------------- > > >> ----------- Come build with us! The BlackBerry(R) Developer > > >> Conference in SF, CA is the only developer event you need to attend > > >> this year. Jumpstart your developing skills, take BlackBerry mobile > > >> applications to market and stay ahead of the curve. Join us from > > >> November 9 - 12, 2009. Register now! > > >> http://p.sf.net/sfu/devconference > > >> > > >> ------------------------------------------------------------------- > > >> ----- > > >> > > >> _______________________________________________ > > >> audacity-devel mailing list > > >> [hidden email] > > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > ---------------------------------------------------------------------- > > -------- Come build with us! The BlackBerry(R) Developer Conference in > > SF, CA is the only developer event you need to attend this year. > > Jumpstart your developing skills, take BlackBerry mobile applications > > to market and stay ahead of the curve. Join us from November 9 - 12, > > 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > audacity-devel mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the > only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From "Ed Musgrove" <[hidden email]> | Fri, 30 Oct 2009 21:54:03 -0700 | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > Is Audacity a professionally developed product? Is it just something that a > few people have thrown together in their spare time? Do we expect Audacity > to be used primarily by those capable of compiling and understanding the > source code, or are the vast majority of users audiophiles who have no > desire nor ability to compile the code? Can the venerable Audacity mentors > who are more focused on major problems accept the enthusiast coder who > might be more comfortable starting out dealing with the little things? > > Any change in the code should be documented. If it is a trivial change made > by a longtime developer a comment with initials and the date next to the > change might be sufficient. Anything which changes the user's experience > should be formally proposed, discussed and the code peer-reviewed with alpha > testing by at least one developer on each major platform. > > I think we need a category of bug like "feature request". That way something > sent to @feedback can be triaged by venerable developers into this category > when appropriate. Recognized developers and hackers (like me) may also > propose a "feature request" bug; someone with authorization on the bug list > would need to actually enter it. We've pretty much agreed as far as I understand it that "enhancements" tracked in Bugzilla or whatever system we use should only be those supported by a developer (or more loosely, active contributors to this list). User requests sent to feedback@ will continue to be processed on: http://wiki.audacityteam.org/index.php?title=Feature_Requests We can take valuable/strongly voted for items from that page at any time and turn it into a "developer supported" enhancement. The point of my question was whether we want to load a formal bug tracker with what may be relatively trivial "enhancement" patches by creating a new item just to hold that patch; or store patches (or links to them) otherwise. Obviously if we use Bugzilla we can attach a patch to an actual P1- P5 bug (or if Checklist remains in the short/medium term, a link to the patch). A patch like that isn't likely to drop out of sight. I think the problem is more the large number of patches for "enhancements", some of which may come from someone completely new to the list, so they couldn't be described as "developer supported" in the sense of the enhancements I was thinking of storing in the bug tracker (where the case for them has already been largely agreed). Gale > > -----Original Message----- > > From: Gale Andrews [mailto:[hidden email]] > > Sent: Friday, October 30, 2009 9:14 PM > > To: [hidden email] > > Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > > > > | From Martyn Shaw <[hidden email]> Sat, 31 Oct 2009 > > | 00:39:14 +0000 > > | Subject: [Audacity-devel] Beta_Feedback > > >... I see no reason (on my platform), or any philosophical reason why > > >the 'about' box shouldn't be resizable, and so I committed it (others > > >may chose to revert). > > > > > > Just the sort of patch that is distracting us (me) from 2.0. It > > > should have gone into a patch-tracker of some sort, commented on by > > > people who tried it but maybe aren't 'committers', and not come up on > > > -devel until later. This isn't a criticism of you or what you've > > > done, but of the limited system that we have right now. I'm hoping > > > that Bugzilla and it's protocols may help with this type of > > > developer-bandwidth problem. > > > > Bugzilla does not from my admittedly limited knowledge have a patch > > tracker. It has a patch viewer (view patches that you have attached to > bugs): > > http://www.bugzilla.org/docs/2.18/html/patchviewer.html > > > > So as far as I can see from the test pages we've had so far, that means > > creating a "bug" or some other "object" for the patch, with cases where > the > > patch actually relates to an already listed bug, and cases where the > object > > would have to be created specifically for it (as in the above case). > > > > If we finally use Bugzilla, is the above a good idea, or are entries on a > Wiki > > page better? Those would presumably require the submitter to actually post > > a short initial message to -devel (patch attached, details of what it does > on > > the Wiki). > > > > But maybe protocol would require a short message to -devel anyway, > > even in the case of a "patch tracker"? > > > > Comments? > > > > > > > > Gale > > > > > > > > > Ed Musgrove wrote: > > > > After release of "stable" I propose to make the prefs panel user > > > > resizable (restrained only by valid screen size) and the keyboard > > > > panel columns automatically size themselves (I have the code > > > > completely finished) just like the mouse prefs panel is. This will > > > > resolve most if not all such issues. Vaguely related, I gave Gale > > > > working code which makes the Help/About... panel user resizable. (it > > > > is a trivial one line change). BTW, is there a problem or reason why > that > > was never committed (patch attached)? > > > > > > > > --Ed > > > > > > > > > > > >> -----Original Message----- > > > >> From: Gale Andrews [mailto:[hidden email]] > > > >> Sent: Sunday, October 25, 2009 7:53 PM > > > >> To: [hidden email] > > > >> Subject: Re: [Audacity-devel] Beta_Feedback > > > >> > > > >> > > > >> | From "Ed Musgrove" <[hidden email]> To > > > >> | <[hidden email]> > > > >> | Subject [Audacity-devel] Beta_Feedback > > > >>> Is it possible that the recent commit to fr.po caused this: > > > >>> > > > >>> Update of /cvsroot/audacity/htdocs/locale In directory > > > >>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > > > >>> > > > >>> Modified Files: > > > >>> fr.po > > > >>> Log Message: > > > >>> Updated web site translation from Olivier Humbert > > > >> No, that is the translation for the web site, not the .po file for > > > >> the > > > > software. > > > >> See below. > > > >> > > > >> > > > >> | From "Ed Musgrove" <[hidden email]> Sun, 25 Oct > > 2009 > > > >> | 09:52:08 -0700 > > > >> | Subject: [Audacity-devel] Beta_Feedback > > > >>> Note that the problem is with width. Note that the Audacity > > > >>> "system informations" is printed in French. > > > >>> > > > >>> I carefully went through both (after having just downloaded the > > > >>> current > > > >> CVS > > > >>> head): > > > >>> audacity\src\prefs\PrefsDialog.cpp > > > >>> audacity\src\prefs\KeyConfigPrefs.cpp > > > >>> To ensure that none of the things I have played with recently were > > > >>> inadvertently committed -- they were not. > > > >>> > > > >>> Recently Gale made some changes to the text. I think that this > > > >>> dialogue initially sizes itself based on the width of the longest > > > >>> text string; > > > > could > > > >>> this be a translation issue? > > > >> If the problem is specific to running Audacity in French, using the > > > >> .mo file compiled from fr.po, then no, because my string changes > > > >> have not yet had a French translation committed. > > > >> > > > >> Using a Unicode Release build from CVS a few days ago on Ubuntu > > > >> 9.04 (so using the current fr.po file) the longer text seems to > > > >> wrap round correctly. The preferences dialogue could in fact still > > > >> be expanded a little horizontally to the full 800px width. > > > >> > > > >> > > > >> > > > >>> If possible, I would like to have the reporter comment out that > > > >>> line so > > > > that > > > >>> the dialog will open without entering the debugger, then, send me > > > >>> a screenshot of the mouse panel, key binding panel and the > > > >>> directories > > > >> panel. > > > >>> Je parle un peut de Francais. (But my spelling and grammar are > > > > atrocious.) > > > >> Ed, I've sent you the e-mail address of the person privately, so > > > >> feel free > > > > to > > > >> contact them off-list for more information (but don't overdo it if > > > >> he isn't keen to go to a lot of trouble). :=) > > > >> > > > >> > > > >> > > > >> Thanks > > > >> > > > >> > > > >> > > > >> Gale > > > >> > > > >> > > > >> > > > >> > > > >>>> -----Original Message----- > > > >>>> From: Gale Andrews [mailto:[hidden email]] > > > >>>> Sent: Sunday, October 25, 2009 1:28 AM > > > >>>> To: Laurent Epinat > > > >>>> Cc: [hidden email]; > > > >>>> [hidden email] > > > >>>> Subject: Re: [Audacity-devel] Beta_Feedback > > > >>>> > > > >>>> > > > >>>> Thank you, I have forwarded this message to our developers' > > > >>>> mailing list. > > > >>>> > > > >>>> > > > >>>> > > > >>>> Gale > > > >>>> Audacity Team > > > >>>> > > > >>>> > > > >>>> | From Laurent Epinat > > > >>>> | Sat, 24 Oct 2009 10:34:26 +0200 > > > >>>> | Subject: Beta_Feedback > > > >>>>> Just for information, I recompile the beta 1.3.9 version on > > > >>>>> AMD64 > > > >>>>> > > > >>>>> and I have an assert when I open the preference dialog box at > > > >>>>> the src/prefs/PrefsDialog.cpp line 136 : > > > >>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences > > dialog > > > >>>>> exceeds max size")); > > > >>>>> > > > >>>>> I add trace on the size and my dialog had > > > >>>>> sz.x=857 sz.y=382 > > > >>>>> > > > >>>>> > > > >>>>> My screen resolution is 1920x1200 I you need more information > > > >>>>> ... > > > >>>>> > > > >>>>> > > > >>>>> Congratulation for the really good software > > > >>>>> > > > >>>>> > > > >>>>> Here the system informations > > > >>>>> > > > >>>>> Informations système > > > >>>>> Support de format de fichier > > > >>>>> libmad (Importation de MP3) Activé > > > >>>>> libvorbis (Import et Export Ogg Vorbis ) Activé > > > >>>>> libid3tag (support des tag ID3) Activé > > > >>>>> libflac (Import et Export FLAC) Activé > > > >>>>> libtwolame (export MP2) Désactivé > > > >>>>> QuickTime (Importer depuis QuickTime) Désactivé > > > >>>>> > > > >>>>> > > > >>>>> Librairies > > > >>>>> libresample > > > >>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio > > > > (Lecture > > > >>>>> et enregistrement audio) > > > >>>>> v19 > > > >>>>> wxWidgets 2.8.10 > > > >>>>> (Unicode) > > > >>>>> > > > >>>>> Fonctions > > > >>>>> Nyquist (Support de modules (plugins)) > Activé > > > >>>>> LADSPA (Support de modules (plugins)) > Activé > > > >>>>> Vamp (Support de modules (plugins)) Activé > > > >>>>> Audio Units (Support de modules (plugins)) Désactivé > > > >>>>> PortMixer (Support du mixage de la carte son) Activé > > > >>>>> SoundTouch (Support du changement de hauteur et de tempo) > > > >>>> Désactivé > > > >>>>> Informations système > > > >>>>> Date de création du programme : Oct 18 2009 > > > >>>>> Type de version : Debug build > > > >>>>> Préfixe d'intallation /usr/local/ > > > >>>>> Répertoire des réglages : /home/laurent/.audacity-data > > > >> > > > >> > > > >> > > > >> > > > > -------------------------------------------------------------------- > > > > -------- > > > > -- > > > >> Come build with us! The BlackBerry(R) Developer Conference in SF, > > > >> CA is the only developer event you need to attend this year. > > > >> Jumpstart your developing skills, take BlackBerry mobile > > > >> applications to market and stay ahead of the curve. Join us from > > November 9 - 12, 2009. Register now! > > > >> http://p.sf.net/sfu/devconference > > > >> _______________________________________________ > > > >> audacity-devel mailing list > > > >> [hidden email] > > > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > >> > > > >> ------------------------------------------------------------------- > > > >> ----- > > > >> > > > >> ------------------------------------------------------------------- > > > >> ----------- Come build with us! The BlackBerry(R) Developer > > > >> Conference in SF, CA is the only developer event you need to attend > > > >> this year. Jumpstart your developing skills, take BlackBerry mobile > > > >> applications to market and stay ahead of the curve. Join us from > > > >> November 9 - 12, 2009. Register now! > > > >> http://p.sf.net/sfu/devconference > > > >> > > > >> ------------------------------------------------------------------- > > > >> ----- > > > >> > > > >> _______________________________________________ > > > >> audacity-devel mailing list > > > >> [hidden email] > > > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > ---------------------------------------------------------------------- > > > -------- Come build with us! The BlackBerry(R) Developer Conference in > > > SF, CA is the only developer event you need to attend this year. > > > Jumpstart your developing skills, take BlackBerry mobile applications > > > to market and stay ahead of the curve. Join us from November 9 - 12, > > > 2009. Register now! > > > http://p.sf.net/sfu/devconference > > > _______________________________________________ > > > audacity-devel mailing list > > > [hidden email] > > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > > > > ---------------------------------------------------------------------------- > -- > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is > the > > only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > audacity-devel mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Vaughan Johnson
|
In reply to this post
by Ed Musgrove-2
Hi, Ed. Are you familiar with the concept of trolling? I think so. :-)
Ed Musgrove wrote: > Is Audacity a professionally developed product? Yes. > Is it just something that a > few people have thrown together in their spare time? "Thrown" is inaccurate, but yes, some professional people did this in their spare time. > Do we expect Audacity > to be used primarily by those capable of compiling and understanding the > source code, or are the vast majority of users audiophiles who have no > desire nor ability to compile the code? The latter of course. But I don't think they care about the About box being resizeable either. > Can the venerable Audacity mentors > who are more focused on major problems accept the enthusiast coder who > might be more comfortable starting out dealing with the little things? Depends on the bandwidth the noob requires. > > Any change in the code should be documented. If it is a trivial change made > by a longtime developer a comment with initials and the date next to the > change might be sufficient. We don't do it that way. We add CVS comments when we commit, rather than clutter the code with the whole history of changes. These CVS comments become part of the history log of that file. There's also the CVS annotate feature for seeing who did what to what code when. > Anything which changes the user's experience > should be formally proposed, discussed and the code peer-reviewed with alpha > testing by at least one developer on each major platform. You may assert that, but doing so will not change the existing culture. That's not the way we do things. This is a group of volunteers, not a hierarchical, formalistic organization. We simply don't have the resources for all that officious procedure. But we do try to approximate the same results with the resources we have. > > I think we need a category of bug like "feature request". A feature request is different from a bug. As Gale pointed out, we have the wiki page for that. - V === > That way something > sent to @feedback can be triaged by venerable developers into this category > when appropriate. Recognized developers and hackers (like me) may also > propose a "feature request" bug; someone with authorization on the bug list > would need to actually enter it. > > > --Ed > > >> -----Original Message----- >> From: Gale Andrews [mailto:[hidden email]] >> Sent: Friday, October 30, 2009 9:14 PM >> To: [hidden email] >> Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback >> >> >> | From Martyn Shaw <[hidden email]> Sat, 31 Oct 2009 >> | 00:39:14 +0000 >> | Subject: [Audacity-devel] Beta_Feedback >>> ... I see no reason (on my platform), or any philosophical reason why >>> the 'about' box shouldn't be resizable, and so I committed it (others >>> may chose to revert). >>> >>> Just the sort of patch that is distracting us (me) from 2.0. It >>> should have gone into a patch-tracker of some sort, commented on by >>> people who tried it but maybe aren't 'committers', and not come up on >>> -devel until later. This isn't a criticism of you or what you've >>> done, but of the limited system that we have right now. I'm hoping >>> that Bugzilla and it's protocols may help with this type of >>> developer-bandwidth problem. >> Bugzilla does not from my admittedly limited knowledge have a patch >> tracker. It has a patch viewer (view patches that you have attached to > bugs): >> http://www.bugzilla.org/docs/2.18/html/patchviewer.html >> >> So as far as I can see from the test pages we've had so far, that means >> creating a "bug" or some other "object" for the patch, with cases where > the >> patch actually relates to an already listed bug, and cases where the > object >> would have to be created specifically for it (as in the above case). >> >> If we finally use Bugzilla, is the above a good idea, or are entries on a > Wiki >> page better? Those would presumably require the submitter to actually post >> a short initial message to -devel (patch attached, details of what it does > on >> the Wiki). >> >> But maybe protocol would require a short message to -devel anyway, >> even in the case of a "patch tracker"? >> >> Comments? >> >> >> >> Gale >> >> >> >>> Ed Musgrove wrote: >>>> After release of "stable" I propose to make the prefs panel user >>>> resizable (restrained only by valid screen size) and the keyboard >>>> panel columns automatically size themselves (I have the code >>>> completely finished) just like the mouse prefs panel is. This will >>>> resolve most if not all such issues. Vaguely related, I gave Gale >>>> working code which makes the Help/About... panel user resizable. (it >>>> is a trivial one line change). BTW, is there a problem or reason why > that >> was never committed (patch attached)? >>>> --Ed >>>> >>>> >>>>> -----Original Message----- >>>>> From: Gale Andrews [mailto:[hidden email]] >>>>> Sent: Sunday, October 25, 2009 7:53 PM >>>>> To: [hidden email] >>>>> Subject: Re: [Audacity-devel] Beta_Feedback >>>>> >>>>> >>>>> | From "Ed Musgrove" <[hidden email]> To >>>>> | <[hidden email]> >>>>> | Subject [Audacity-devel] Beta_Feedback >>>>>> Is it possible that the recent commit to fr.po caused this: >>>>>> >>>>>> Update of /cvsroot/audacity/htdocs/locale In directory >>>>>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 >>>>>> >>>>>> Modified Files: >>>>>> fr.po >>>>>> Log Message: >>>>>> Updated web site translation from Olivier Humbert >>>>> No, that is the translation for the web site, not the .po file for >>>>> the >>>> software. >>>>> See below. >>>>> >>>>> >>>>> | From "Ed Musgrove" <[hidden email]> Sun, 25 Oct >> 2009 >>>>> | 09:52:08 -0700 >>>>> | Subject: [Audacity-devel] Beta_Feedback >>>>>> Note that the problem is with width. Note that the Audacity >>>>>> "system informations" is printed in French. >>>>>> >>>>>> I carefully went through both (after having just downloaded the >>>>>> current >>>>> CVS >>>>>> head): >>>>>> audacity\src\prefs\PrefsDialog.cpp >>>>>> audacity\src\prefs\KeyConfigPrefs.cpp >>>>>> To ensure that none of the things I have played with recently were >>>>>> inadvertently committed -- they were not. >>>>>> >>>>>> Recently Gale made some changes to the text. I think that this >>>>>> dialogue initially sizes itself based on the width of the longest >>>>>> text string; >>>> could >>>>>> this be a translation issue? >>>>> If the problem is specific to running Audacity in French, using the >>>>> .mo file compiled from fr.po, then no, because my string changes >>>>> have not yet had a French translation committed. >>>>> >>>>> Using a Unicode Release build from CVS a few days ago on Ubuntu >>>>> 9.04 (so using the current fr.po file) the longer text seems to >>>>> wrap round correctly. The preferences dialogue could in fact still >>>>> be expanded a little horizontally to the full 800px width. >>>>> >>>>> >>>>> >>>>>> If possible, I would like to have the reporter comment out that >>>>>> line so >>>> that >>>>>> the dialog will open without entering the debugger, then, send me >>>>>> a screenshot of the mouse panel, key binding panel and the >>>>>> directories >>>>> panel. >>>>>> Je parle un peut de Francais. (But my spelling and grammar are >>>> atrocious.) >>>>> Ed, I've sent you the e-mail address of the person privately, so >>>>> feel free >>>> to >>>>> contact them off-list for more information (but don't overdo it if >>>>> he isn't keen to go to a lot of trouble). :=) >>>>> >>>>> >>>>> >>>>> Thanks >>>>> >>>>> >>>>> >>>>> Gale >>>>> >>>>> >>>>> >>>>> >>>>>>> -----Original Message----- >>>>>>> From: Gale Andrews [mailto:[hidden email]] >>>>>>> Sent: Sunday, October 25, 2009 1:28 AM >>>>>>> To: Laurent Epinat >>>>>>> Cc: [hidden email]; >>>>>>> [hidden email] >>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback >>>>>>> >>>>>>> >>>>>>> Thank you, I have forwarded this message to our developers' >>>>>>> mailing list. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Gale >>>>>>> Audacity Team >>>>>>> >>>>>>> >>>>>>> | From Laurent Epinat >>>>>>> | Sat, 24 Oct 2009 10:34:26 +0200 >>>>>>> | Subject: Beta_Feedback >>>>>>>> Just for information, I recompile the beta 1.3.9 version on >>>>>>>> AMD64 >>>>>>>> >>>>>>>> and I have an assert when I open the preference dialog box at >>>>>>>> the src/prefs/PrefsDialog.cpp line 136 : >>>>>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences >> dialog >>>>>>>> exceeds max size")); >>>>>>>> >>>>>>>> I add trace on the size and my dialog had >>>>>>>> sz.x=857 sz.y=382 >>>>>>>> >>>>>>>> >>>>>>>> My screen resolution is 1920x1200 I you need more information >>>>>>>> ... >>>>>>>> >>>>>>>> >>>>>>>> Congratulation for the really good software >>>>>>>> >>>>>>>> >>>>>>>> Here the system informations >>>>>>>> >>>>>>>> Informations système >>>>>>>> Support de format de fichier >>>>>>>> libmad (Importation de MP3) Activé >>>>>>>> libvorbis (Import et Export Ogg Vorbis ) Activé >>>>>>>> libid3tag (support des tag ID3) Activé >>>>>>>> libflac (Import et Export FLAC) Activé >>>>>>>> libtwolame (export MP2) Désactivé >>>>>>>> QuickTime (Importer depuis QuickTime) Désactivé >>>>>>>> >>>>>>>> >>>>>>>> Librairies >>>>>>>> libresample >>>>>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio >>>> (Lecture >>>>>>>> et enregistrement audio) >>>>>>>> v19 >>>>>>>> wxWidgets 2.8.10 >>>>>>>> (Unicode) >>>>>>>> >>>>>>>> Fonctions >>>>>>>> Nyquist (Support de modules (plugins)) > Activé >>>>>>>> LADSPA (Support de modules (plugins)) > Activé >>>>>>>> Vamp (Support de modules (plugins)) Activé >>>>>>>> Audio Units (Support de modules (plugins)) Désactivé >>>>>>>> PortMixer (Support du mixage de la carte son) Activé >>>>>>>> SoundTouch (Support du changement de hauteur et de tempo) >>>>>>> Désactivé >>>>>>>> Informations système >>>>>>>> Date de création du programme : Oct 18 2009 >>>>>>>> Type de version : Debug build >>>>>>>> Préfixe d'intallation /usr/local/ >>>>>>>> Répertoire des réglages : /home/laurent/.audacity-data >>>>> >>>>> >>>>> >>>> -------------------------------------------------------------------- >>>> -------- >>>> -- >>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, >>>>> CA is the only developer event you need to attend this year. >>>>> Jumpstart your developing skills, take BlackBerry mobile >>>>> applications to market and stay ahead of the curve. Join us from >> November 9 - 12, 2009. Register now! >>>>> http://p.sf.net/sfu/devconference >>>>> _______________________________________________ >>>>> audacity-devel mailing list >>>>> [hidden email] >>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>>>> >>>>> ------------------------------------------------------------------- >>>>> ----- >>>>> >>>>> ------------------------------------------------------------------- >>>>> ----------- Come build with us! The BlackBerry(R) Developer >>>>> Conference in SF, CA is the only developer event you need to attend >>>>> this year. Jumpstart your developing skills, take BlackBerry mobile >>>>> applications to market and stay ahead of the curve. Join us from >>>>> November 9 - 12, 2009. Register now! >>>>> http://p.sf.net/sfu/devconference >>>>> >>>>> ------------------------------------------------------------------- >>>>> ----- >>>>> >>>>> _______________________________________________ >>>>> audacity-devel mailing list >>>>> [hidden email] >>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> ---------------------------------------------------------------------- >>> -------- Come build with us! The BlackBerry(R) Developer Conference in >>> SF, CA is the only developer event you need to attend this year. >>> Jumpstart your developing skills, take BlackBerry mobile applications >>> to market and stay ahead of the curve. Join us from November 9 - 12, >>> 2009. Register now! >>> http://p.sf.net/sfu/devconference >>> _______________________________________________ >>> audacity-devel mailing list >>> [hidden email] >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> >> >> > ---------------------------------------------------------------------------- > -- >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA is > the >> only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
In reply to this post
by Gale (Audacity Team)
I think what you said is pretty much what I said:
"enhancement" == "feature request" "a developer" == " venerable Audacity mentor" " (or more loosely, active contributors to this list)" == "hackers (like me)" To get from http://wiki.audacityteam.org/index.php?title=Feature_Requests to a "formal enhancement" requires intervention by an Audacity PTB. As for storing non-committed patches, I do not think it a good idea. Any patch proposed by ANYONE active on the dev-list should be first attached (zipped if large) to a dev-list message. This leaves it open for peer review and automatically stores it online at Source Forge (though the interface is not good for locating old attachments). Those not on the dev-list should attach a (zipped--neither .patch nor .txt files are allowed) file to a post on http://wiki.audacityteam.org/index.php?title=Feature_Requests. --Ed > -----Original Message----- > From: Gale Andrews [mailto:[hidden email]] > Sent: Saturday, October 31, 2009 1:18 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > | From "Ed Musgrove" <[hidden email]> Fri, 30 Oct 2009 > | 21:54:03 -0700 > | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > Is Audacity a professionally developed product? Is it just something > > that a few people have thrown together in their spare time? Do we > > expect Audacity to be used primarily by those capable of compiling and > > understanding the source code, or are the vast majority of users > > audiophiles who have no desire nor ability to compile the code? Can > > the venerable Audacity mentors who are more focused on major problems > > accept the enthusiast coder who might be more comfortable starting out > dealing with the little things? > > > > Any change in the code should be documented. If it is a trivial change > > made by a longtime developer a comment with initials and the date next > > to the change might be sufficient. Anything which changes the user's > > experience should be formally proposed, discussed and the code > > peer-reviewed with alpha testing by at least one developer on each major > platform. > > > > I think we need a category of bug like "feature request". That way > > something sent to @feedback can be triaged by venerable developers > > into this category when appropriate. Recognized developers and hackers > > (like me) may also propose a "feature request" bug; someone with > > authorization on the bug list would need to actually enter it. > > We've pretty much agreed as far as I understand it that "enhancements" > tracked in Bugzilla or whatever system we use should only be those > supported by a developer (or more loosely, active contributors to this > > User requests sent to feedback@ will continue to be processed on: > http://wiki.audacityteam.org/index.php?title=Feature_Requests > > We can take valuable/strongly voted for items from that page at any time > and turn it into a "developer supported" enhancement. > > The point of my question was whether we want to load a formal bug tracker > with what may be relatively trivial "enhancement" patches by creating a new > item just to hold that patch; or store patches (or links to > them) otherwise. > > Obviously if we use Bugzilla we can attach a patch to an actual P1- P5 bug (or > if Checklist remains in the short/medium term, a link to the patch). A patch > like that isn't likely to drop out of sight. > > I think the problem is more the large number of patches for > "enhancements", some of which may come from someone completely new > to the list, so they couldn't be described as "developer supported" in the > sense of the enhancements I was thinking of storing in the bug tracker > (where the case > for them has already been largely agreed). > > > > Gale > > > > > > -----Original Message----- > > > From: Gale Andrews [mailto:[hidden email]] > > > Sent: Friday, October 30, 2009 9:14 PM > > > To: [hidden email] > > > Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > > > > > > > | From Martyn Shaw <[hidden email]> Sat, 31 Oct 2009 > > > | 00:39:14 +0000 > > > | Subject: [Audacity-devel] Beta_Feedback > > > >... I see no reason (on my platform), or any philosophical reason > > > >why the 'about' box shouldn't be resizable, and so I committed it > > > >(others may chose to revert). > > > > > > > > Just the sort of patch that is distracting us (me) from 2.0. It > > > > should have gone into a patch-tracker of some sort, commented on > > > > by people who tried it but maybe aren't 'committers', and not come > > > > up on -devel until later. This isn't a criticism of you or what > > > > you've done, but of the limited system that we have right now. > > > > I'm hoping that Bugzilla and it's protocols may help with this > > > > type of developer-bandwidth problem. > > > > > > Bugzilla does not from my admittedly limited knowledge have a patch > > > tracker. It has a patch viewer (view patches that you have attached > > > to > > bugs): > > > http://www.bugzilla.org/docs/2.18/html/patchviewer.html > > > > > > So as far as I can see from the test pages we've had so far, that > > > means creating a "bug" or some other "object" for the patch, with > > > cases where > > the > > > patch actually relates to an already listed bug, and cases where the > > object > > > would have to be created specifically for it (as in the above case). > > > > > > If we finally use Bugzilla, is the above a good idea, or are entries > > > on a > > Wiki > > > page better? Those would presumably require the submitter to > > > actually post a short initial message to -devel (patch attached, > > > details of what it does > > on > > > the Wiki). > > > > > > But maybe protocol would require a short message to -devel anyway, > > > even in the case of a "patch tracker"? > > > > > > Comments? > > > > > > > > > > > > Gale > > > > > > > > > > > > > Ed Musgrove wrote: > > > > > After release of "stable" I propose to make the prefs panel user > > > > > resizable (restrained only by valid screen size) and the > > > > > keyboard panel columns automatically size themselves (I have the > > > > > code completely finished) just like the mouse prefs panel is. > > > > > This will resolve most if not all such issues. Vaguely related, > > > > > I gave Gale working code which makes the Help/About... panel > > > > > user resizable. (it is a trivial one line change). BTW, is there > > > > > a problem or reason why > > that > > > was never committed (patch attached)? > > > > > > > > > > --Ed > > > > > > > > > > > > > > >> -----Original Message----- > > > > >> From: Gale Andrews [mailto:[hidden email]] > > > > >> Sent: Sunday, October 25, 2009 7:53 PM > > > > >> To: [hidden email] > > > > >> Subject: Re: [Audacity-devel] Beta_Feedback > > > > >> > > > > >> > > > > >> | From "Ed Musgrove" <[hidden email]> To > > > > >> | <[hidden email]> > > > > >> | Subject [Audacity-devel] Beta_Feedback > > > > >>> Is it possible that the recent commit to fr.po caused this: > > > > >>> > > > > >>> Update of /cvsroot/audacity/htdocs/locale In directory > > > > >>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > > > > >>> > > > > >>> Modified Files: > > > > >>> fr.po > > > > >>> Log Message: > > > > >>> Updated web site translation from Olivier Humbert > > > > >> No, that is the translation for the web site, not the .po file > > > > >> for the > > > > > software. > > > > >> See below. > > > > >> > > > > >> > > > > >> | From "Ed Musgrove" <[hidden email]> Sun, 25 > Oct > > > 2009 > > > > >> | 09:52:08 -0700 > > > > >> | Subject: [Audacity-devel] Beta_Feedback > > > > >>> Note that the problem is with width. Note that the Audacity > > > > >>> "system informations" is printed in French. > > > > >>> > > > > >>> I carefully went through both (after having just downloaded > > > > >>> the current > > > > >> CVS > > > > >>> head): > > > > >>> audacity\src\prefs\PrefsDialog.cpp > > > > >>> audacity\src\prefs\KeyConfigPrefs.cpp > > > > >>> To ensure that none of the things I have played with recently > > > > >>> were inadvertently committed -- they were not. > > > > >>> > > > > >>> Recently Gale made some changes to the text. I think that this > > > > >>> dialogue initially sizes itself based on the width of the > > > > >>> longest text string; > > > > > could > > > > >>> this be a translation issue? > > > > >> If the problem is specific to running Audacity in French, using > > > > >> the .mo file compiled from fr.po, then no, because my string > > > > >> changes have not yet had a French translation committed. > > > > >> > > > > >> Using a Unicode Release build from CVS a few days ago on Ubuntu > > > > >> 9.04 (so using the current fr.po file) the longer text seems to > > > > >> wrap round correctly. The preferences dialogue could in fact > > > > >> still be expanded a little horizontally to the full 800px width. > > > > >> > > > > >> > > > > >> > > > > >>> If possible, I would like to have the reporter comment out > > > > >>> that line so > > > > > that > > > > >>> the dialog will open without entering the debugger, then, send > > > > >>> me a screenshot of the mouse panel, key binding panel and the > > > > >>> directories > > > > >> panel. > > > > >>> Je parle un peut de Francais. (But my spelling and grammar are > > > > > atrocious.) > > > > >> Ed, I've sent you the e-mail address of the person privately, > > > > >> so feel free > > > > > to > > > > >> contact them off-list for more information (but don't overdo it > > > > >> if he isn't keen to go to a lot of trouble). :=) > > > > >> > > > > >> > > > > >> > > > > >> Thanks > > > > >> > > > > >> > > > > >> > > > > >> Gale > > > > >> > > > > >> > > > > >> > > > > >> > > > > >>>> -----Original Message----- > > > > >>>> From: Gale Andrews [mailto:[hidden email]] > > > > >>>> Sent: Sunday, October 25, 2009 1:28 AM > > > > >>>> To: Laurent Epinat > > > > >>>> Cc: [hidden email]; > > > > >>>> [hidden email] > > > > >>>> Subject: Re: [Audacity-devel] Beta_Feedback > > > > >>>> > > > > >>>> > > > > >>>> Thank you, I have forwarded this message to our developers' > > > > >>>> mailing list. > > > > >>>> > > > > >>>> > > > > >>>> > > > > >>>> Gale > > > > >>>> Audacity Team > > > > >>>> > > > > >>>> > > > > >>>> | From Laurent Epinat > > > > >>>> | Sat, 24 Oct 2009 10:34:26 +0200 > > > > >>>> | Subject: Beta_Feedback > > > > >>>>> Just for information, I recompile the beta 1.3.9 version on > > > > >>>>> AMD64 > > > > >>>>> > > > > >>>>> and I have an assert when I open the preference dialog box > > > > >>>>> at the src/prefs/PrefsDialog.cpp line 136 : > > > > >>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences > > > dialog > > > > >>>>> exceeds max size")); > > > > >>>>> > > > > >>>>> I add trace on the size and my dialog had > > > > >>>>> sz.x=857 sz.y=382 > > > > >>>>> > > > > >>>>> > > > > >>>>> My screen resolution is 1920x1200 I you need more > > > > >>>>> information ... > > > > >>>>> > > > > >>>>> > > > > >>>>> Congratulation for the really good software > > > > >>>>> > > > > >>>>> > > > > >>>>> Here the system informations > > > > >>>>> > > > > >>>>> Informations système > > > > >>>>> Support de format de fichier > > > > >>>>> libmad (Importation de MP3) Activé > > > > >>>>> libvorbis (Import et Export Ogg Vorbis ) Activé > > > > >>>>> libid3tag (support des tag ID3) Activé > > > > >>>>> libflac (Import et Export FLAC) Activé > > > > >>>>> libtwolame (export MP2) Désactivé > > > > >>>>> QuickTime (Importer depuis QuickTime) Désactivé > > > > >>>>> > > > > >>>>> > > > > >>>>> Librairies > > > > >>>>> libresample > > > > >>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio > > > > > (Lecture > > > > >>>>> et enregistrement audio) > > > > >>>>> v19 > > > > >>>>> wxWidgets 2.8.10 > > > > >>>>> (Unicode) > > > > >>>>> > > > > >>>>> Fonctions > > > > >>>>> Nyquist (Support de modules (plugins)) > > Activé > > > > >>>>> LADSPA (Support de modules (plugins)) > > Activé > > > > >>>>> Vamp (Support de modules (plugins)) > > > > >>>>> Audio Units (Support de modules (plugins)) > Désactivé > > > > >>>>> PortMixer (Support du mixage de la carte son) Activé > > > > >>>>> SoundTouch (Support du changement de hauteur et de > tempo) > > > > >>>> Désactivé > > > > >>>>> Informations système > > > > >>>>> Date de création du programme : Oct 18 2009 > > > > >>>>> Type de version : Debug build > > > > >>>>> Préfixe d'intallation /usr/local/ > > > > >>>>> Répertoire des réglages : /home/laurent/.audacity-data > > > > >> > > > > >> > > > > >> > > > > >> > > > > > ---------------------------------------------------------------- > > > > > ---- > > > > > -------- > > > > > -- > > > > >> Come build with us! The BlackBerry(R) Developer Conference in > > > > >> SF, CA is the only developer event you need to attend this year. > > > > >> Jumpstart your developing skills, take BlackBerry mobile > > > > >> applications to market and stay ahead of the curve. Join us > > > > >> from > > > November 9 - 12, 2009. Register now! > > > > >> http://p.sf.net/sfu/devconference > > > > >> _______________________________________________ > > > > >> audacity-devel mailing list > > > > >> [hidden email] > > > > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > >> > > > > >> --------------------------------------------------------------- > > > > >> ---- > > > > >> ----- > > > > >> > > > > >> --------------------------------------------------------------- > > > > >> ---- > > > > >> ----------- Come build with us! The BlackBerry(R) Developer > > > > >> Conference in SF, CA is the only developer event you need to > > > > >> attend this year. Jumpstart your developing skills, take > > > > >> BlackBerry mobile applications to market and stay ahead of the > > > > >> curve. Join us from November 9 - 12, 2009. Register now! > > > > >> http://p.sf.net/sfu/devconference > > > > >> > > > > >> --------------------------------------------------------------- > > > > >> ---- > > > > >> ----- > > > > >> > > > > >> _______________________________________________ > > > > >> audacity-devel mailing list > > > > >> [hidden email] > > > > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > > > ------------------------------------------------------------------ > > > > ---- > > > > -------- Come build with us! The BlackBerry(R) Developer > > > > Conference in SF, CA is the only developer event you need to attend > this year. > > > > Jumpstart your developing skills, take BlackBerry mobile > > > > applications to market and stay ahead of the curve. Join us from > > > > November 9 - 12, 2009. Register now! > > > > http://p.sf.net/sfu/devconference > > > > _______________________________________________ > > > > audacity-devel mailing list > > > > [hidden email] > > > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > ------ > > -- > > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > > is > > the > > > only developer event you need to attend this year. Jumpstart your > > > developing skills, take BlackBerry mobile applications to market and > > > stay ahead of the curve. Join us from November 9 - 12, 2009. Register > now! > > > http://p.sf.net/sfu/devconference > > > _______________________________________________ > > > audacity-devel mailing list > > > [hidden email] > > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > ---------------------------------------------------------------------- > > -------- Come build with us! The BlackBerry(R) Developer Conference in > > SF, CA is the only developer event you need to attend this year. > > Jumpstart your developing skills, take BlackBerry mobile applications > > to market and stay ahead of the curve. Join us from November 9 - 12, > > 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > audacity-devel mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the > only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
In reply to this post
by Vaughan Johnson
Sorry--was not really "trolling" just trying to get us to think of the
extremes. My apology if anyone took offense. --Ed > -----Original Message----- > From: Vaughan Johnson [mailto:[hidden email]] > Sent: Saturday, October 31, 2009 2:58 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > Hi, Ed. Are you familiar with the concept of trolling? I think so. :-) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Martyn Shaw-2
|
In reply to this post
by Ed Musgrove-2
Ed Musgrove wrote: > I think what you said is pretty much what I said: > "enhancement" == "feature request" > "a developer" == " venerable Audacity mentor" > " (or more loosely, active contributors to this list)" == "hackers (like > me)" > To get from http://wiki.audacityteam.org/index.php?title=Feature_Requests > to a "formal enhancement" requires intervention by an Audacity PTB. > > As for storing non-committed patches, I do not think it a good idea. They should be kept somewhere, in case we want to look at them. Any > patch proposed by ANYONE active on the dev-list should be first attached > (zipped if large) to a dev-list message. This leaves it open for peer review > and automatically stores it online at Source Forge (though the interface is > not good for locating old attachments). That is part of the problem, yes. Those not on the dev-list should > attach a (zipped--neither .patch nor .txt files are allowed) file to a post > on http://wiki.audacityteam.org/index.php?title=Feature_Requests. That would be a good idea. How does that work? I am not very good editing wikis. Martyn > --Ed > > >> -----Original Message----- >> From: Gale Andrews [mailto:[hidden email]] >> Sent: Saturday, October 31, 2009 1:18 PM >> To: [hidden email] >> Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback >> >> >> | From "Ed Musgrove" <[hidden email]> Fri, 30 Oct 2009 >> | 21:54:03 -0700 >> | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback >>> Is Audacity a professionally developed product? Is it just something >>> that a few people have thrown together in their spare time? Do we >>> expect Audacity to be used primarily by those capable of compiling and >>> understanding the source code, or are the vast majority of users >>> audiophiles who have no desire nor ability to compile the code? Can >>> the venerable Audacity mentors who are more focused on major problems >>> accept the enthusiast coder who might be more comfortable starting out >> dealing with the little things? >>> Any change in the code should be documented. If it is a trivial change >>> made by a longtime developer a comment with initials and the date next >>> to the change might be sufficient. Anything which changes the user's >>> experience should be formally proposed, discussed and the code >>> peer-reviewed with alpha testing by at least one developer on each major >> platform. >>> I think we need a category of bug like "feature request". That way >>> something sent to @feedback can be triaged by venerable developers >>> into this category when appropriate. Recognized developers and hackers >>> (like me) may also propose a "feature request" bug; someone with >>> authorization on the bug list would need to actually enter it. >> We've pretty much agreed as far as I understand it that "enhancements" >> tracked in Bugzilla or whatever system we use should only be those >> supported by a developer (or more loosely, active contributors to this > list). >> User requests sent to feedback@ will continue to be processed on: >> http://wiki.audacityteam.org/index.php?title=Feature_Requests >> >> We can take valuable/strongly voted for items from that page at any time >> and turn it into a "developer supported" enhancement. >> >> The point of my question was whether we want to load a formal bug tracker >> with what may be relatively trivial "enhancement" patches by creating a > new >> item just to hold that patch; or store patches (or links to >> them) otherwise. >> >> Obviously if we use Bugzilla we can attach a patch to an actual P1- P5 bug > (or >> if Checklist remains in the short/medium term, a link to the patch). A > patch >> like that isn't likely to drop out of sight. >> >> I think the problem is more the large number of patches for >> "enhancements", some of which may come from someone completely new >> to the list, so they couldn't be described as "developer supported" in the >> sense of the enhancements I was thinking of storing in the bug tracker >> (where the case >> for them has already been largely agreed). >> >> >> >> Gale >> >> >> >>>> -----Original Message----- >>>> From: Gale Andrews [mailto:[hidden email]] >>>> Sent: Friday, October 30, 2009 9:14 PM >>>> To: [hidden email] >>>> Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback >>>> >>>> >>>> | From Martyn Shaw <[hidden email]> Sat, 31 Oct 2009 >>>> | 00:39:14 +0000 >>>> | Subject: [Audacity-devel] Beta_Feedback >>>>> ... I see no reason (on my platform), or any philosophical reason >>>>> why the 'about' box shouldn't be resizable, and so I committed it >>>>> (others may chose to revert). >>>>> >>>>> Just the sort of patch that is distracting us (me) from 2.0. It >>>>> should have gone into a patch-tracker of some sort, commented on >>>>> by people who tried it but maybe aren't 'committers', and not come >>>>> up on -devel until later. This isn't a criticism of you or what >>>>> you've done, but of the limited system that we have right now. >>>>> I'm hoping that Bugzilla and it's protocols may help with this >>>>> type of developer-bandwidth problem. >>>> Bugzilla does not from my admittedly limited knowledge have a patch >>>> tracker. It has a patch viewer (view patches that you have attached >>>> to >>> bugs): >>>> http://www.bugzilla.org/docs/2.18/html/patchviewer.html >>>> >>>> So as far as I can see from the test pages we've had so far, that >>>> means creating a "bug" or some other "object" for the patch, with >>>> cases where >>> the >>>> patch actually relates to an already listed bug, and cases where the >>> object >>>> would have to be created specifically for it (as in the above case). >>>> >>>> If we finally use Bugzilla, is the above a good idea, or are entries >>>> on a >>> Wiki >>>> page better? Those would presumably require the submitter to >>>> actually post a short initial message to -devel (patch attached, >>>> details of what it does >>> on >>>> the Wiki). >>>> >>>> But maybe protocol would require a short message to -devel anyway, >>>> even in the case of a "patch tracker"? >>>> >>>> Comments? >>>> >>>> >>>> >>>> Gale >>>> >>>> >>>> >>>>> Ed Musgrove wrote: >>>>>> After release of "stable" I propose to make the prefs panel user >>>>>> resizable (restrained only by valid screen size) and the >>>>>> keyboard panel columns automatically size themselves (I have the >>>>>> code completely finished) just like the mouse prefs panel is. >>>>>> This will resolve most if not all such issues. Vaguely related, >>>>>> I gave Gale working code which makes the Help/About... panel >>>>>> user resizable. (it is a trivial one line change). BTW, is there >>>>>> a problem or reason why >>> that >>>> was never committed (patch attached)? >>>>>> --Ed >>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Gale Andrews [mailto:[hidden email]] >>>>>>> Sent: Sunday, October 25, 2009 7:53 PM >>>>>>> To: [hidden email] >>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback >>>>>>> >>>>>>> >>>>>>> | From "Ed Musgrove" <[hidden email]> To >>>>>>> | <[hidden email]> >>>>>>> | Subject [Audacity-devel] Beta_Feedback >>>>>>>> Is it possible that the recent commit to fr.po caused this: >>>>>>>> >>>>>>>> Update of /cvsroot/audacity/htdocs/locale In directory >>>>>>>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 >>>>>>>> >>>>>>>> Modified Files: >>>>>>>> fr.po >>>>>>>> Log Message: >>>>>>>> Updated web site translation from Olivier Humbert >>>>>>> No, that is the translation for the web site, not the .po file >>>>>>> for the >>>>>> software. >>>>>>> See below. >>>>>>> >>>>>>> >>>>>>> | From "Ed Musgrove" <[hidden email]> Sun, 25 >> Oct >>>> 2009 >>>>>>> | 09:52:08 -0700 >>>>>>> | Subject: [Audacity-devel] Beta_Feedback >>>>>>>> Note that the problem is with width. Note that the Audacity >>>>>>>> "system informations" is printed in French. >>>>>>>> >>>>>>>> I carefully went through both (after having just downloaded >>>>>>>> the current >>>>>>> CVS >>>>>>>> head): >>>>>>>> audacity\src\prefs\PrefsDialog.cpp >>>>>>>> audacity\src\prefs\KeyConfigPrefs.cpp >>>>>>>> To ensure that none of the things I have played with recently >>>>>>>> were inadvertently committed -- they were not. >>>>>>>> >>>>>>>> Recently Gale made some changes to the text. I think that this >>>>>>>> dialogue initially sizes itself based on the width of the >>>>>>>> longest text string; >>>>>> could >>>>>>>> this be a translation issue? >>>>>>> If the problem is specific to running Audacity in French, using >>>>>>> the .mo file compiled from fr.po, then no, because my string >>>>>>> changes have not yet had a French translation committed. >>>>>>> >>>>>>> Using a Unicode Release build from CVS a few days ago on Ubuntu >>>>>>> 9.04 (so using the current fr.po file) the longer text seems to >>>>>>> wrap round correctly. The preferences dialogue could in fact >>>>>>> still be expanded a little horizontally to the full 800px width. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> If possible, I would like to have the reporter comment out >>>>>>>> that line so >>>>>> that >>>>>>>> the dialog will open without entering the debugger, then, send >>>>>>>> me a screenshot of the mouse panel, key binding panel and the >>>>>>>> directories >>>>>>> panel. >>>>>>>> Je parle un peut de Francais. (But my spelling and grammar are >>>>>> atrocious.) >>>>>>> Ed, I've sent you the e-mail address of the person privately, >>>>>>> so feel free >>>>>> to >>>>>>> contact them off-list for more information (but don't overdo it >>>>>>> if he isn't keen to go to a lot of trouble). :=) >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> >>>>>>> >>>>>>> Gale >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Gale Andrews [mailto:[hidden email]] >>>>>>>>> Sent: Sunday, October 25, 2009 1:28 AM >>>>>>>>> To: Laurent Epinat >>>>>>>>> Cc: [hidden email]; >>>>>>>>> [hidden email] >>>>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback >>>>>>>>> >>>>>>>>> >>>>>>>>> Thank you, I have forwarded this message to our developers' >>>>>>>>> mailing list. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Gale >>>>>>>>> Audacity Team >>>>>>>>> >>>>>>>>> >>>>>>>>> | From Laurent Epinat >>>>>>>>> | Sat, 24 Oct 2009 10:34:26 +0200 >>>>>>>>> | Subject: Beta_Feedback >>>>>>>>>> Just for information, I recompile the beta 1.3.9 version on >>>>>>>>>> AMD64 >>>>>>>>>> >>>>>>>>>> and I have an assert when I open the preference dialog box >>>>>>>>>> at the src/prefs/PrefsDialog.cpp line 136 : >>>>>>>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences >>>> dialog >>>>>>>>>> exceeds max size")); >>>>>>>>>> >>>>>>>>>> I add trace on the size and my dialog had >>>>>>>>>> sz.x=857 sz.y=382 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> My screen resolution is 1920x1200 I you need more >>>>>>>>>> information ... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Congratulation for the really good software >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Here the system informations >>>>>>>>>> >>>>>>>>>> Informations système >>>>>>>>>> Support de format de fichier >>>>>>>>>> libmad (Importation de MP3) Activé >>>>>>>>>> libvorbis (Import et Export Ogg Vorbis ) Activé >>>>>>>>>> libid3tag (support des tag ID3) Activé >>>>>>>>>> libflac (Import et Export FLAC) Activé >>>>>>>>>> libtwolame (export MP2) Désactivé >>>>>>>>>> QuickTime (Importer depuis QuickTime) Désactivé >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Librairies >>>>>>>>>> libresample >>>>>>>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio >>>>>> (Lecture >>>>>>>>>> et enregistrement audio) >>>>>>>>>> v19 >>>>>>>>>> wxWidgets 2.8.10 >>>>>>>>>> (Unicode) >>>>>>>>>> >>>>>>>>>> Fonctions >>>>>>>>>> Nyquist (Support de modules (plugins)) >>> Activé >>>>>>>>>> LADSPA (Support de modules (plugins)) >>> Activé >>>>>>>>>> Vamp (Support de modules (plugins)) > Activé >>>>>>>>>> Audio Units (Support de modules (plugins)) >> Désactivé >>>>>>>>>> PortMixer (Support du mixage de la carte son) Activé >>>>>>>>>> SoundTouch (Support du changement de hauteur et de >> tempo) >>>>>>>>> Désactivé >>>>>>>>>> Informations système >>>>>>>>>> Date de création du programme : Oct 18 2009 >>>>>>>>>> Type de version : Debug build >>>>>>>>>> Préfixe d'intallation /usr/local/ >>>>>>>>>> Répertoire des réglages : /home/laurent/.audacity-data >>>>>>> >>>>>>> >>>>>>> >>>>>> ---------------------------------------------------------------- >>>>>> ---- >>>>>> -------- >>>>>> -- >>>>>>> Come build with us! The BlackBerry(R) Developer Conference in >>>>>>> SF, CA is the only developer event you need to attend this year. >>>>>>> Jumpstart your developing skills, take BlackBerry mobile >>>>>>> applications to market and stay ahead of the curve. Join us >>>>>>> from >>>> November 9 - 12, 2009. Register now! >>>>>>> http://p.sf.net/sfu/devconference >>>>>>> _______________________________________________ >>>>>>> audacity-devel mailing list >>>>>>> [hidden email] >>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>>>>>> >>>>>>> --------------------------------------------------------------- >>>>>>> ---- >>>>>>> ----- >>>>>>> >>>>>>> --------------------------------------------------------------- >>>>>>> ---- >>>>>>> ----------- Come build with us! The BlackBerry(R) Developer >>>>>>> Conference in SF, CA is the only developer event you need to >>>>>>> attend this year. Jumpstart your developing skills, take >>>>>>> BlackBerry mobile applications to market and stay ahead of the >>>>>>> curve. Join us from November 9 - 12, 2009. Register now! >>>>>>> http://p.sf.net/sfu/devconference >>>>>>> >>>>>>> --------------------------------------------------------------- >>>>>>> ---- >>>>>>> ----- >>>>>>> >>>>>>> _______________________________________________ >>>>>>> audacity-devel mailing list >>>>>>> [hidden email] >>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>>>> ------------------------------------------------------------------ >>>>> ---- >>>>> -------- Come build with us! The BlackBerry(R) Developer >>>>> Conference in SF, CA is the only developer event you need to attend >> this year. >>>>> Jumpstart your developing skills, take BlackBerry mobile >>>>> applications to market and stay ahead of the curve. Join us from >>>>> November 9 - 12, 2009. Register now! >>>>> http://p.sf.net/sfu/devconference >>>>> _______________________________________________ >>>>> audacity-devel mailing list >>>>> [hidden email] >>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>>> >>>> >>>> >>> ---------------------------------------------------------------------- >>> ------ >>> -- >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >>>> is >>> the >>>> only developer event you need to attend this year. Jumpstart your >>>> developing skills, take BlackBerry mobile applications to market and >>>> stay ahead of the curve. Join us from November 9 - 12, 2009. Register >> now! >>>> http://p.sf.net/sfu/devconference >>>> _______________________________________________ >>>> audacity-devel mailing list >>>> [hidden email] >>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> >>> ---------------------------------------------------------------------- >>> -------- Come build with us! The BlackBerry(R) Developer Conference in >>> SF, CA is the only developer event you need to attend this year. >>> Jumpstart your developing skills, take BlackBerry mobile applications >>> to market and stay ahead of the curve. Join us from November 9 - 12, >>> 2009. Register now! >>> http://p.sf.net/sfu/devconference >>> _______________________________________________ >>> audacity-devel mailing list >>> [hidden email] >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> >> >> > ---------------------------------------------------------------------------- > -- >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA is > the >> only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Martyn Shaw-2
|
In reply to this post
by Vaughan Johnson
Vaughan Johnson wrote: ... > >> Can the venerable Audacity mentors >> who are more focused on major problems accept the enthusiast coder who >> might be more comfortable starting out dealing with the little things? > Depends on the bandwidth the noob requires. but we do try and be patient, and need more developers! ... >> I think we need a category of bug like "feature request". > A feature request is different from a bug. As Gale pointed out, we have > the wiki page for that. And then there is a third thing. They are "feature submissions". That is 'I wanted it to do this so here is a patch to make that so'. So where do we store that patch so that we can look at it 'sometime'? (and I consider searching the list archive as 'lost'). TTFN Martyn ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
In reply to this post
by Martyn Shaw-2
After having spent a week lurking on the wxWidgets dev-list I have changed
my opinion on one of these; see below ... --Ed > -----Original Message----- > From: Martyn Shaw [mailto:[hidden email]] > Sent: Sunday, November 01, 2009 3:12 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > > Ed Musgrove wrote: > > I think what you said is pretty much what I said: > > "enhancement" == "feature request" > > "a developer" == " venerable Audacity mentor" > > " (or more loosely, active contributors to this list)" == "hackers > > (like me)" > > To get from > > http://wiki.audacityteam.org/index.php?title=Feature_Requests > > to a "formal enhancement" requires intervention by an Audacity PTB. > > > > As for storing non-committed patches, I do not think it a good idea. > > They should be kept somewhere, in case we want to look at them. > The folks developing wxWidgets are using a patch tracker, here is an example: http://trac.wxwidgets.org/ticket/11372#comment:3 Which is based on an open-source project, Trac: http://trac.wxwidgets.org/about > Any > > patch proposed by ANYONE active on the dev-list should be first > > attached (zipped if large) to a dev-list message. This leaves it open > > for peer review and automatically stores it online at Source Forge > > (though the interface is not good for locating old attachments). > > That is part of the problem, yes. > > Those not on the dev-list should > > attach a (zipped--neither .patch nor .txt files are allowed) file to a > > post on http://wiki.audacityteam.org/index.php?title=Feature_Requests. > > That would be a good idea. How does that work? I am not very good > wikis. > [ Ed-- ] No editing of a wiki is involved. This is just a forum (bulletin board) with a fairly good interface. The messages are threaded, one may subscribe to a message (get e-mail notification when a message gets a new reply), insert hyperlinks in your messages (this allows you to embed pictures in your post which you have stored elsewhere) and attach files (zipped) which other readers may easily download. > Martyn > > > --Ed > > > > > >> -----Original Message----- > >> From: Gale Andrews [mailto:[hidden email]] > >> Sent: Saturday, October 31, 2009 1:18 PM > >> To: [hidden email] > >> Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > >> > >> > >> | From "Ed Musgrove" <[hidden email]> Fri, 30 Oct > 2009 > >> | 21:54:03 -0700 > >> | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > >>> Is Audacity a professionally developed product? Is it just something > >>> that a few people have thrown together in their spare time? Do we > >>> expect Audacity to be used primarily by those capable of compiling > >>> and understanding the source code, or are the vast majority of users > >>> audiophiles who have no desire nor ability to compile the code? Can > >>> the venerable Audacity mentors who are more focused on major > >>> problems accept the enthusiast coder who might be more comfortable > >>> starting out > >> dealing with the little things? > >>> Any change in the code should be documented. If it is a trivial > >>> change made by a longtime developer a comment with initials and the > >>> date next to the change might be sufficient. Anything which changes > >>> the user's experience should be formally proposed, discussed and the > >>> code peer-reviewed with alpha testing by at least one developer on > >>> each major > >> platform. > >>> I think we need a category of bug like "feature request". That way > >>> something sent to @feedback can be triaged by venerable developers > >>> into this category when appropriate. Recognized developers and > >>> hackers (like me) may also propose a "feature request" bug; someone > >>> with authorization on the bug list would need to actually enter it. > >> We've pretty much agreed as far as I understand it that "enhancements" > >> tracked in Bugzilla or whatever system we use should only be those > >> supported by a developer (or more loosely, active contributors to > >> this > > list). > >> User requests sent to feedback@ will continue to be processed on: > >> http://wiki.audacityteam.org/index.php?title=Feature_Requests > >> > >> We can take valuable/strongly voted for items from that page at any > >> time and turn it into a "developer supported" enhancement. > >> > >> The point of my question was whether we want to load a formal bug > >> tracker with what may be relatively trivial "enhancement" patches by > >> creating a > > new > >> item just to hold that patch; or store patches (or links to > >> them) otherwise. > >> > >> Obviously if we use Bugzilla we can attach a patch to an actual P1- > >> P5 bug > > (or > >> if Checklist remains in the short/medium term, a link to the patch). > >> A > > patch > >> like that isn't likely to drop out of sight. > >> > >> I think the problem is more the large number of patches for > >> "enhancements", some of which may come from someone completely > new to > >> the list, so they couldn't be described as "developer supported" in > >> the sense of the enhancements I was thinking of storing in the bug > >> tracker (where the case for them has already been largely agreed). > >> > >> > >> > >> Gale > >> > >> > >> > >>>> -----Original Message----- > >>>> From: Gale Andrews [mailto:[hidden email]] > >>>> Sent: Friday, October 30, 2009 9:14 PM > >>>> To: [hidden email] > >>>> Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > >>>> > >>>> > >>>> | From Martyn Shaw <[hidden email]> Sat, 31 Oct > 2009 > >>>> | 00:39:14 +0000 > >>>> | Subject: [Audacity-devel] Beta_Feedback > >>>>> ... I see no reason (on my platform), or any philosophical reason > >>>>> why the 'about' box shouldn't be resizable, and so I committed it > >>>>> (others may chose to revert). > >>>>> > >>>>> Just the sort of patch that is distracting us (me) from 2.0. It > >>>>> should have gone into a patch-tracker of some sort, commented on > >>>>> by people who tried it but maybe aren't 'committers', and not come > >>>>> up on -devel until later. This isn't a criticism of you or what > >>>>> you've done, but of the limited system that we have right now. > >>>>> I'm hoping that Bugzilla and it's protocols may help with this > >>>>> type of developer-bandwidth problem. > >>>> Bugzilla does not from my admittedly limited knowledge have a patch > >>>> tracker. It has a patch viewer (view patches that you have attached > >>>> to > >>> bugs): > >>>> http://www.bugzilla.org/docs/2.18/html/patchviewer.html > >>>> > >>>> So as far as I can see from the test pages we've had so far, that > >>>> means creating a "bug" or some other "object" for the patch, with > >>>> cases where > >>> the > >>>> patch actually relates to an already listed bug, and cases where > >>>> the > >>> object > >>>> would have to be created specifically for it (as in the above case). > >>>> > >>>> If we finally use Bugzilla, is the above a good idea, or are > >>>> entries on a > >>> Wiki > >>>> page better? Those would presumably require the submitter to > >>>> actually post a short initial message to -devel (patch attached, > >>>> details of what it does > >>> on > >>>> the Wiki). > >>>> > >>>> But maybe protocol would require a short message to -devel anyway, > >>>> even in the case of a "patch tracker"? > >>>> > >>>> Comments? > >>>> > >>>> > >>>> > >>>> Gale > >>>> > >>>> > >>>> > >>>>> Ed Musgrove wrote: > >>>>>> After release of "stable" I propose to make the prefs panel user > >>>>>> resizable (restrained only by valid screen size) and the keyboard > >>>>>> panel columns automatically size themselves (I have the code > >>>>>> completely finished) just like the mouse prefs panel is. > >>>>>> This will resolve most if not all such issues. Vaguely related, I > >>>>>> gave Gale working code which makes the Help/About... panel user > >>>>>> resizable. (it is a trivial one line change). BTW, is there a > >>>>>> problem or reason why > >>> that > >>>> was never committed (patch attached)? > >>>>>> --Ed > >>>>>> > >>>>>> > >>>>>>> -----Original Message----- > >>>>>>> From: Gale Andrews [mailto:[hidden email]] > >>>>>>> Sent: Sunday, October 25, 2009 7:53 PM > >>>>>>> To: [hidden email] > >>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback > >>>>>>> > >>>>>>> > >>>>>>> | From "Ed Musgrove" <[hidden email]> To > >>>>>>> | <[hidden email]> > >>>>>>> | Subject [Audacity-devel] Beta_Feedback > >>>>>>>> Is it possible that the recent commit to fr.po caused this: > >>>>>>>> > >>>>>>>> Update of /cvsroot/audacity/htdocs/locale In directory > >>>>>>>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665 > >>>>>>>> > >>>>>>>> Modified Files: > >>>>>>>> fr.po > >>>>>>>> Log Message: > >>>>>>>> Updated web site translation from Olivier Humbert > >>>>>>> No, that is the translation for the web site, not the .po file > >>>>>>> for the > >>>>>> software. > >>>>>>> See below. > >>>>>>> > >>>>>>> > >>>>>>> | From "Ed Musgrove" <[hidden email]> Sun, 25 > >> Oct > >>>> 2009 > >>>>>>> | 09:52:08 -0700 > >>>>>>> | Subject: [Audacity-devel] Beta_Feedback > >>>>>>>> Note that the problem is with width. Note that the Audacity > >>>>>>>> "system informations" is printed in French. > >>>>>>>> > >>>>>>>> I carefully went through both (after having just downloaded the > >>>>>>>> current > >>>>>>> CVS > >>>>>>>> head): > >>>>>>>> audacity\src\prefs\PrefsDialog.cpp > >>>>>>>> audacity\src\prefs\KeyConfigPrefs.cpp > >>>>>>>> To ensure that none of the things I have played with recently > >>>>>>>> were inadvertently committed -- they were not. > >>>>>>>> > >>>>>>>> Recently Gale made some changes to the text. I think that this > >>>>>>>> dialogue initially sizes itself based on the width of the > >>>>>>>> longest text string; > >>>>>> could > >>>>>>>> this be a translation issue? > >>>>>>> If the problem is specific to running Audacity in French, using > >>>>>>> the .mo file compiled from fr.po, then no, because my string > >>>>>>> changes have not yet had a French translation committed. > >>>>>>> > >>>>>>> Using a Unicode Release build from CVS a few days ago on Ubuntu > >>>>>>> 9.04 (so using the current fr.po file) the longer text seems to > >>>>>>> wrap round correctly. The preferences dialogue could in fact > >>>>>>> still be expanded a little horizontally to the full 800px width. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>> If possible, I would like to have the reporter comment out that > >>>>>>>> line so > >>>>>> that > >>>>>>>> the dialog will open without entering the debugger, then, send > >>>>>>>> me a screenshot of the mouse panel, key binding panel and the > >>>>>>>> directories > >>>>>>> panel. > >>>>>>>> Je parle un peut de Francais. (But my spelling and grammar are > >>>>>> atrocious.) > >>>>>>> Ed, I've sent you the e-mail address of the person privately, so > >>>>>>> feel free > >>>>>> to > >>>>>>> contact them off-list for more information (but don't overdo it > >>>>>>> if he isn't keen to go to a lot of trouble). :=) > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Thanks > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Gale > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>> -----Original Message----- > >>>>>>>>> From: Gale Andrews [mailto:[hidden email]] > >>>>>>>>> Sent: Sunday, October 25, 2009 1:28 AM > >>>>>>>>> To: Laurent Epinat > >>>>>>>>> Cc: [hidden email]; > >>>>>>>>> [hidden email] > >>>>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Thank you, I have forwarded this message to our developers' > >>>>>>>>> mailing list. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Gale > >>>>>>>>> Audacity Team > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> | From Laurent Epinat > >>>>>>>>> | Sat, 24 Oct 2009 10:34:26 +0200 > >>>>>>>>> | Subject: Beta_Feedback > >>>>>>>>>> Just for information, I recompile the beta 1.3.9 version on > >>>>>>>>>> AMD64 > >>>>>>>>>> > >>>>>>>>>> and I have an assert when I open the preference dialog box at > >>>>>>>>>> the src/prefs/PrefsDialog.cpp line 136 : > >>>>>>>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences > >>>> dialog > >>>>>>>>>> exceeds max size")); > >>>>>>>>>> > >>>>>>>>>> I add trace on the size and my dialog had > >>>>>>>>>> sz.x=857 sz.y=382 > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> My screen resolution is 1920x1200 I you need more information > >>>>>>>>>> ... > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Congratulation for the really good software > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Here the system informations > >>>>>>>>>> > >>>>>>>>>> Informations système > >>>>>>>>>> Support de format de fichier > >>>>>>>>>> libmad (Importation de MP3) Activé > >>>>>>>>>> libvorbis (Import et Export Ogg Vorbis ) Activé > >>>>>>>>>> libid3tag (support des tag ID3) Activé > >>>>>>>>>> libflac (Import et Export FLAC) Activé > >>>>>>>>>> libtwolame (export MP2) Désactivé > >>>>>>>>>> QuickTime (Importer depuis QuickTime) Désactivé > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Librairies > >>>>>>>>>> libresample > >>>>>>>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio > >>>>>> (Lecture > >>>>>>>>>> et enregistrement audio) > >>>>>>>>>> v19 > >>>>>>>>>> wxWidgets 2.8.10 > >>>>>>>>>> (Unicode) > >>>>>>>>>> > >>>>>>>>>> Fonctions > >>>>>>>>>> Nyquist (Support de modules (plugins)) > >>> Activé > >>>>>>>>>> LADSPA (Support de modules (plugins)) > >>> Activé > >>>>>>>>>> Vamp (Support de modules (plugins)) > > Activé > >>>>>>>>>> Audio Units (Support de modules (plugins)) > >> Désactivé > >>>>>>>>>> PortMixer (Support du mixage de la carte son) Activé > >>>>>>>>>> SoundTouch (Support du changement de hauteur et de > >> tempo) > >>>>>>>>> Désactivé > >>>>>>>>>> Informations système > >>>>>>>>>> Date de création du programme : Oct 18 2009 > >>>>>>>>>> Type de version : Debug build > >>>>>>>>>> Préfixe d'intallation /usr/local/ > >>>>>>>>>> Répertoire des réglages : /home/laurent/.audacity-data > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> ---------------------------------------------------------------- > >>>>>> ---- > >>>>>> -------- > >>>>>> -- > >>>>>>> Come build with us! The BlackBerry(R) Developer Conference in > >>>>>>> SF, CA is the only developer event you need to attend this year. > >>>>>>> Jumpstart your developing skills, take BlackBerry mobile > >>>>>>> applications to market and stay ahead of the curve. Join us from > >>>> November 9 - 12, 2009. Register now! > >>>>>>> http://p.sf.net/sfu/devconference > >>>>>>> _______________________________________________ > >>>>>>> audacity-devel mailing list > >>>>>>> [hidden email] > >>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel > >>>>>>> > >>>>>>> --------------------------------------------------------------- > >>>>>>> ---- > >>>>>>> ----- > >>>>>>> > >>>>>>> --------------------------------------------------------------- > >>>>>>> ---- > >>>>>>> ----------- Come build with us! The BlackBerry(R) Developer > >>>>>>> Conference in SF, CA is the only developer event you need to > >>>>>>> attend this year. Jumpstart your developing skills, take > >>>>>>> BlackBerry mobile applications to market and stay ahead of the > >>>>>>> curve. Join us from November 9 - 12, 2009. Register now! > >>>>>>> http://p.sf.net/sfu/devconference > >>>>>>> > >>>>>>> --------------------------------------------------------------- > >>>>>>> ---- > >>>>>>> ----- > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> audacity-devel mailing list > >>>>>>> [hidden email] > >>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel > >>>>> ------------------------------------------------------------------ > >>>>> ---- > >>>>> -------- Come build with us! The BlackBerry(R) Developer > >>>>> Conference in SF, CA is the only developer event you need to > >>>>> attend > >> this year. > >>>>> Jumpstart your developing skills, take BlackBerry mobile > >>>>> applications to market and stay ahead of the curve. Join us from > >>>>> November 9 - 12, 2009. Register now! > >>>>> http://p.sf.net/sfu/devconference > >>>>> _______________________________________________ > >>>>> audacity-devel mailing list > >>>>> [hidden email] > >>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel > >>>> > >>>> > >>>> > >>> -------------------------------------------------------------------- > >>> -- > >>> ------ > >>> -- > >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, > >>>> CA is > >>> the > >>>> only developer event you need to attend this year. Jumpstart your > >>>> developing skills, take BlackBerry mobile applications to market > >>>> and stay ahead of the curve. Join us from November 9 - 12, 2009. > >>>> Register > >> now! > >>>> http://p.sf.net/sfu/devconference > >>>> _______________________________________________ > >>>> audacity-devel mailing list > >>>> [hidden email] > >>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel > >>> > >>> -------------------------------------------------------------------- > >>> -- > >>> -------- Come build with us! The BlackBerry(R) Developer Conference > >>> in SF, CA is the only developer event you need to attend this year. > >>> Jumpstart your developing skills, take BlackBerry mobile > >>> applications to market and stay ahead of the curve. Join us from > >>> November 9 - 12, 2009. Register now! > >>> http://p.sf.net/sfu/devconference > >>> _______________________________________________ > >>> audacity-devel mailing list > >>> [hidden email] > >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel > >> > >> > >> > > ---------------------------------------------------------------------- > > ------ > > -- > >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA > >> is > > the > >> only developer event you need to attend this year. Jumpstart your > >> developing skills, take BlackBerry mobile applications to market and > >> stay ahead of the curve. Join us from November 9 - 12, 2009. Register > now! > >> http://p.sf.net/sfu/devconference > >> _______________________________________________ > >> audacity-devel mailing list > >> [hidden email] > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > ---------------------------------------------------------------------- > > -------- Come build with us! The BlackBerry(R) Developer Conference in > > SF, CA is the only developer event you need to attend this year. > > Jumpstart your developing skills, take BlackBerry mobile applications > > to market and stay ahead of the curve. Join us from November 9 - 12, > > 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > audacity-devel mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the > only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From "Ed Musgrove" <[hidden email]> | Sun, 1 Nov 2009 16:04:03 -0800 | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > -----Original Message----- > > From: Martyn Shaw [mailto:[hidden email]] > > Sent: Sunday, November 01, 2009 3:12 PM > > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > Ed Musgrove wrote: > > > To get from > > > http://wiki.audacityteam.org/index.php?title=Feature_Requests > > > to a "formal enhancement" requires intervention by an Audacity PTB. > > > > > > As for storing non-committed patches, I do not think it a good idea. > > > > They should be kept somewhere, in case we want to look at them. > > > [ Ed-- ] > The folks developing wxWidgets are using a patch tracker, here is an > example: > http://trac.wxwidgets.org/ticket/11372#comment:3 > > Which is based on an open-source project, Trac: > http://trac.wxwidgets.org/about That isn't explicitly a patch tracker. It's a bug tracker, like Bugzilla, which we're considering now as a replacement for Checklist. You can attach a patch to a bug, as in that ticket 11372, or not. If you want to use Bugzilla to track all patches, then every time someone sends a patch to _devel saying "this is my idea for a new item in the track dropdown menu" or whatever it is, we have to raise a Bugzilla item for it. I don't object strongly to that, if these had their own "Unverified Enhancement" category or similar, but I think it may make more sense not to clutter a bug tracker with them. > > > Any patch proposed by ANYONE active on the dev-list should be first > > > attached (zipped if large) to a dev-list message. This leaves it open > > > for peer review and automatically stores it online at Source Forge > > > (though the interface is not good for locating old attachments). Martyn said "I consider searching the list archive as 'lost' ". I agree - far too cumbersome. > > Those not on the dev-list should > > > attach a (zipped--neither .patch nor .txt files are allowed) file to a > > > post on http://wiki.audacityteam.org/index.php?title=Feature_Requests. > > > > That would be a good idea. How does that work? I am not very good > editing wikis. > > > > [ Ed-- ] > No editing of a wiki is involved. This is just a forum (bulletin board) with > a fairly good interface. The messages are threaded, one may subscribe to a > message (get e-mail notification when a message gets a new reply), insert > hyperlinks in your messages (this allows you to embed pictures in your post > which you have stored elsewhere) and attach files (zipped) which other > readers may easily download. Are you talking about the Audacity Forum, Ed? http://forum.audacityteam.org/ The Wiki Feature Requests page is for user Feature Requests. Let's leave it like that, I'd suggest. There are no patches linked to there nor likely to be. As regards uploading to the Wiki, only a few image formats are allowed at the moment. The documentation suggests other formats like .zip, .txt and .pdf could be added to the image upload system, but I've never tried it. Do we want to? I think the easiest thing may be just to have a Wiki page for "enhancement patches" and link to the thread where someone posted to -devel with an attached patch. That doesn't create extra e-mail. I don't mind doing the work. If the patch is for a bug, then it would be attached to the bug in the bug tracker, or linked to as we've done in the past in the Checklist. While it's possible to use the Forum, I still think it needs one page to store the patches, so people know exactly where to go and look for patches that haven't been dealt with. I suspect the Wiki is the more obvious place for storage of the links or patches, just like "Feature Requests" are thrashed out on the Forum and then eventually added to the Wiki Feature Requests page by Peter and myself. So if any users do drop patches on the Forum rather than posting to -devel, the patches could then be moved to the Wiki "enhancement patches" page. Gale ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
> -----Original Message-----
which we're
> From: Gale Andrews [mailto:[hidden email]] > Sent: Sunday, November 01, 2009 9:00 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > | From "Ed Musgrove" <[hidden email]> Sun, 1 Nov 2009 > | 16:04:03 -0800 > | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > -----Original Message----- > > > From: Martyn Shaw [mailto:[hidden email]] > > > Sent: Sunday, November 01, 2009 3:12 PM > > > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback Ed > > > Musgrove wrote: > > > > To get from > > > > http://wiki.audacityteam.org/index.php?title=Feature_Requests > > > > to a "formal enhancement" requires intervention by an Audacity PTB. > > > > > > > > As for storing non-committed patches, I do not think it a good idea. > > > > > > They should be kept somewhere, in case we want to look at them. > > > > > [ Ed-- ] > > The folks developing wxWidgets are using a patch tracker, here is an > > example: > > http://trac.wxwidgets.org/ticket/11372#comment:3 > > > > Which is based on an open-source project, Trac: > > http://trac.wxwidgets.org/about > > That isn't explicitly a patch tracker. It's a bug tracker, like Bugzilla, > considering now as a replacement for Checklist. You can attach a patch to a > bug, as in that ticket 11372, or not. > [ Ed-- ] Maybe we should have two Bugzilla projects--one for bugs and one for features. I am eager to see how well the Bugzilla interface works for honing in a bug repair. Rarely is the first patch I submit for testing the be all/end all! > If you want to use Bugzilla to track all patches, then every time someone > sends a patch to _devel saying "this is my idea for a new item in the track > dropdown menu" or whatever it is, we have to raise a Bugzilla item for it. > I don't object strongly to that, if these had their own "Unverified > Enhancement" category or similar, but I think it may make more sense not to > clutter a bug tracker with them. > > > > > > Any patch proposed by ANYONE active on the dev-list should be first > > > > attached (zipped if large) to a dev-list message. This leaves it open > > > > for peer review and automatically stores it online at Source Forge > > > > (though the interface is not good for locating old attachments). > > Martyn said "I consider searching the list archive as 'lost' ". I agree - far > too cumbersome. > [ Ed-- ] +1 lost > > > > Those not on the dev-list should > > > > attach a (zipped--neither .patch nor .txt files are allowed) file to a > > > > post on > http://wiki.audacityteam.org/index.php?title=Feature_Requests. > > > > > > That would be a good idea. How does that work? I am not very good > > editing wikis. > > > > > > > [ Ed-- ] > > No editing of a wiki is involved. This is just a forum (bulletin board) with > > a fairly good interface. The messages are threaded, one may subscribe to a > > message (get e-mail notification when a message gets a new reply), insert > > hyperlinks in your messages (this allows you to embed pictures in your post > > which you have stored elsewhere) and attach files (zipped) which other > > readers may easily download. > > Are you talking about the Audacity Forum, Ed? > http://forum.audacityteam.org/ > [ Ed-- ] Yes... http://forum.audacityteam.org/viewforum.php?f=20&sid=b89cf6b62c221ff68a5f98f e82c7a1c7 > The Wiki Feature Requests page is for user Feature Requests. Let's leave > it like that, I'd suggest. There are no patches linked to there nor likely > to be. > > As regards uploading to the Wiki, only a few image formats are allowed > at the moment. The documentation suggests other formats like .zip, .txt > and .pdf could be added to the image upload system, but I've never tried > it. Do we want to? > [ Ed-- ] If we want to store non-committed patches we need some storage and interface. > I think the easiest thing may be just to have a Wiki page for "enhancement > patches" and link to the thread where someone posted to -devel with an > attached patch. That doesn't create extra e-mail. I don't mind doing > the work. > > If the patch is for a bug, then it would be attached to the bug in the > bug tracker, or linked to as we've done in the past in the Checklist. > > While it's possible to use the Forum, I still think it needs one page to > store the patches, so people know exactly where to go and look for > patches that haven't been dealt with. > > I suspect the Wiki is the more obvious place for storage of the links or > patches, just like "Feature Requests" are thrashed out on the Forum and > then eventually added to the Wiki Feature Requests page by Peter and > myself. So if any users do drop patches on the Forum rather than posting > to -devel, the patches could then be moved to the Wiki "enhancement > patches" page. > Sound good. My biggest problem with the wiki is that it does not make for easy dialog. There are innumerable categories on the wiki "Feature Request" page. Maybe it should be broken down into sub-pages with the main page being only an index with links (i.e. just the "contents" on the main page). There is no easy way of telling who voted for what; nor is there an obvious way to add a vote. I suppose I could "Edit" the page (which I just did as a test--made the first item 059 votes instead of 59--changed it back too). Who is to say how many votes are real? There is no real effort to maintain a status--"Would like to implement", "Will implement", "Unlikely to implement"--etc.; some of the items on the page are working in 1.3.10--some of them have notes to that effect, others do not. > > > Gale > > > > > ---------------------------------------------------------------------------- -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From "Ed Musgrove" <[hidden email]> | Sun, 1 Nov 2009 21:52:53 -0800 | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > -----Original Message----- > > From: Gale Andrews [mailto:[hidden email]] > > Sent: Sunday, November 01, 2009 9:00 PM > > To: [hidden email] > > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > > > > | From "Ed Musgrove" <[hidden email]> Sun, 1 Nov 2009 > > | 16:04:03 -0800 > > | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback > > > > -----Original Message----- > > > > From: Martyn Shaw [mailto:[hidden email]] > > > > Sent: Sunday, November 01, 2009 3:12 PM > > > > Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback Ed > > > > Musgrove wrote: > > > > > To get from > > > > > http://wiki.audacityteam.org/index.php?title=Feature_Requests > > > > > to a "formal enhancement" requires intervention by an Audacity PTB. > > > > > > > > > > As for storing non-committed patches, I do not think it a good idea. > > > > > > > > They should be kept somewhere, in case we want to look at them. > > > > > > > [ Ed-- ] > > > The folks developing wxWidgets are using a patch tracker, here is an > > > example: > > > http://trac.wxwidgets.org/ticket/11372#comment:3 > > > > > > Which is based on an open-source project, Trac: > > > http://trac.wxwidgets.org/about > > > > That isn't explicitly a patch tracker. It's a bug tracker, like Bugzilla, > which we're > > considering now as a replacement for Checklist. You can attach a patch to > a > > bug, as in that ticket 11372, or not. > > > [ Ed-- ] > Maybe we should have two Bugzilla projects--one for bugs and one for > features. Personally I think we are overplaying "features". We've already got lots of "developer-supported" ones to choose from, and lots of ideas for new capabilities which could be part of GSoC (GSoC could also cover bug-fixing or stabilising what we have now). That's not to deny that sometimes, a small patch can provide a good usability enhancement. > > ... I think the easiest thing may be just to have a Wiki page for "enhancement > > patches" and link to the thread where someone posted to -devel with an > > attached patch. That doesn't create extra e-mail. I don't mind doing > > the work. > > > > If the patch is for a bug, then it would be attached to the bug in the > > bug tracker, or linked to as we've done in the past in the Checklist. > > > > While it's possible to use the Forum, I still think it needs one page to > > store the patches, so people know exactly where to go and look for > > patches that haven't been dealt with. > > > > I suspect the Wiki is the more obvious place for storage of the links or > > patches, just like "Feature Requests" are thrashed out on the Forum and > > then eventually added to the Wiki Feature Requests page by Peter and > > myself. So if any users do drop patches on the Forum rather than posting > > to -devel, the patches could then be moved to the Wiki "enhancement > > patches" page. > > > [ Ed-- ] > Sound good. My biggest problem with the wiki is that it does not make for > easy dialog. We don't find that too difficult. Each message on the Forum is a bullet point on the Wiki. > There are innumerable categories on the wiki "Feature Request" page. Maybe > it should be broken down into sub-pages with the main page being only an > index with links (i.e. just the "contents" on the main page). Quite possibly. I've already got a plan to split it down to four or five categories, one per page, but it's no priority for me to do it at the moment. > There is no easy way of telling who voted for what > nor is there an obvious way to add a vote. I suppose I could "Edit" > the page (which I just did as a test--made the first item 059 votes instead > of 59--changed it back too). That's how you "vote", yes: http://wiki.audacityteam.org/index.php?title=Editing_Feature_Requests#Voting > Who is to say how many votes are real? If anyone cheats by adding multiple votes, I change it back. It works fairly well, though we could investigate a better voting system longer term. We had an experimental one, but it was (or became) broken. > There is no real effort to maintain a status--"Would like to implement", > "Will implement", "Unlikely to implement"--etc.; De facto, anything not already adopted as a "developer-supported" enhancement is "currently unlikely". > some of the items on the page are working in 1.3.10--some of them have > notes to that effect, others do not. True, but again, priorities. If you would like to volunteer to move things already in 1.3 versions from Feature Requests to: http://wiki.audacityteam.org/index.php?title=Completed_Features feel free. But it may make more sense to do all that after 2.0, both because of "priorities", and because a lot of items in "Completed Features" will then need moving from "In latest Beta" to "In latest Stable" anyway. Gale ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
