ComfyUI
ComfyUI copied to clipboard
Ability to switch between different graphs

Wow. Nice work!
What I meant is that I would like the workflows to be in a folder like: workflows/default_txt2img.json workflows/area_composition.json in the same format you get when you export them from the UI.
This is so I can easily modify them if I change things.
What I meant is that I would like the workflows to be in a folder like: workflows/default_txt2img.json workflows/area_composition.json in the same format you get when you export them from the UI.
This is so I can easily modify them if I change things.
Can we implement this later? I just have some more ideas that I would like to implement to make using ComfyUI more convenient.
is it that difficult to implement? You can just put a list of filenames in the code and fetch them.
It's not that difficult, you can just download it and fix everything you want at once and save it. Thus, you can store an arbitrary number of presets without changing the code at all. To make such functionality with separate files, you will also have to write code in the server part that will give a list of files.
I only mean for the presets that are already there.
The: web/DefaultWorkflows.json should be multiple files like: workflows/default_txt2img.json workflows/area_composition.json
The: web/DefaultWorkflows.json should be multiple files like: workflows/default_txt2img.json workflows/area_composition.json
Do you think it makes sense to do this for presets that are loaded only once at the first launch? Then it's all not used anywhere.
yes because those presets will likely be modified a lot by me and others so I want it to be simple.
Then I will make an index file.json that will contain a list of files with presets. So will it be normal?
yes that's good.
To implement sequential downloading of several files so that nothing breaks quickly does not work, while I leave it like this. Either generate it on the server side or come up with a loading method that takes into account the asynchrony of requests. I'll probably do it tomorrow.
This is awesome. Could use some Styling, like darker shade than graph BG but not black against white which is terrible for eyes and not advised for dark themes. Buttons could use BGs.
High contrast is more a accessibility theme for people receiving less light in their eyes, for a lot of other people it causes headaches, ghosting of lettering against blackness, etc.
I did the loading of default graphs from several files.
I like this addition!
Would be great if it could be toggleable, maybe on the side menu that is already there!

I plan to move the side menu to the top menu. It's just not such an important task to do it now. Now I want to make an additional interface to interact with the nodes and a graphical editor.
Oh no, you got there first :smile: . I was also working on GUI to add libraries, history and multiple graphs. The main issue is that litegraph.js has few bugs :/.

that will be great
any updates on this ??
any updates on this ??
If you want it merged faster you should test it and let us know if you find any bugs or if everything works fine.
any updates on this ??
I'm still working on additional functionality
any updates on this ??
If you want it merged faster you should test it and let us know if you find any bugs or if everything works fine.
ok sure , thanks for the hard work
im kinda new in that stuff , shall i clone the whole repo again , or there are a way to only see the changes
i added [email protected]:JAlB-/ComfyUI.git as another remote source i fetched it but when i run i cant see the new ui
oh sorry had to clear the browser cache
I'm going to die waiting for this.
Been driving this, must have feature or something akin to it. Brings this closer to the usability / friendliness of A1111 by being able to rapidly switch through workflows without manually managing save files.
Unfortunately, I can't devote as much time to the project as I would like. If there is a desire to help, then I will not refuse to help.
@JAlB- what features are missing in this currently? Are there any bugs your already aware of?
This is really old and likely not even compatible with a merge to test without manually fixing things.