[Concept] Custom categories

[LukeG89]

Just an idea.

It may happen that users want specific nodes in the same place, even when they are far from each other and/or belong to other groups (or not).

Currently as a workaround, you need to keep them outside of the groups and use the "ungrouped" category.
But it's not the best option, because:

• There is only one category
• You need to remember what you put in the ungrouped
  (especially if you have many out-of-group nodes)

What if users can create custom categories with specific name?

Proposed workflows:

Option 1:

• Select the nodes you want to include
• Right-click menu
  • Controller Panel
    • Include in category
• Now you can:
  • Select a category you already created
  • Create new category
• With the last option, a window to edit and save the category name appear

After you saved, you can:

• Click the "+" button in the Controller window
• In the dropdown list there are the categories you created
• You can open them like group tabs

Option 2:

• Click the "+" button in the Controller window
• There is a new option in the dropdown list: Add category
• Give a name to the new category
• An empty category is created (displayed like a group tab)

Now you can:

• Select the nodes you want to include
• Right-click menu
  • Controller Panel
    • Include in category
• Select the category you created

This would overcome the current "limitations" of groups.
Categories can be used as alteratives of groups.

@chrisgoringe @JorgeR81 What do you think?

[JorgeR81]

Categories can be used as alteratives of groups.

After so much effort in making the Controller a "mirror" of the graph's canvas, it feels like a step backwards, having to introduce a new concept, just for the Controller.

The category could help in some cases, but it may be confusing, because it doesn't exist in the graph canvas.

Group colors are working very well in the controller.
The category would be an "abstract" concept, harder to visualize.

I think it's a similar problem to the one we were discussing at the ComfyUI repo, about InvokeAI.

If we make the Controller different from what's happening in the graph canvas, it may help, at first, in specific workflows, but in the long run, the Controller it would be harder and less intuitive to use.

---

It may happen that users want specific nodes in the same place, even when they are far from each other and/or belong to other groups (or not).

If we want these nodes together in the Controller, we probably also wanted them together in the workflow.
Then it's just a matter of trying to organize the workflow better.

There are other extensions that can help with that.
I still plan having use everywhere nodes :)

[chrisgoringe]

You know if you have multiple groups with the same name the controller treats them as one?

[JorgeR81]

You know if you have multiple groups with the same name the controller treats them as one?

Ah yes, I noticed that !

That could be a good workaround !

[LukeG89]

You know if you have multiple groups with the same name the controller treats them as one?

Didn't know that! That would work as a custom category!

Nevermind guys!

[chrisgoringe]

This sort of thing is exactly why I implemented the groups by name!

…

On Mon, 4 Nov 2024 at 8:12 AM, LukeG89 ***@***.***> wrote: You know if you have multiple groups with the same name the controller treats them as one? Didn't know that! That would work as a custom category! Nevermind guys! — Reply to this email directly, view it on GitHub <#271 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBLMA5JN7U6TACNVVOGCUTZ62GVPAVCNFSM6AAAAABRCW2RN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJTGY3DOOA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>