"Face Group" / "Group Index" / "Face Set" concept naming #102962
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#102962
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Options
Note: "Face Map" is currently used in Blender too, but I don't think that's a good name, so I won't consider it here
Face Group
Group Index
Face Set
The name could generalize for multi-domain cases like "Set Index"
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @HooglyBoogly
Added subscriber: @mod_moder
I don't see a problem in
...
Index is a lot unifed one
And group is no has specific of random domain. It more general
Added subscriber: @lone_noel
Added subscriber: @Caner-Aslan
"Face Group" feels like the right one.
Added subscriber: @Kuboa
Added subscriber: @wannes.malfait
I prefer
Face Set
, exactly for the reasons described. You want to have the same concept for vertices, but thenVertex Group
would be a problem if we went withFace Group
, so I really don't see that as an optionright, cheers to the name father/mother of vertex group :) , what about "face group index", too long?
Compared to the simplicity of "Face Set", I do think "Face Group Index" is a bit long. Personally I also prefer
Face Set
.I think we would use "Edge Set" for the edge rings node (D16471), but I can't think of anywhere else we would use this naming immediately.
no problem, I will get used to it.
This comment was removed by @Kuboa
Added subscriber: @JacquesLucke
Some context the the screenshot above-- we discussed this in a few meeting. Mostly we agreed that either "Set" or "Group" would work okay.
"Group" won out in the end since it maps a bit better to the "Group ID" terminology which is a natural socket name that shows it's an integer,
the order doesn't matter, and it should be the same for many faces. "Set" also had the disadvantage that it sounded like the "Set" nodes.
The largest downside of "Group" is that it sounds a bit like vertex group. The extra "ID" word used on many sockets should help show a difference.
I could still see us running into that problem in the future. And I do think that similarities with "Set" were much better than the similarities with "Vertex Group".
So now I'm second guessing this again (!), but in the interest of moving forward and not bike-shedding I will commit the renames above.
Added subscriber: @Bradley_G
I think "Group ID" is generally a very good idea. This idea can be generalized to many different domain/nodes, instead of being a concept that may be used once only.
As for name similarity with "Vertex Group", I wonder whether it can possible to rename vertex group into things like "Vertex Set" or others?
Although it's called group, essentially it's just boolean. In GN, we most often just call them "selection", in which demonstrates "vertex group" may not be a good name in the first place.