digital-garbage
2349c550cb
graph.py reads an input's TYPE, which is all a wire needs. Editing a value needs the rest -- the choices a combo offers, the bounds on a number, whether the box is multiline -- so that is asked separately rather than widening the question graph.py asks. Read from ComfyUI's own INPUT_TYPES, so a node written for ComfyUI is editable here without knowing anything about FunPack. Caught while looking at the real output rather than after committing: deciding "a socket is upper case" is wrong, because STRING is upper case -- every prompt box in the pipeline came back as something nobody could type in. The honest rule is ComfyUI's own primitive set, plus forceInput, which is a short list core holds on purpose. /funpack/api/nodes answers by name. ComfyUI's /object_info returns every installed node, which on a machine with a few packs is megabytes for a question about a dozen; a node nobody installed comes back as null rather than missing, so "this slot points at something absent" reads differently from "I did not ask". The dev server now registers ComfyUI's nodes and FunPack's own, through the same function the tests use. Without it the pipeline was fourteen "there is no node called X installed" and nothing to edit -- so the one thing the dev server exists for could not reach the half of the app that matters. It now reports the three problems that are real: no model, no CLIP, no VAE chosen.
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.