Re: 
Returning to the topic of menu bar verbosity. Maybe you can remove these “toggle walls”:
The left icons already make apparent that they are toggles. And the Toggle in front of every item make these menus quite hard to read (IMO) and unnecessarily wide.
Hi @eirannejad (and @DavidRutten, I think). I just updated the WIP and noticed that the G2 scripting components have these new access indicator dots. I’m sure that’s probably helpful to some users, but I find them quite verbose and distracting (as per the general design observations made here). Is there an option to turn these off? If not, it would great if you could add one. Also, the G2 scripting components are wider than their G1 counterparts (even without the access indicators). Here’s a 1:1 comparison of a current project component:
But that added width is probably a general G2 component design choice. Anywho, something to consider.
I agree with that. It is visually distracting, Please consider it as an optional feature.
It’s looking fantastic! I will stop pestering you about every little design detail now. Also, zen mode is brilliant:
Thanks so much Ehsan, looking forward to many more years of scripting stuff in Rhino 
Edit: Sorry this was actually in Rhino 9 Grasshopper 1. But guessing it’s the same in G2.
You are most welcome. Thanks for being patient 
I pretty much rewrote all of the editor so now I can actually fix the bugs that were incredibly complicated to fix before. This rewrite affects all the script editors.
I wanted to name it Anders Mode, but you know…
I am sure there is a new collection of bugs now and I will be cleaning and polishing those in the coming weeks
No worries, I highly appreciate the tenacity you guys have for full rewrites. And for dealing with the inevitable annoying feedback from oldhat sticklers like myself when things are different/don’t work 
Hahaha, sorry. It is really nice though! As are the new icons.
I had some issues with the general settings not sticking, but can’t seem to reproduce that now. And certain toggles don’t appear to toggle too well (e.g. the minimap). I’ll report back when I see a pattern.
Okay, I lied, just one more for old times sake. And then I swear I’ll stop! Going from:
To:
Where I’ve made these minor edits:
With the left/vertical border being the most notable, especially when zoomed in:
Where I’ve changed the two pixels on the right of the vertical border (i.e. the grabble ones with the hover over state) from Rhino.UI.ThemeSettings.Frame.Edge to the same as the center/horisontal one:
I can certainly also see how one might like having the top left icon (i.e. like the old C# component). It just kinda clashes with my personal setup (i.e. no main window title bar + Grasshopper 1 + GhPython do not have icons):
But again, Grasshopper 2 has the icon and it really is a very minor annoyance. So no biggie.
Edit: Also, these tabs got substantially taller than they were e.g. back here:
I see how this was pretty confusing. In the latest update all borders use Rhino.UI.ThemeSettings.Frame.Edge:
Meaning we get borders with 3, 2, and 1 pixels widths when collapsing the left panel:
IMO this looks weird/unintentional, especially when using a darker color like here. Which could be fixed by using Rhino.UI.ThemeSettings.Content.Background for the two 2 pixel wide interior borders (i.e. similar to the horisontal interior border in the previous release):
(
)
Hi @eirannejad, to minimise friction I took the plunge and started using Visual Studio Code instead of my old trusty Sublime Text (i.e. outside of my Rhino coding). And I actually really like it, once I turned off all the AI/Microslop. Anywho, I’m not sure how much can be applied 1:1 to the new script editor. But here are a couple of the settings that really helped make things feel more GhPython-like:
"editor.trimAutoWhitespace": false (stop the editor automagically deleting intentional white space)."python.analysis.extraCommitChars": true (allows one to autocomplete with brackets, fixing this)."python.analysis.completeFunctionParens": true (adds brackets when autocompleting with tab/enter).It would be great if you can implement these in the new script editor.
Edit: Upon further testing, 2. and 3. appear to conflict when both are true. I’d use just 2.