Thread: [Audacity-devel] Opening 1.2.6 Projects
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2007-11-25 18:09:07
|
On the checklist, this essential item is marked as done: "Fix: Change dialog when you open a 1.2 project. It should just tell them that this will change the project to a 1.4 project file that can't be opened by 1.2. [Done]" The wording that appears when you open a 1.2.6 Project in 1.3.4 is: "This file was saved by Audacity 1.2.6 and the format\nhas changed. This version of Audacity can try to\nopen it, but there may be problems. You should back up\nyour project first, to be safe.\n\nAfter you save the file with this version of Audacity,\nyou will not be able to open the file in the older\nversion anymore. Would you like to open\nthis file right now anyway?" To me this does not look consistent with the fix. Should we just remove the second and third sentence (and fix "anymore")? And is this wording better? "This file was saved by Audacity 1.2.6. You can open\nthe file with this version of Audacity, but if you save it with this version\nyou will no longer be able to open it in older versions.\n\nOpen this file now?" Gale |
From: Vaughan J. <va...@au...> - 2007-11-27 04:32:38
|
Gale Andrews wrote: > On the checklist, this essential item is marked as done: > > "Fix: Change dialog when you open a 1.2 project. It should just tell > them that this will change the project to a 1.4 project file that can't > be opened by 1.2. [Done]" > > The wording that appears when you open a 1.2.6 Project in 1.3.4 is: > > "This file was saved by Audacity 1.2.6 and the format\nhas changed. > This version of Audacity can try to\nopen it, but there may be problems. > You should back up\nyour project first, to be safe.\n\nAfter you save > the file with this version of Audacity,\nyou will not be able to open > the file in the older\nversion anymore. Would you like to open\nthis > file right now anyway?" > > To me this does not look consistent with the fix. Should we just > remove the second and third sentence (and fix "anymore")? And is > this wording better? > > "This file was saved by Audacity 1.2.6. You can open\nthe file with this > version of Audacity, but if you save it with this version\nyou will no > longer be able to open it in older versions.\n\nOpen this file now?" > > > Gale > > I think that's great! Thanks, Gale! - Vaughan |
From: Martyn S. <mar...@go...> - 2007-11-28 01:20:48
|
Hello there Vaughan Johnson wrote: > Gale Andrews wrote: ... >> "This file was saved by Audacity 1.2.6. You can open\nthe file with this >> version of Audacity, but if you save it with this version\nyou will no >> longer be able to open it in older versions.\n\nOpen this file now?" ... > > I think that's great! Thanks, Gale! > ... Yes, much better, so I committed it, along with a few other changes to wording that I got from posts and the Wiki. Can somebody update the Wiki please? I thought it best to 'commit and be damned' rather than to pontificate here. I may get flamed, but wtf. I wasn't sure whether to put 'Waveform (dB)' in quotes in GUIPrefs, I thought it best to, since it's a piece of screen text that the user is looking for. I don't know if it is consistent elsewhere, but I think it should be. I put "OK... Audacious!" to "OK" in the Splash screen; it's the first thing people will see when they start Audacity, and I think it should look/sound like a 'normal' app. I think we should revert to "Audacious!" in the 'About' box - there is a long history of 'abouts' being quirky and being a place to express individualism in an application. When we are asking for new information, I think it is good to say "New sample rate (Hz): [box]" and so that's what I made the Resample box say. There has been much opinion here about 'Frequency [Box] Hz' and 'Frequency (Hz): [Box]' and it seems to me that there must be some interface norms that we can comply to. Can anybody point to the standards? This seems like the 'OK, Cancel' issue which was resolved in that way. I think "New sample rate (Hz): [box]" is likely to be less work, work on more screen readers, look worse in some cases, and vary in acceptance depending on cultural norms and the dialog we are talking about. But I think it is a good default. So, if I have annoyed people my expressing myself in the CVS, so be it. They will no doubt change things back. Have put a Unicode_Debug build I just made at http://mjshaw.at-uclan.com/audacity.zip, in case anyone who can't build (and is on Win) want's to try it. The following 'experimental' bits are turned on (I think): LOGARITHMIC_TONE_CHIRP looks good to go to me LOGARITHMIC_SPECTRUM also looking good to me EXPERIMENTAL_RULER_AUTOSIZE and again (although I have some issues with 'Ruler', which I shall try and resolve) EXPERIMENTAL_FIND_NOTES still work to do here, I think. EXPERIMENTAL_FFT_SKIP_POINTS untested by me EXPERIMENTAL_FFT_Y_GRID I've done some testing, but am unsure about it's general usefulness to a wider audience. EXPERIMENTAL_FIND_NOTES I'll leave this one up to you, I think it's work-in-progress. TTFN Martyn |
From: Gale A. <ga...@au...> - 2007-11-28 19:01:50
|
| From Martyn Shaw <mar...@go...> | Wed, 28 Nov 2007 01:22:49 +0000 | Subject: [Audacity-devel] Moving forewards... > > Gale Andrews wrote: > ... > >> "This file was saved by Audacity 1.2.6. You can open\nthe file with this > >> version of Audacity, but if you save it with this version\nyou will no > >> longer be able to open it in older versions.\n\nOpen this file now?" > ... > Yes, much better, so I committed it, along with a few other changes to > wording that I got from posts and the Wiki. Can somebody update the > Wiki please? Yes - I moved the items you did to the "Done" section in [[Wording]]. Thanks, Martyn. I managed to add one (moved in from Release Checklist) just after you did your changes: =Project.cpp= '''Current text, when opening 1.x project in 1.3.4: (line 2146)''' "This file was saved by Audacity (1.x.x), a much\nolder version of Audacity. The format has changed.\nAudacity will probably destroy the file in trying\nto open it. You must back up your project\nfirst, to be safe.\n\nWould you like to try to open this file\nright now anyway?" '''Suggested alternative" "This file was saved by Audacity (1.x.x), a much\nolder version. The format has changed.\nAudacity could corrupt the file in opening\nit, so you must back it up first.\n\nOpen this file now?" > I wasn't sure whether to put 'Waveform (dB)' in quotes in GUIPrefs, I > thought it best to, since it's a piece of screen text that the user is > looking for. I don't know if it is consistent elsewhere, but I think > it should be. It looks like another issue for our [[Visual Consistency]] page. It looks currently that we either don't put in quotes or use double quotes " "... I'd have thought don't put in quotes when it's a section header, do if it's inside a header, but don't have strong views. > I put "OK... Audacious!" to "OK" in the Splash screen; it's the first > thing people will see when they start Audacity, and I think it should > look/sound like a 'normal' app. I think we should revert to > "Audacious!" in the 'About' box - there is a long history of 'abouts' > being quirky and being a place to express individualism in an application. It's inconsistent with the "Welcome Screen", inconsistent with our expressed desire to avoid being "friendly" in the program itself, and makes for a very long button, especially if we precede it with "OK..." so that VI users are more comfortable with it. And to be honest when I first saw it as "Audacious" in 1.2.6 I didn't know if I was supposed to click it or what. If we must have this word, could it go as text to left of the "OK" button? > When we are asking for new information, I think it is good to say > "New sample rate (Hz): [box]" and so that's what I made the Resample > box say. There has been much opinion here about 'Frequency [Box] Hz' > and 'Frequency (Hz): [Box]' and it seems to me that there must be some > interface norms that we can comply to. Can anybody point to the > standards? This seems like the 'OK, Cancel' issue which was resolved > in that way. > > I think "New sample rate (Hz): [box]" is likely to be less work, work > on more screen readers, look worse in some cases, and vary in > acceptance depending on cultural norms and the dialog we are talking > about. But I think it is a good default. Goldwave (just checked) and (from memory) a few others have units in square brackets [ ] before the slider and/or input box. On the whole, this has my vote. It should satisfy screen readers, there are then no inconsistencies with Nyquist plug-ins, and (to me) the square brackets look better against a rectangular object like an input box. The worst case (against a short input box) looks better to me than the worst case (after a long input box) if you have the unit after the box. We'd have to fiddle with some of the Preferences text again, especially Audio I/O, but units before the box seems to be less work in total. Thanks Gale |