please!
Bump on this one. I’m guessing there won’t be a native RCP replacement for a while (if ever). So any small edits you can make to the current one would be much appreciated. Cheers.
TLDR: Drop bold fonts + make all borders 1 pixel wide 
Double bump on this one 
Again, TLDR:
Also, it would be great to hear if there are ANY plans to continue native development on the Grasshopper 1 RCP (e.g. adding Gene Pool, Value List, Color Swatch, and an editable Panel, see first post from 2017)? And if Grasshopper 2 will eventually get an RCP? It’s been well over a decade with plenty of more or less usable third party Grasshopper GUI plugins, but I really much prefer native McNeel solutions (that doesn’t require me writing tons of e.g. ETO code, assuming that’s the only alternative currently) 
Edit: Ping @DavidRutten
Anders, do you have a small version of one of you RCP controlled scripts?
I would be happy to spend an hour or two to re-write this using DKUI - which allows for full control of the style via CSS. I would just ask that I be allowed to make and publish a video of the process as an example.
Please let me know if this would be of interest?
Cheers
Dk
I don’t use third party plugins/dependencies, unless strictly necessary. But thanks so much for the offer 
Eventually. It’s a big job and as GH1 showed, a lot of really bad decisions can be made in a short span of time. It’s currently not on the 9.0 stop ship list, so this will appear some indeterminate time after first Rhino9 ships, but it will be part of Rhino9 development.
That’s great news, thanks for clarifying this. Really looking forward to seeing what you come up with!
We’re probably quite a few years away from using GH2 in production (especially one with an RCP). So if at all possible, myself (and I think many users) would benefit greatly from just adding the Value List to the existing Grasshopper 1 RCP. Having drop-downs and check lists would improve things significantly. Anything else is just gravy, but of course styling also matters 
Fair enough @AndersDeleuran.
Though I would note that with the installation of DKUI - and many other 3rd-party plugins - now being 100% taken care of by the Rhino Package Manager, it’s MUCH less hassle than dealing with plugins in the past.
Having a rich and well-supported ecosystem of plugins, and opening your workflow up to the work of developers beyond just the McNeel team, is honestly one of the huge advantages of design and development in Rhino.
Cheers,
DK
Exactly this, the RCP is very simple and user friendly. But also, one can script it fairly easily (though this is limited and a wee bit convoluted). See for instance how I close/open the Color Scheme groups in the video example I posted up here.
Indeed, it’s much better now than back in the fully Food4Rhino days!
Having received many Grasshopper files from many architects/designer/engineers, I’m gonna have to (partially) disagree here. Opening a file and being meet with a wall of (mostly) unnecessary plugins/dependencies of more or less sketchy origins is a daily giant pain in the ass. And then there’s of course dependency hell, technical debt, versioning issues, malicious intent etc. I don’t enforce rules about when to use plugins at BIG, but I do provide this “best practice”:
Good use of plugins:
When the functionality provided does not exist in Grasshopper/RhinoCommon (e.g. Kangaroo prior to becoming first party).
Acceptable use of plugins:
When the functionality provided does exist in RhinoCommon, but is not exposed in Grasshopper (e.g. Elefront and parts of Human).
Bad use of plugins:
When the functionality provided does exist or is simple to reproduce in Grasshopper/GHPython/C# (e.g. parts of Pufferfish and Wombat).
My take on the “Grasshopper UI” plugin has been a minimalist one. For straightforward stuff, I put all of the functionality into a Rhino panel, which does not require any additional Grasshopper set up beyond labeling groups (which many people do anyway), which means you also don’t have to one-by-one publish things to the RCP, or define any UI controls.
It uses built-in Eto forms, does not require wiring up any Grasshopper components. It is actually a .rhp, so it doesn’t even have a Grasshopper component or become a dependency in your GH script.
It also has some features like creating a drop down menu based on your folder structure (like if you have a library of scripts in nested folders).
It’s not as fancy or rich as some of the other options, but I think spiritually it’s closer to the RCP.
There’s a dedicated thread about it here: Suimple: Automatically Create UI's from Grasshopper Scripts - #23 by Muhammad_Talha_Mufte
Looks great! Did not know about this.
Are you still developing it? From what I read from documentation, it works with the group named INPUT and OUTPUT, I use groups intentionally on my scripts so changing them is not ideal.
Would it be possible to still make it work by a right click menu option like RCP does?
Also would it be possible to re-organize the panels (in your image green, blue, red) by dragging and dropping on the window instead of by physically organizing the groups in the GH canvas?
That would be great!
I am still developing it, though so far slowly as I haven’t gotten a ton of feedback, but if there’s interest I am happy to take it further. Yes at the moment it does rely on group naming (it doesn’t have to be “INPUT” exactly, it just looks for any group name that contains the word ‘input’ or ‘output’, so you could do something like “Input: Wall Dimensions” and it would work).
I can have a look at your requests - the drag and drop is theoretically easy, though eto’s drag and drop I have found to be fussy. We could do something like, have a small Grasshopper element that is like “UI Group Index”, and you add that to your group to set the order, but then your GH file would now need the plugin as a dependency.
Anyway, I don’t want to pollute this thread, if you want to meet me over on the dedicated thread, I’ll have a look!
RCP Enhanced UI.gh (25.2 KB)
I used to make my own UI with RCP and some tricks. today I just asked AI to build it for me.
totally usable for me. ¯\_(ツ)_/¯
Thanks, nice set of examples. I’ve never used the RCP very much and this is a really helpful.
Turns out one might do it in less than 500 lines of GhPython:
Hi Anders, didn’t you post about this project example in ETO interface? I can’t find the post anymore. I thought it was a great example and it looked really neat actually!
