digital-garbageandClaude Sonnet 5 1abf136e03 feat: wire per-scene reference-image picking into the real generate flow
Fills in the placeholder left in _buildQueueInputs: v5's real per-scene
fields (core/projects.py's Scene.source_image/.references) already
round-trip through api.js's getProject/saveProject today -- it's a raw
whole-object PUT/GET, and the server's own Scene.from_dict()/asdict()
extract and return them regardless of what else v4's project shape carries.
There was just no UI to set them and nothing reading them at generate time.

Added:
- store.js: setSourceImage/setReferences, thin patchScene wrappers (same
  pattern as the existing setSourceTrim).
- inspector.js: a "Reference media" section on the scene panel, right after
  v4's own i2v anchor/Source field, using the same window.MediaPicker
  thumbnail-grid component already used throughout this file for image
  picks -- a single Resolution-source picker plus an add/remove list for
  References.
- generate_bridge.js: exposes reference_wiring.js's wireReferences()
  (untouched, already tested, no DOM dependency).
- store.js's _buildQueueInputs: sets assets.source_image from the run's
  first/anchor scene, and calls wireReferences() for its references --
  same "first scene stands for the whole run" convention its prompt-text
  branch already uses for a multi-scene (whole-timeline) run. An unwired
  reference (no matching slot in the current pipeline) surfaces as a real
  notice in the timeline header, not a silent drop.

Live-verified against the dev server end to end: picked a real reference
image from the Media bin, watched it persist server-side
(GET /funpack/api/projects/:id showed it in the saved file), then clicked
Generate and confirmed the pipeline check ran with it -- the current
default pipeline has no reference slot, and the app correctly said so
("1 reference could not be wired into this pipeline and will not be
used.") rather than silently dropping it. 691/692 JS tests and 548/548
Python tests pass (the one JS failure is the pre-existing, unrelated
projects.test.js import-race flake).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 14:46:57 +03:00
2026-08-27 16:25:34 +03:00
2026-08-27 16:25:34 +03:00
2026-08-27 16:25:34 +03:00

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.

S
Description
No description provided
Readme GPL-3.0
23 MiB
Languages
Python 64.4%
JavaScript 32.7%
CSS 2.8%