digital-garbage
8318b3da0b
Third off the port list. Users will want to add the one pack a workflow needs without being sent to another UI to do it, and a pack that ships experimental work needs the same for itself. custom_nodes.py comes across as core/nodes_manager.py, changed in two places: where FunPack's root is, and one guard that the port made necessary. THE GUARD. custom_nodes_root() asks ComfyUI first and falls back to "FunPack lives inside custom_nodes" -- a reliable anchor in an install, and a wrong one in a development checkout, where the parent is somebody's home directory. Every rule protecting the delete measures against that answer, so with ComfyUI's paths unavailable, "remove Foo" resolved against ~/Documents and all four guards happily agreed. It now checks the assumption it is named after and refuses with where it thinks it is. Found by running the function, not by reading it. Two faults of my own, both in the window: * Update and Remove were a button GROUP -- radios -- for two actions that are not a choice between two states. It also left Remove looking selected after a click, which is an alarming thing to look at. * A failure was drawn and then wiped by the redraw in the same finally block: the message appeared and vanished in one frame. What went wrong is state now, not an argument to one draw call.
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.