This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:qt4_feature_review [2009/11/16 03:00]
dev:qt4_feature_review [2018/02/07 17:07] (current)
Line 1: Line 1:
 ====== Feature Review for Thorn ====== ====== Feature Review for Thorn ======
 This is intended to be complementary to the [[qt4_bug_tracker|Fake Bug Tracker]]. This is intended to be complementary to the [[qt4_bug_tracker|Fake Bug Tracker]].
-This was a good idea Chris had, but I'm starting over from the top and being more systematic and methodical.  ​Because I have a tendency to use the menu options on the left more than those on the right of any particular contextthe methodology is to go from right to left, bottom to top.  When menu items appear ​in related pairs or groupseg. "move to staff above" ​and "move to staff below" it is OK to glob them all together in one section unless particular of them have problems. ​ If all of this seems confusing, ​look below should make it apparent enough. +This was a good idea Chris had, but let's take it to the next level.  ​For the first phasewe're going to go through every menu in Rosegarden item by item, and create ​structure following ​this pattern:
- +
-The TOC in this document doesn'​t like having major editors as H1 headings, so I had to adjust everything to make the TOC sensible.+
 <code docuwiki>​ <code docuwiki>​
-===== Major Editor (eg. Notation, Main Window) ===== +====== Major Editor (eg. Notation, Main Window) ​====== 
-==== Top Level Menu ==== +===== Top Level Menu ===== 
-=== Menu Item === +==== Menu Item ==== 
-== Menu Sub-Item == +**BUG** 
-**Menu Sub-Sub-Item** (not enough levels of headings to make that work out)+**Observation** 
 +=== Menu Sub-Item ​=== 
 +[[dev:​major_sub_structure|Link text...]] 
 +== Menu Sub-Sub-Item ​==
 </​code>​ </​code>​
