blender
/
blender
128
396
Fork 568
Code Issues 6.2k Pull Requests 749 Projects 19 Wiki Activity

Separate ColorRamp node name into Color Ramp #104996

Merged
Daniel Salazar merged 4 commits from zanqdo/blender:color-ramp-node into main 2023-03-24 05:00:14 +01:00
Conversation 4 Commits 4 Files Changed 5 +11 -11
Daniel Salazar commented 2023-02-21 00:11:13 +01:00
Member
Copy Link

Node names should be properly separated for easy searching and reading
and for consistency with other (color) nodes.

Reasoning:

All other nodes are already named separately.
image

Even the manual names it separately
https://docs.blender.org/manual/en/latest/modeling/geometry_nodes/color/color_ramp.html

There are also internal mentions to Color Ramp inside Blender operators and tooltips.

Note:This patch should only touch UI names which do not need versioning.

Node names should be properly separated for easy searching and reading and for consistency with other (color) nodes. Reasoning: All other nodes are already named separately. ![image](/attachments/0848b3ca-d551-4a16-a066-42d3663991a7) Even the manual names it separately https://docs.blender.org/manual/en/latest/modeling/geometry_nodes/color/color_ramp.html There are also internal mentions to Color Ramp inside Blender operators and tooltips. Note:This patch should only touch UI names which do not need versioning.
image.png
12 KiB
Daniel Salazar added 1 commit 2023-02-21 00:11:23 +01:00
4b7c3799c1 Separate ColorRamp node name into Color Ramp 
Node names should be properly separated for easy searching and reading
and for consistency with other (color) nodes
Iliya Katushenock commented 2023-02-21 12:28:46 +01:00
Member
Copy Link

It seems strange to have such a name in the interface, but for the names of all functions and comments to stick together. Are we sure it's definitely not just one word?

It seems strange to have such a name in the interface, but for the names of all functions and comments to stick together. Are we sure it's definitely not just one word?
Hans Goudey commented 2023-02-21 14:18:41 +01:00
Member
Copy Link

The reason we hadn't changed these is that they do influence how nodes are accessed in the Python API. The node names will be different, and those are used as identifiers. See #102607 and #96219.

For planning it also makes sense to group a bunch of name changes and reorganizations into one release, that makes the change easier to learn.

Not sure if this matches the opinion of others, but I think it's where we ended up when we talked last.

The reason we hadn't changed these is that they do influence how nodes are accessed in the Python API. The node names will be different, and those are used as identifiers. See #102607 and #96219. For planning it also makes sense to group a bunch of name changes and reorganizations into one release, that makes the change easier to learn. Not sure if this matches the opinion of others, but I think it's where we ended up when we talked last.
Daniel Salazar added 1 commit 2023-02-24 22:26:52 +01:00
Daniel Salazar added 1 commit 2023-02-25 02:41:23 +01:00
Hans Goudey commented 2023-03-21 16:03:19 +01:00
Member
Copy Link

Looking at this now, it's clear that the change would be fine, since it only affects the names (not the identifiers). Is this marked as WIP for any particular reason? Otherwise I would accept it.

Looking at this now, it's clear that the change would be fine, since it only affects the names (not the identifiers). Is this marked as WIP for any particular reason? Otherwise I would accept it.
Hans Goudey added this to the Nodes & Physics project 2023-03-21 16:03:30 +01:00
Daniel Salazar changed title from WIP: Separate ColorRamp node name into Color Ramp to Separate ColorRamp node name into Color Ramp 2023-03-22 00:58:46 +01:00
Daniel Salazar commented 2023-03-22 01:02:53 +01:00
Author
Member
Copy Link

Looking at this now, it's clear that the change would be fine, since it only affects the names (not the identifiers). Is this marked as WIP for any particular reason? Otherwise I would accept it.

I've removed the WIP tag, should I do the same for?:
#104998
#104999

> Looking at this now, it's clear that the change would be fine, since it only affects the names (not the identifiers). Is this marked as WIP for any particular reason? Otherwise I would accept it. I've removed the WIP tag, should I do the same for?: https://projects.blender.org/blender/blender/pulls/104998 https://projects.blender.org/blender/blender/pulls/104999
Hans Goudey approved these changes 2023-03-23 15:30:37 +01:00
Daniel Salazar added 1 commit 2023-03-24 04:56:07 +01:00
Daniel Salazar merged commit c971adfeef into main 2023-03-24 05:00:14 +01:00
Daniel Salazar deleted branch color-ramp-node 2023-03-24 05:00:14 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Hans Goudey
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Nodes & Physics
Assignees
Clear assignees
No Assignees
3 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#104996
No description provided.
Delete Branch "zanqdo/blender:color-ramp-node"

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?