Hi Rhino developers,
I think the Rhino layer system needs to be upgraded.
I don’t know if you ever looked at the Vector Works layers architecture.
In VW it is possible to assing a class to a specific layer or group of layers.
Please watch this video to understand the possibilities of classes:
Thanks.
no video?
I was looking for the video too… 
Are you using user attributes in Rhino?
I saw a video about classes and was thinking the same.
Don’t understand the connection between classes and layers, for me they are different… but could be I don’t get gabrielefx’s request…
This is interesting and a similar system can be created with user text. Same is in the example in the video, some curves would be in a layer ‘crv’.
Each curve has a user text key called ‘color’ and whatever value.
It’s easy to filter the content with Grasshopper. In plain Rhino, it would be a bit of a back and forth to select the content by user key and value…
In Vectorworks its slightly different from Rhino, in VW Design Layers are usuallly the ‘where’ , symbols and objects are the ‘what’, I’m sure others have their own take on it but thats what I was taught. VW also has Sheet Layers, its a different methodology from Rhino.
Oops! I forgot it:
Probably this video explains what I want to achieve.
I’d like to have a panel (like the layers) where I can turn on-off various elements which are parts of a specific class.
Thanks to the Marting suggestion I was able to simulate what I’d like to have in Rhinoceros.
Let’s say I want to model 10 building elevations. Each elevation has walls, windows, railings, stairs, etc.
I create one layer for the 3d walls, one for the 3d floors, one for the 3d windows, etc.
Now I want to subdivide each elevation to a class/name: floor 01, floor 02, floor 03, etc. and switch on-off each class/layer.
Hi,
I’m also struggling organising file in Rhino. Right now it’s not possible to work on several plans for exemple Plan 0, Plan +1, Plan +2 without duplicating a lot of layers.
If you have these 3 plans made with a lot of layer describing all the element of construction. For exemple; Construction>Door frame, door handle, screw, etc…
Then, it means that you have to duplicate all this layer structure three times for the three planes if you want to be able to manage these three planes separately, make them appear or not in the layout, superimpose them to check things, etc…And then if you want to change something for the doors, even just the colour, you have to change it three times etc. without ever finishing.
It’s true that Vectorworks has this structure of classes and layers that provide a second organisational level and allow entire parts of the model to be displayed or hidden, or variants to be created and managed in the layout.
I tried once to work with groups, you can name them, but it’s difficult to select them and then say you want to hide or show different groups in the layout. A group panel and the ability to manage it in the layout might be a solution.
For the user text, I’m not sure it’s possible to control that from the layout either, is it?
Add user text attributes to your objects and use these to filter your content.
Thanks for your feedback, I’ll give it a try!
But is it possible to hide/show objects with the user text attribute in a layout detail? And in another detail and layout hide/show differently?
That might be challenging.
There’s a command called _HideInDetail
Command: HideInDetail
Must have a detail viewport active to run this command
Then maybe this script could be helpful:
Hi Pip -
FWIW, instead of groups, you can work with named selection sets. That makes selecting the correct items easier than with groups.
You’ll still need to use HideInDetail…
-wim
@wim is there any progress on this topic?
Hi jsbzh -
I’m not seeing any outstanding action items in this thread.
-wim
Appreciate the update, Wim. If possible, could the team take another pass at this? I’ve gathered concrete AEC/renovation examples here that may clarify the need: Rhino 9 Wish List - #51 by jsbzh and this Rhino 9 Wish List - #60 by jsbzh
Rhino 9 Wish List - #76 by Ctrh
To make the case stronger, here is a brief, practical explanation of why this matters in daily AEC work. In renovation projects, and in new-build projects too, we must show phases and program clearly across plans, sections, elevations, and axonometric views. We use different colors and line attributes (linetype, lineweight, hatches/fills). Rhino has these tools—great—but we are missing a clean way to organize them. In many places, these conventions are required for permitting.
We also need to handle furniture, appliances, and planting across those phases with the same attributes to communicate use/program changes. This may sound odd, but it’s very important for making the case—and often getting approval—for changes in a client’s building uses. Today the options are duplicating layer trees, and in named selections, or manual HideInDetail. (The last two are not practical at all!). These become slow and fragile when moving between design and construction drawings, with multiple people in the same file, and many layouts to print.
What would help is a second organizational axis next to Layers. The name (“Classes”, “Tags”, “Categories”) is less important than the function.
So here is the small, practical starting point:
I can share a small example file and screenshots via DM if useful.
If others run into the same issue, +1s and examples would help.
And btw, Rhino is fantastic for these kinds of projects because it combines 2D and 3D so well—that is why I am being persistent about this.
Edit: The title of this thread “Classes for layers” might be slightly misleading or imprecise.
This would be a huge improvement for rhino. 
Would also love to see this!