Differences

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
Next revision Both sides next revision
dev:qt4_feature_review [2009/11/16 02:56]
michael
dev:qt4_feature_review [2009/11/16 03:11]
michael
Line 4: Line 4:
 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 context, the methodology is to go from right to left, bottom to top.  If this seems confusing, a look below should make it apparent enough.+**NOTICE** DISREGARD ALL OF THIS FOR THE TIME BEING. ​ I have been thinking about what I started here, and before this gets too far out of hand, I'm going to go through here and refactor it, and all the instructions I wrote 10 minutes ago are null and void now. 
 + 
 +We'll do one page per major editor (what was H2 in the original) and we won't go in reverse order. ​ I'm going to flip all of that crap around before I go any further. 
 + 
 +What we're going to wind up with is a systematic and formatted list of all menu functions with review comments inline. ​ It's no far stretch to take that work, polish it up a little here and there, and turn the whole shebang into the beginning of a new **manual** from scratch, that won't leave anything out.  We can pull bits from the old manual into the new structure, and add copy to fill in all the holes (the original manual had a ton of comments about things that never ultimately got documented) and eventually wind up with a good piece of documentation out of all of this.  Of course I don't expect that to get done before February, but it's pointless to type all this crap without an eye toward getting the biggest long-term return. 
 + 
 +Stay tuned... 
 + 
 + 
 +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 context, the methodology is to go from right to left, bottom to top.  When menu items appear in related pairs or groups, eg. "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, a look below should make it apparent enough.
  
 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. 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.
 
 
dev/qt4_feature_review.txt · 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