Feature Request: Build yak package w/o RUI file

With the R8 ScriptEditor’s “Build Package” functionality, an RUI (toolbars) file is always added to the yak package. Please give us an option to disable this.

Background: In our company, we deploy about 4 or 5 different yak packages that are developed by different people, and in different programming languages. One of our packages is solely concerned with distributing our 2 toolbars, and to provide a consistent workspace. It takes care of our toolbars, icons etc.
Unless the developer provides icons for each of the commands in their plug-in, the RUI file ends up with just plain ‘grey box’ icons. The user then has to disable them.
Admittedly, our deployment scenario is rather niche. However, being able to build a Yak package w/o the RUI file might have benefits to other deployment scenarios, too.
I am aware that a Yak package is simply a Zip archive, and that it is possible to programmatically extract the RUI from it. But this is not the same as building the Yak package w/o the RUI in the first place. Some of our developers simply wish to distribute RS Python packages for their team members, and don’t want to go through the process of rename .yak to .zip, deleting the .rui, and then renaming back from .zip to .yak.
Thank you for considering this.

Upvote for this.

My ideal would be to specify my own RUI rather than the default, I’m constantly doing the rename to .zip and copying in my own custom .rui.

Cheers

DK

@eirannejad

I have a couple of other suggestions as well.

What I might do is send you a video of my current workflow with all the “extra processing” I do after I create the YAK and before I upload to the package manager.

Currently the Script Editor tool chain is awesome, but is not idealized for a professional Grasshopper to commercial plugin workflow.

Cheers

DK

Looking forward to it and it is a great time to have this feedback so I can implement for Rhino WIP