Agree on point or vertex for domain name #86821

Closed
opened 2021-03-22 14:54:03 +01:00 by Dalai Felinto · 8 comments

Arguments towards point:

  • For nodes like Attribute Convert and Attribute Fill having a single domain for point cloud/voxels/vertices.
  • We already use points for a lot of nodes.
  • It is strange to refer to the same thing (point) as two different things. (however the same can be said about edit mode vertices and "geometry" points).

Arguments towards vertex:

  • Vertex is something users are already familiar with,
  • When we get (generic) attribute edit mode users will probably be seeing vertices as the domain.

An option is to show them in the spreadsheet as "vertex", but to show in the node editor as "point".

Arguments towards point: * For nodes like `Attribute Convert` and `Attribute Fill` having a single domain for point cloud/voxels/vertices. * We already use points for a lot of nodes. * It is strange to refer to the same thing (point) as two different things. (however the same can be said about edit mode vertices and "geometry" points). Arguments towards vertex: * Vertex is something users are already familiar with, * When we get (generic) attribute edit mode users will probably be seeing vertices as the domain. An option is to show them in the spreadsheet as "vertex", but to show in the node editor as "point".
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Author
Owner

Added subscriber: @brecht

Added subscriber: @brecht
Author
Owner

I talked with @brecht and I'm still not convinced about using points. More arguments towards vertices:

  • For Volumes and Point Cloud the Attribute Convert and Attribute Fill nodes can make it do with the "Auto" option.

For me the main argument towards point is the Point nodes (Point Rotate, Point Scale, ...) existence. Though not necessarily a deal breaker.

I talked with @brecht and I'm still not convinced about using points. More arguments towards vertices: * For Volumes and Point Cloud the `Attribute Convert` and `Attribute Fill` nodes can make it do with the "Auto" option. For me the main argument towards point is the Point nodes (Point Rotate, Point Scale, ...) existence. Though not necessarily a deal breaker.
Author
Owner

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Author
Owner

After further debate with @JacquesLucke we settle on the following:

Proposal:

  • Spreadsheet editor (and custom attributes in the future) to use the specific name Vertex, Voxel, ...
  • Node editor to use Point

Design:
We have the more specific names where there is more context (spreadsheet editor and other places).

Rationale:
We use vertex everywhere but nodes editor. So we make the spreadsheet editor comply to everywhere. And leave the node editor to be the place where we make the distinction of the domains.


Jacques will make a patch for that.

After further debate with @JacquesLucke we settle on the following: **Proposal**: * Spreadsheet editor (and custom attributes in the future) to use the specific name `Vertex`, `Voxel`, ... * Node editor to use `Point` **Design**: We have the more specific names where there is more context (spreadsheet editor and other places). **Rationale**: We use vertex everywhere but nodes editor. So we make the spreadsheet editor comply to everywhere. And leave the node editor to be the place where we make the distinction of the domains. --- Jacques will make a patch for that.

This issue was referenced by 1f2a801044

This issue was referenced by 1f2a801044ac77a5371fbea3bdc2cf3c4258954f
Author
Owner

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Dalai Felinto self-assigned this 2021-04-26 12:19:01 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#86821
No description provided.