Starting with the 2014-01-28 WIP release, Rhino for Mac now uses a single window with sidebars for performing modeling. An earlier version of this modeling style has been available through the TestSingleWindowModeling command, but this is now the default.
There are currently unresolved issues with single windowing layout in 10.7, so single window modeling is currently disabled on 10.7.
There is an earlier post about other single window modeling features.
This version has a number of new features to single window modeling that are available through settings in the Themes preference panel.
You can now display a tool palette of your choosing above the viewport views. You can create your own tool palette (of course) and populate it with as many tool buttons as you like. The top tool palette will use as many rows as necessary to display your tool palette, and will resize as you resize your modeling window.
The left sidebar is the Command sidebar and contains a tool palette. If you are not using the ribbon bar, you can choose which tool palette is displayed here. The ribbon bar dynamically changes which tool palette is displayed in the sidebar, so this option is disabled when using the ribbon bar.
Another setting lets you place the Osnaps panel in the command sidebar. If you have a smaller laptop, you may want to turn this option off.
By default, the options for the running command are now displayed in the command sidebar. As before, just start typing to type a command. No need to click in the Command box before typing a command.
If you prefer to use the Command Options HUD panel instead of having the command options in the sidebar, select the Custom theme in the Themes preference panel and choose the “Use command options dialog” option.
Both sidebars can now be sized narrower than in earlier versions, allowing for more modeling space in the middle of the window.
Some of you will want the old UI back, and, for a short period of time, you can do this. The command mentioned in the Discourse post, TestSingleWindowModeling, will now autocomplete and will revert to previous UI versions. This is only a temporary condition. The TestSingleWindowModeling command will disappear in the near future, and the new UI will be the only option.
I will suggest that reverting to the old UI only be done as a last resort. It has been a challenge to keep the previous UI versions running correctly while making the new UI changes. If I have introduced minor problems to the old UI versions, they probably won’t be fixed. Also note that the old UI versions are going to be abandoned and removed after the TestSingleWindowModeling command is removed.