Difference between revisions of "Completed Proposal Menu Reorganisation"
m (→Developer/QA Backing: add my support)
(old & new Edit Menus side-by-side)
|Line 62:||Line 62:|
** 'Split|Split New|Join|Detach at Silences'
** 'Split|Split New|Join|Detach at Silences'
Revision as of 21:41, 28 April 2011
|Proposal pages help us get from feature requests into actual plans. This proposal page is about reorganising the menus.|
Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.
- Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.
One driver for reorganising the menus is to avoid the problems that arise from having 'export' and 'save' as different functions. The options there can with care be merged so that there are fewer menu items.
The Audacity menus have also become rather complex with numerous options, especially when label linking is enabled.
- "Something needs to be done!" That sentiment is backed by (at least)
- GA - But regressions in functionality and need for ease of access must be kept in mind
- PS - I particularly like restricting the Open (Open Project) command to only opening Projects
- New users:
- Confused about what 'export' and 'save' mean.
- Too many choices.
- Expecting to work with (e.g.) wav rather than projects.
- Experienced users:
- Find menus too long.
- Find menus too verbose.
The general tenor of the solution is to make it easier and more natural to get to the most commonly used and most familiar options. This will mainly be achieved by better grouping of menu items into submenus, rather than putting them all at the same level.
Mostly better use of fly-out submenus.
- 'Open' will be renamed 'Open Project' and ONLY open an Audacity project. If you try to open a wav file it will tell you about projects and tell you to import instead. This will help reduce the risk of users thinking they are genuinely opening and working on a wav file directly.
- Recent Files will continue to operate much 'as currently'. If you import a file it will be added to the recent files list. If you select a non .aup file from the recently opened list it is imported.
- Drag-and-drop opening of a .wav file will import the dragged audio into your current project.
- 'Save Project|Save Project As >|Export >' as the three saving options on the main menu, in that order.
- 'Save Project As >' leads to
- 'Standard Project...|Compressed Project...'.
- 'Export >' leads to
- 'Export All Audio|Export Selection|Export Multiple|Export Labels|Export MIDI'.
- We might at some future date give access to all export settings from this 'Export' submenu, and also faster routes to export wav, export mp3, but we're not doing that this time round.
- The chains menu item is now called 'Batch Chains >' and leads to
- 'Check Dependencies...' moves to the Tools menu. It is a diagnostic tool.
- 'Meta Data Editor...' moves to the View menu. It isn't a file, and does not belong in the file menu.
- 'Remove Audio >' leading to
- 'Cut|Split Cut|Delete|Split Delete|Silence Audio|Trim'
- 'Clip Boundaries >' leading to
- 'Split|Split New|Join|Detach at Silences'
- 'Mix and Render >'
- 'Replace|Mix to New Track'
- 'All Track Mute/Solo >'
- 'Mute All|UnMute All|UnSolo All|UnMute & UnSolo All'
- Now has the Meta Data Editor, and it is called 'Meta Data Editor' not 'Open Meta Data Editor'.
- This is a new menu before Help, with things that mostly come from Help.
The items which are really 'tools' (diagnostics) taken out of Help and are now in the Tools menu.
- Help Menu has 'About' as the last entry.
Mock up of proposed menu changes.
These aren't strictly part of the menu reorganization, but came up in discussion of it. They are not being acted on for this proposal.
- Some users would like Export to default to the directory where the audacity project is.
- Ed has a patch to allow this
- Some users would like project save and export directories to be set by preferences.
- Ed has a patch to allow .aup to be drag and dropped too.
- It would probably be a good idea to modify trim so that it only removes audio from selected clips, not whole clips outside its selection.
- The "align" commands are inadequate, confusing and lack shortcut bindings. A command to align tracks end-to-end is sorely needed.
- Stop and move cursor to stop point, which is SHIFT+A, is not in the menu. Preferred option is to make this a preference as to how stop behaves.
- Signposting: Give the users visual clues that are in their face. Look at GIMP. Every menu item has a hover tooltip which is duplicated in the Status Bar. It would have to have a Preference to turn it off (as it does in GIMP).
- Lots of discussion of shortcut keys. (Moved to talk page for now).
- At this stage we are NOT proposing a mode where Audacity can switch over to using a wav file as if it were its project - much as Microsoft word can open a txt file, but then warns when you try to save it that 'some features/formatting can't be saved in text format'. It's not that hard to add, but it would go outside the scope of this proposal. This would be a good feature though and solve a lot of user confusion. If we were to do it, we'd list in the warning dialog what would be lost. IF we did this we could at the same time change the labeling of 'Save Project' and 'Save Project As' to 'Save' and 'Save As'. We would also change 'Recent Projects' back to 'Recent Files'.
- In the Edit menu, there is an unresolved issue as to how to handle the different behaviour of [ and ] when the track is static or playing (currently this is at Edit > Select > Left / Right at Playback Position).
- There is a consistent view among some users that the Tracks Menu and not the Track Control Panel should have commands for channel setting (or even rate and format). This is on grounds of discoverability above all else. Gale thinks this is worth some consideration although it might be hard to make it work intuitively. It "would" be a considerable time saving if e.g. you wanted to split 20 stereo pairs in a project.