For me I would have my monitor 1 with a MD at the bottom ,and ready for the PRv or loop construction view inside it , Monitor 2 I would have the Console view with a MD at the top and all my plugins nestled in there. Thats one way I would set it up..

Of course multiple docks would require some tweaks to keyboard navigation. 

I'm so-so about it. If it existed I'm sure I'd use it. After all Adobe apps and Vegas and the like have an almost infinite amount of palette dockability with each other. 

And even with the Multidock, I often break plugs out so I can keep them "always up" in a corner while I work. 

Screensets and me are still dubiously circling each other. I get large pauses when switching..sometimes it even hangs. I think I'd actually prefer assigning individual plugs to the num keys so you could pop a specific plugin to the front with one keystroke. 

+1!

multiple monitors + multiple docks = better workflow (for me!)

I think I'd actually prefer assigning individual plugs to the num keys so you could pop a specific plugin to the front with one keystroke. 

Thats Not a Bad Idea..  

 I think every launched window/module/button/fader/switch ect should have the ability for a midi learn. A: this will allow for us to build a custom console/controller with no programming knowledge needed , A simple learn and save. no more MMC mode or mackie mode no more throwing out old midi controllers if its midi hardware it can be used on any feature in Sonar. That would hold same for touch screen to.. 

To split modules into groups so that you don't need to click through tabs if you have a bunch of them in there. 
 
John

Wow, it's weird reading things I wrote so long ago!
That said, I truly miss SAW+. It had the most dirt-simple "screenset" implementation evar. SHIFT+F-key saved a layout, F-key recalled it. No lag, no crashing. And it instantly allowed 12 layouts of EVERY THING. Screensets now, even like I wrote all those months ago, are buggy as heck. They lag, they hang, they are just a total pain. Plus the weird "you don't have to save" BUT "you have to be IN the new screenset when you edit" is completely backwards. 
 
All that said, the obvious definition is: plugin UIs in one tabbable window, different editing views in the other. It's extremely obvious, even WITH inline PRV (never use btw), console view (also never use, get over it, it's a dead medium for folk who can't let go of physical hardware...and I say that having learned on them), and all the other views. One last thing: MAKE THE PRV ABLE TO ROTATE 90 DEGREES! Studio One can do it, and it makes ALL the difference learning parts since a piano keyboard goes left to right, not bottom to top. 

...wicked
One last thing: MAKE THE PRV ABLE TO ROTATE 90 DEGREES! Studio One can do it, and it makes ALL the difference learning parts since a piano keyboard goes left to right, not bottom to top. 

While that may better simulate  a real player piano, I'd find it pretty weird to have horizontal chords and notes moving vertically.

Yah, though I wouldn't be surprised if it was easier to acclimate to than you think.
 
But, I don't play through projects in the PRV anyway, I edit there. I'll play little bits over and over. one of the major streamer programs IIRC goes top-bottom instead of left-right.
 
I like the idea because it makes it way easier for me to figure out parts. I suspect younger folk will like it because Rock Band and all those games work in a similar fashion.