I have a hard time to imagine editing Subdivision surfaces as shown above, that’s why I thought one should bring up this topic early in the process. The reason is quite simple: I know for sure that one can take care of all of these parameters inside SubD apps, without a lot of GUI and modal queries and in a fraction of the time one needs to read and understand the above text. For me it clearly is one of the most attractive attributes in mesh modelling that one as a user may keep on going forward at all time.
Maybe the initial outcome of a certain operation is not yet what one originally meant to do… but that realistically also happens all the time in Surfacing too. In contrast to polysurface editing however, the whole volume remains fully editable at all time. That’s actually a huge difference! It therefore is perfectly in order to approach a Subd shape iteratively and to give the nurby control freak who’s keen on exact numbers and angles a break – at least for early concept development, where SubD shines.
The last paragraph however wasn’t meant to say that one should leave control away, not at all. The following is an unordered mix of own suggestions and principles found inside applications other than Rhino. I think some of them were worth looking into in order to make modelling with meshes inside Rhino as playful, dynamic and full of happy accidents as it can be. It’s about command flow / commandline options, custom UI widgets, Keyboard bindings and further stuff of that nature. My idea is not that you guys cram all of this into Rhino (chances were meager anyway) some of these options also overlap or even kinda contradict each other – it’s essentially just a big bag of ideas.
As it would have taken a lot of additional time I leave away most illustrations for now. If something isn’t clear let me know and I’ll record a gif. One might notice that Buttons and Toolbars don’t apeary anywhere, simply as I rarely use them in any program.