Another idea for a better staff view: to wit, Cakewalk publishes an application program interface (API) into Sonar and lets 3rd party developers build a better staff view. While they're at it, 3rd parties could engineer a new script engine and add other UI features that we don't even know we desperately need (until we see them in action). I'll bet some of those 3rd party developers are members of this forum. (Heck, I had my own custom macro interface hack communicating with a version of Pro Audio many moons ago.)
CW has already opened up the ProChannel API to 3rd parties, enticing them to write PC-friendly plugins. And of course, there are all sorts of supported hooks for hardware interfaces, so a set of hooks into the Staff View for custom apps doesn't seem so far-fetched to me. (Of course, a fully-functional SV doesn't seem far-fetched to me either, so shows what I know....)
So, four strategic-direction suggestions so far for Cakewalk:
1) (Current) CW repeats its intention to do something about SV someday.
2) CW "enhances" staff view as part of the Sonar package, to make it as effective for note manipulation as piano roll view.
3) CW sells an add-on SV module (call it Sonar Staffworthy Edition). I'm buying (as are others in this thread).
4) CW publishes a set of hooks into Track view for 3rd parties to add other views, staff included, or widgets or "apps" or whatamacallems.
5) (Ooops, over my limit.) Okay, wild and crazy, but maybe CW open-sources the Staff View code and lets users have at it. Lots of dots to connect here, but this is a dream thread, right?