-While going through the interface, bugs are noted as **BUG** inline in the comments. ​ These should be collected and copied to the  +It is OK at this stage to group very similar functions under one heading, ​eg"​Move ​to Staff Above" ​and "Move to Staff Below" ​can become "Move to Staff Above/Below" and so on.
-[[qt4_bug_tracker|bug tracker]] page.  ​It is acceptable to wait and copy them straight to the "bugs now fixed" section ​at the bottom if they are trivial bugs to hammer out. +
- +
-As one thing leads to another, major sub-features like the guitar chord editor, the control rulers, and so forth will get their own H2 level sections with links from the relevant sections in the menu item by item documentation. +
- +
-This is going to be a huge pain in the ass to finish and do as well as what I've restarted here in the Notation section below. ​ Seems like maybe Julie, Chris and Ilan are all anal retentive enough to help out with this and be thorough and methodical enough to make it worthwhile. ​ Any takers? ​ We could divide up and work on different sections in the same fashion as what I've begun here.  Then somebody could go back through and pull out all the **BUG** notices. +
- +
- +
- +
- +
- +
- +
-===== Notation Editor ===== +
- +
-Feature review by menu, bottom to top, right to left.  If no comments appear for a heading, ​everything is working fine. +
- +
-==== Help ==== +
-=== About Qt === +
-=== About Rosegarden === +
-=== Guidelines === +
-=== Tutorial === +
-=== Manual === +
- +
-==== Tools ==== +
-=== Step Recording === +
-It took a bit of jiggling ​to get this to work, but I think it's OK now that I've saved a working MIDI input setup in my default studio. ​ In spite of getting rid of the stupid ​"current? Y/N" ​problem (the answer is YES DAMMIT now) we still don't have working MIDI recording out of the box on my home setup, because there'​s only one input device, and it's not connected ​to anything at all out of the box. +
- +
-This is one thing where I might consider the opposite approach from the one I've been going on about on the playback side.  There'​s not much harm I can think of creating devices for every available RECORD device, and hooking them up out of the box.  (Whereas doing this on the PLAYBACK side is completely EVIL.) +
- +
-=== Grace Insert Mode === +
-Seems to be working a well as always. ​ There are still problems with ledger lines and grace notes. ​ The note heads are scaled down, and so are the lines, so if you have a grace with ledger lines adjacent to a full sized note with ledger lines, they don't sync up at all.  It might be worth taking a quick look at fixing this one before February, because it has irritated me for a long time, and it might not actually be that difficult to solve. ​ I'll try to look into this shortly. ​ But anyway, definitely working well enough to release with as far as my experiments have shown (and a vast, VAST improvement over the old grace note tool that was utterly worthless). +
- +
-=== Triplet Insert Mode === +
-Even works in combination with grace mode.  Good stuff. ​ There are assorted well-documented age-old problems with triplet spanners and whatnot, but none of that impacts release. +
- +
-=== Chord Insert Mode === +
-**Observation:​** I tried do-re-mi keys and toggling H to enter chords followed by single notes followed by chords, and it all worked well. +
- +
-=== Insert Rest === +
-=== Insert Note === +
-== Do Re Mi == +
-I did not test every combination,​ but I've been through this pretty heavily while working out the problem with C and B and so on in the Romance language translations. ​ That all works now, and I think it's all in good shape, but I must admit I did not test this thoroughly. +
- +
-**Observation:​** We really need to make up some keyboard maps à la Open Octave Midi and publish them somewhere. ​ Even link to them from inside the GUI by way of web links or something. ​ Doesn'​t necessarily have to be done to release, but it would be very nice of us. +
- +
-=== Durations === +
-== 1 2 3 Y . == +
-This all seems to be working, but I did not test methodically this time around, and breakage **may** have crept in somehow since we were hammering on all of this a few months ago.  Probably hasn'​t,​ but I'm admitting the lack of testing for the record. +
- +
-=== Guitar Chord === +
-[[dev:​qt4_feature_review#​guitar_chord_selector|See...]] +
- +
-=== Text === +
-**BUG** No Help link +
- +
-I reviewed the behavior not long back and fixed the text background, resizing problem,and so on.  I have not done a fresh review, but at a glance it seems to be in the state I left it in, and well-behaved enough for release. +
- +
-=== Symbols === +
-=== Clefs === +
-=== Accidentals === +
-=== Erase === +
-=== Draw Notes and Rests === +
-I keep feeling like there'​s something still vaguely quirky about all of this, but I can't pin anything down at the moment. +
- +
-=== Select and Edit === +
-Works generally with the caveat that selections between the edit view and any associated ruler are buggy. +
-[[dev:​qt4_feature_review#​TBA|See...]] +
- +
-==== Move ==== +
-=== Transport Controls === +
-I won't go through these one by one.  They seem to be working. +
- +
-=== Next / Previous Segment === +
-Not working, or has no meaning in the current testing context. ​ **REVIEW** +
- +
-=== Next Staff Up Down === +
-The [[dev:​qt4_feature_review#​TBA|Track Header]] blue outline moves responsively as I would expect. +
- +
-**BUG** The playback/​insert cursor stays anchored to its original spot +
-**BUG** I had a whole staff selected. ​ When I moved up and down from there, the selection remained +
- +
-Entering with do-re-mi keys follows the blue track header outline. ​ After entering the first note in this fashion, the two bugs above correct themselves. +
- +
- +
-=== Clear Loop === +
-**BUG** This should use action states. ​ If there is no loop to clear, this should not be enabled. +
- +
-If a loop is set manually, this does work. +
- +
-=== Set Loop to Selection === +
-Obeys "have selection"​ action state. +
- +
-**BUG** Does not function! ​ (Missing slot?​) ​ **NOTE** I am testing in a multi-staff view +
- +
-=== Cursor Back / Forward ​and Select === +
-**BUG** Does not function! ​ (Missing slot?) +
- +
-Dubious icons. ​ I'm not sure about these, but I think I like them better than I did the last time I looked at them, so maybe we should leave well enough alone there. ​ (Or remove this feature if it won't be made to work again.) +
- +
-==== Adjust ==== +
-=== Visibility === +
-== Make Invisible / Visible == +
-Works. +
- +
-**BUG** the recolor code is making a mess of the note glyphs. ​ Invisible notes get fat as all their whispy peripheral pixels of very light opacity all seem to take on the same alpha level This looks shitty. +
- +
-== Fine Timing == +
-**Jog Left / Jog Right** +
- +
-== Fine Positioning == +
-**BUG** Something is going wrong with **symbols** and the "have selection"​ action state. ​ If I select only a segno or coda, the "have selection"​ does not go active, and I can't reach anything on the **Adjust** menu.  This applies to **lyrics** and **slurs** too.  Basically everything I have tried to fine position that should be capable of moving in any arbitrary direction refuses enable the **Adjust** menu.  **SERIOUS BUG** +
- +
-**BUG** The menu items work, but in practice you usually hold **shift** while clicking and dragging something to fine position it.  This is **broken**. ​ **SERIOUS BUG** +
- +
-== Velocity == +
-**Increase / Decrease Velocity** +
-  **CANNOT BE TESTED** / **NO VISUAL FEEDBACK** ​ In a **multi-staff** view, the velocity ruler is completely blank, and the raw note ruler is just showing a bunch of black nothing+
-  ​**Observation** For the sake of sanity, logic, and reason, it may be a good idea to disable all property and control rulers in multi-staff/​multi-segment views.  ​I have not looked at Classic during this test, but I remember looking at Classic while considering this point fairly recently, ​and I recall that Classic made a complete mess of this.  It's a mind bending problem trying ​to decide how it should behave, ​and I think disabling it is a fair option ​to consider. ​ Want to use the rulers? ​ Do it segment by segment Worth discussing!+While going through the interface, bugs are noted as **BUG** inline in the comments.  ​These should be collected ​and copied to the [[qt4_bug_tracker|bug tracker]] page.  It is acceptable ​to wait and copy them straight ​to the "bugs now fixed" section at the bottom if they are trivial bugs to hammer out.
-**Set Event Velocities ** 
-This dialog looks frigged up.  Either something is missing or its layout is much taller than it should be. 
 +===== Major Editors =====
 +[[dev:​thorn_main_window_review|Main Window]]
 +[[dev:​thorn_notation_review|Notation Editor]]
 +===== Major Interface Elements =====
 +Rulers? ​ Not sure yet.
-===== Guitar Chord Selector ===== 
-==== Choosing and Inserting Chords ==== 
-Choosing chords and inserting them into notation works generally. 
-**BUG** Something is wrong with the highlight colors. ​ The highlighted fretboard has a different background from all the other highlights. ​ May be a style problem. 
-==== Editing Chords ==== 
-Seems to work and look rather better than it used to. 
-**BUG** From fret 5 onward, the little blue hover cursor does not show up, and it isn't apparent you can click to make a dot appear. 
-=== Deleting Chords === 
-Not very apparent which ones can be deleted and which ones can't, but the "​Delete"​ button does cycle enabled states appropriately,​ and this does seem to work generally. ​ General improvement might be indicated long after more pressing matters are dealt with. 
 ===== Tail ===== ===== Tail =====
dev/qt4_feature_review.1258336808.txt.gz · Last modified: 2018/02/07 17:07 (external edit)
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki