Comfy-Org / Comfy-Org/ComfyUI_frontend
[UI/UX]: Rename CLIP inputs/outputs/node names as TE inputs/outputs/node names on the frontend-side
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 699
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 490
Description
# Intro
ComfyUI was made back in the day when the only (prominent) local models at the time used CLIP as a TE, here, it made good enough sense to call CLIP inputs and outputs as CLIP. However now, the name is entirely inaccurate and it is obvious that naming these inputs and outputs CLIP was not good at all for future-proofing. Sure, some models like SDXL and Flux use CLIP as their TE(s), but the latter uses two TEs, both T5 and CLIP, models like Lumina and HiDream use LLMs as TEs, and we can see many other examples of this.
For newcomers to ComfyUI, they obviously are not entirely aware of this, they may find it odd that we load, say, Gemma 2B, with a _CLIP_ loader node, rather than a _TE_ loader node, the latter would make more sense.
It is obviously impossible at this point to actually internally rename CLIP inputs to TE, but it should be feasible enough on the frontend side of things.
# How should this work?
Firstly, make a setting in the menu that shows whether or not to show CLIP inputs and outputs, as well as node names, as TE, or to use the original CLIP names.
Now essentially, this would likely work via just renaming all CLIP elements on the front-end side as TE. Meaning that searching for CLIP in nodes would still show us the (renamed) nodes, TE Text Encode (Prompt), TE Loader, etc., while these nodes and their inputs would be renamed to TE.
Internally, these nodes are still named the same thing, and the name for the input/output type is still CLIP, but this allows us to essentially fix this issue without touching the backend of ComfyUI at all.
┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-4977-UI-UX-Rename-CLIP-inputs-outputs-node-names-as-TE-inputs-outputs-node-names-on-the--24f6d73d3650814bb441cd94bf9d5dc5) by [Unito](https://www.unito.io)
Contributor guide
Assessment
This issue has not been assessed yet.