RE: [platform-ui-dev] [Editor Mgmt] Make EditorManager$Editor adaptable

["Tsai, Philip" <Philip.Tsai@xxxxxxxxxx>]

 Hello Eduardo,

 Thanks for the detailed message on this.  I prefer the drop-down approach that shows the most recently vested editors -- with the drop-down locates next to the list of editor tabs.  

 I find the current "< >" linear-scrolling next to editor tabs quite ineffective -- one typically develops by going through related classes at once to aid the understanding of architecture and class-logic.  To use the "< >" mechanism to aid efficient development implicitly requires one to visually remember which file belongs to which tab.  When developers are focused on code logic, their minds and attentions should not be distracted by that, though.  The current alternative of hovering over a tab to know the complete filename -- in the case that many tabs are open and names partially hidden -- is time-consuming, detrimental to efficient development.

 The Editor Dialog is also inefficient in that it presents too much information and required a few too more clicks in order to reach the desired destination.
I simply don't use it.

 The Ctrl-F6 stack-based approach is neat -- frequently holding down Ctrl keys for a few seconds each time, though, is detrimental to users' finger health.

 Jared's Viewer is nice in that its arrow buttons allow one to navigate recently visited tabs.  It has some bugs, though, and takes more UI real-estate than the drop-down approach.
 
 In the perfect world -- in the case that you wouldn't want to ditch all previous efforts: it is nice to allow users to configure what to show next to editor tabs:  1) "< >" for users that tend to open disparate or few editors at once,  2) "drop-down of the view shown through Ctrl-F6" for users that develop in quick-succession mode.  This improvement in Editor Management looks minor yet generates big potential for more developer-addiction to Eclipse.