digital-garbageandClaude Sonnet 5
770d58a315
models.js's ~2700 lines were entirely built around v4's Studio "roles" and "candidates per role" concept, neither of which exists in v5 -- the pipeline is a flat, swappable slot list, not a fixed named-role set. Replaced with a renderer over the live slots (GET /api/pipeline) grouped the way the pipeline itself groups them (Loaders/Preparation/Sampling/ Render), each slot's real widget inputs read live from GET /api/nodes and edited through the same /api/pipeline POST. The "not ready to generate yet" / incomplete-inputs list is now real and visible, not implied. Node add/remove/swap/wire is NOT built here -- v4's graph-editing machinery assumed nodes that no longer exist, and a real editor is its own piece of work; this establishes the actual working file-picker surface first. Extracted `pipeline_state.js`: engine_settings.js and models.js both edit the SAME live pipeline, and each independently caching its own `slots` copy (as Engine Settings' fix earlier this session did) would let one panel's save silently revert the other's un-saved edits the moment the user switched between them -- the exact stale-state bug already fixed once this session, about to recur in a second file. One shared module now owns `slots`/the manifest/the save queue; both panels are thin renderers over it. engine_settings.js refactored to consume it (no behavior change, confirmed live). Live-verified end to end: picked real model/clip/vae files scanned off disk, watched "incomplete" clear field by field down to "ready to generate", and got back a genuine queueable ComfyUI prompt graph. Then confirmed the cross-panel fix specifically: saved an Engine Settings toggle afterward and the POST still carried every file pick Models & Pipeline had made -- neither panel clobbers the other. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ComfyUI-FunPack v5 — "Cunning Cranberry"
FunPack v4.0.0 is going to be the latest release of classic FunPack. Next update is another milestone update, or shall I say, a full rework.
Maintenance of current FunPack became a mess — forgetting to add or remove buttons from/to UI, finding functions that don't do anything but still present in the code absolutely randomly, trying to keep the UI neat while it has no strict boundaries on how it should look like, and of course — making it easy for users to understand how FunPack operates and how you can operate it — this is all time, money and token-consuming.
General idea behind the FunPack v5 rework is writing it from scratch, with a new architecture where a feature can't be forgotten, where a wire can't be missed, where one failing module never stops whole process from executing. Loaders and features would tell the UI by themselves what sorts of inputs they need and where to put it — and UI will compose them according to design guidelines it would have. Samplers would become independent from features — if a feature is available and enabled, sampler would call it. If it's not — it gets skipped and doesn't even appear in the UI so it won't confuse you.
Most of this comes from a FunUI backend draft that got shelved after understanding on how much time has to be invested into polishing it. Without a community support and wide usage it would become another dead project only one person in the world needs but no one else.
Come to think of it, FunPack already became something alike, with an exception — this project is more than alive, and while I can, I will support it.
Final goal is to make FunPack an ultimate answer for a novice's question "I don't know how to generate — what do I install and how do I start?" and for a professional's question "I need a UI with all the cutting edge techniques available on day 0 — which one?"
Preparation for the v5 had started.
FunPack v5.0 "Cunning Cranberry" — coming fall 2026.
This branch is a clean start. Classic FunPack lives on main.