plexora 0.0.1__py3-none-any.whl

plexora/plugins/figure_builder/templates/figure_builder/library.html

@@ -0,0 +1,74 @@
+{% extends 'base.html' %}
+{% block content %}
+<title>Plexora - Figures</title>
+{# Deliberately shaped like the Open Project page, down to the class names it
+   reuses from openProject.css: a figure and a project are the same KIND of
+   thing to a user -- something saved, found again and opened -- and giving the
+   two lists different furniture would be inventing a distinction that does not
+   exist. Everything specific to figures is prefixed .fb-, which is what keeps
+   this plugin's stylesheet off core's elements. #}
+<div class="open-project-page fb-library">
+    <div class="open-project-header">
+        <div>
+            <h1>Figures</h1>
+            <p class="open-project-subtitle" id="fb_library_count">Loading&hellip;</p>
+        </div>
+        <button type="button" class="btn btn-primary open-project-create" id="fb_library_create">
+            <span class="fas fa-plus"></span> New Figure&hellip;
+        </button>
+    </div>
+
+    <div class="open-project-tabs" role="tablist">
+        <a class="open-project-tab" role="tab" aria-selected="false"
+           href="{{ data.base_url }}/open_project">Projects</a>
+        <span class="open-project-tab is-active" role="tab" aria-selected="true">Figures</span>
+    </div>
+
+    <div class="open-project-toolbar">
+        <div class="open-project-search">
+            <span class="fas fa-magnifying-glass"></span>
+            <input type="text" id="fb_library_search" placeholder="Search figures&hellip;" autocomplete="off">
+        </div>
+    </div>
+
+    <div id="fb_library_results" class="project-results project-grid"></div>
+
+    <div id="fb_library_empty" class="open-project-state" hidden>
+        <span class="fas fa-images open-project-state-icon"></span>
+        <p>No figures yet</p>
+        <p class="fb-muted">Open a project, find a view worth keeping, and capture it &mdash;
+            or start an empty figure here.</p>
+        <button type="button" class="btn btn-primary" id="fb_library_create_empty">Create your first figure&hellip;</button>
+    </div>
+
+    <div id="fb_library_no_results" class="open-project-state" hidden>
+        <span class="fas fa-magnifying-glass open-project-state-icon"></span>
+        <p>No figures match your search</p>
+    </div>
+
+    {# A button, not a link: deleting posts, so there is no URL for a
+       prefetcher or a stale bookmark to follow. Dismissed through bootstrap's
+       data API for the reason core's delete dialog documents -- the ES-module
+       build never assigns window.bootstrap. #}
+    <div class="modal fade" id="fb_delete_modal" tabindex="-1" aria-hidden="true">
+        <div class="modal-dialog modal-dialog-centered">
+            <div class="modal-content">
+                <div class="modal-header">
+                    <h5 class="modal-title">Delete figure?</h5>
+                    <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Close"></button>
+                </div>
+                <div class="modal-body">
+                    <p>Delete <strong id="fb_delete_modal_name"></strong>? Its layout, captured
+                        scenes and previews are removed from disk and cannot be recovered.</p>
+                    <p class="fb-muted">The images it referenced are untouched.</p>
+                </div>
+                <div class="modal-footer">
+                    <button type="button" class="btn btn-outline-light" data-bs-dismiss="modal">Cancel</button>
+                    <button id="fb_delete_modal_confirm" type="button" class="btn btn-danger"
+                            data-bs-dismiss="modal">Delete</button>
+                </div>
+            </div>
+        </div>
+    </div>
+</div>
+{% endblock %}

plexora/plugins/figure_builder/templates/figure_builder/workspace.html

@@ -0,0 +1,27 @@
+{% extends 'base.html' %}
+{% block content %}
+<title>Plexora - Figure</title>
+{# The viewer's stylesheet, on a page with no viewer.
+
+   Quick Edit mounts a SECOND ViewerSidebar beside a mini preview of a figure
+   panel -- core's own channel widget, driving core's own markup, so a user
+   never has to learn a second set of channel controls and a fix to the real
+   one lands here too. The look of that markup lives in viewer.css, which
+   index.html normally owns.
+
+   Safe to link here because every id rule in it (#bodyDiv, #openseadragon,
+   #channel_list, ...) names an element index.html renders and this page does
+   not, so they are inert; what applies is the .channel-slot / .searchable-select
+   / .color-swatch class set, which is exactly what is being borrowed. #}
+<link rel="stylesheet" href="{{ data.base_url }}/client/src/css/viewer.css?v=20260823_viewer_refactor">
+{# One figure, opened without a project.
+
+   Canvas-only by construction: there is no viewer here because there is no
+   datasource here, and a figure legitimately references several. Editing a
+   panel's SCENE therefore navigates to that panel's own datasource with the
+   tool open (see figureWorkspace.js) -- which is a page load, and is the honest
+   one: main.js boots per page and the server holds one loaded datasource, so
+   "swap the image under the live viewer" is not a thing this app can do without
+   pretending. #}
+{% include 'figure_builder/workspace_body.html' %}
+{% endblock %}

plexora/plugins/figure_builder/templates/figure_builder/workspace_body.html

@@ -0,0 +1,458 @@
+{# The figure canvas.
+
+   ONE workspace, and the canvas is nearly all of it. This markup used to be
+   rendered in two places -- a figure's own page and a split pane beside the
+   live viewer -- and the split pane is gone: composing a figure and looking
+   down a microscope are different activities, and half a window was not enough
+   room for either. What is left is a page whose dominant element is the figure.
+
+   The permanent chrome is deliberately thin: a narrow tool rail, a tray of
+   panels, and a topbar. Everything that ACTS on a selection is built in
+   JavaScript into #fb_overlay_layer and floats beside what it acts on
+   (figureContextBar.js) -- a fixed properties column would take three hundred
+   pixels away from the thing the user is looking at, permanently, to show
+   controls that are relevant some of the time.
+
+   #fb_text_panel is not a return of that column, and the distinction is the
+   word "permanently": it is CONTEXTUAL, present only while a text object is
+   selected or being typed into, and gone the rest of the time. Text carries
+   far more formatting than any other object here -- family, size, colour,
+   weight, leading, two alignments -- and a popover deep enough to hold all of
+   it is a popover nobody can work in. It holds formatting only; anything that
+   can be done to any OBJECT stays on the floating bar.
+
+   That bar renders from figureActions.js, one declaration of what each action
+   is and when it applies, which the right-click menu renders from as well. It
+   used to be four hand-built lists and they had drifted -- the menu disabled
+   "Bring to front" where the bar offered it live on a text box and it did
+   nothing at all.
+
+   #fb_overlay_layer is the one part of this the canvas renderer never touches.
+   FigureCanvas.render() replaces the whole of #fb_page_surface on every change,
+   so anything that has to survive a render -- the context bar, an open text
+   editor -- lives out here instead. #}
+<div class="fb-workspace" id="fb_workspace"
+     data-figure-id="{{ data.figure_id | default('') }}">
+    {# Clusters on the desk, not a strip across it. The bar itself paints
+       nothing: what floats is the controls, in the same card as the rail and
+       the tray. The gap between two clusters is what says which controls belong
+       together, which is the job the grey pill inside a solid bar was doing --
+       without a box inside a box. #}
+    <header class="fb-topbar">
+        <div class="fb-bar-cluster fb-bar-cluster-lead">
+            {# The library is where this goes by default and where it goes if
+               anything is uncertain. It is retargeted at the VIEWER, in
+               JavaScript, when the note left by figureSidebarController says
+               that is where the user came from -- because the commonest trip
+               there is is capture a few fields, look at the figure, go back to
+               the slide for one more, and an arrow that always went to the
+               library made the way back a search. #}
+            <a class="fb-back" id="fb_back" href="{{ data.figure_builder_url }}/figures"
+               title="Back to figures">
+                <span class="fas fa-chevron-left"></span>
+            </a>
+            {# contenteditable would be fewer elements and the wrong control: it
+               accepts pasted markup, and this value is rendered back into a
+               list of cards. A plain input cannot carry anything but text. #}
+            <input type="text" id="fb_title" class="fb-title-input" autocomplete="off"
+                   spellcheck="false" maxlength="200" aria-label="Figure title">
+            <span id="fb_save_status" class="fb-save-status" role="status" aria-live="polite"></span>
+        </div>
+
+        <div class="fb-topbar-spacer"></div>
+
+        {# History, pages and View in one card: three ways of moving around what
+           already exists. Export is not one of those, and does not share it. #}
+        <div class="fb-bar-cluster">
+            <div class="fb-topbar-group" role="group" aria-label="History">
+                <button type="button" id="fb_undo" class="fb-icon-button" title="Undo (⌘Z)" disabled>
+                    <span class="fas fa-rotate-left"></span>
+                </button>
+                <button type="button" id="fb_redo" class="fb-icon-button" title="Redo (⇧⌘Z)" disabled>
+                    <span class="fas fa-rotate-right"></span>
+                </button>
+            </div>
+
+            <span class="fb-bar-divider" aria-hidden="true"></span>
+
+            <div class="fb-topbar-group" role="group" aria-label="Pages">
+                <select id="fb_page_select" class="fb-select fb-select-quiet" aria-label="Page"></select>
+                <button type="button" id="fb_page_menu" class="fb-icon-button" title="Page actions"
+                        aria-haspopup="true" aria-expanded="false">
+                    <span class="fas fa-ellipsis"></span>
+                </button>
+            </div>
+
+            <span class="fb-bar-divider" aria-hidden="true"></span>
+
+            <button type="button" id="fb_view_menu" class="fb-button"
+                    aria-haspopup="true" aria-expanded="false">
+                <span class="fas fa-eye"></span> View
+            </button>
+        </div>
+
+        {# Zoom is not up here. It changes where the eye is, not what the figure
+           is, and sitting in a row with Undo and Export it looked like the same
+           kind of control. It lives in the status bar at the foot of the
+           canvas, beside the readout it moves. #}
+
+        <button type="button" id="fb_export_open" class="fb-button fb-button-primary fb-bar-solo">
+            <span class="fas fa-file-export"></span> Export
+        </button>
+    </header>
+
+    {# A native <dialog>: modal, focus-trapped and Esc-dismissible without a
+       line of script, and it cannot end up behind the canvas the way a
+       positioned div can. #}
+    <dialog id="fb_export_dialog" class="fb-dialog">
+        <h2>Export figure</h2>
+        <p class="fb-muted">Panels are re-rendered from the source images at the resolution
+            you ask for &mdash; not from what is on screen.</p>
+
+        <label class="fb-field-label" for="fb_export_format">Format</label>
+        <select id="fb_export_format" class="fb-select">
+            <option value="pdf">PDF &mdash; text and legends stay editable</option>
+            <option value="tiff">TIFF &mdash; flattened, for submission</option>
+            <option value="png">PNG &mdash; flattened, for circulating</option>
+        </select>
+
+        <label class="fb-field-label" for="fb_export_dpi">Resolution</label>
+        <select id="fb_export_dpi" class="fb-select">
+            <option value="150">150 DPI</option>
+            <option value="300" selected>300 DPI</option>
+            <option value="600">600 DPI</option>
+            <option value="1200">1200 DPI</option>
+        </select>
+
+        <label class="fb-check">
+            <input type="checkbox" id="fb_export_provenance" checked>
+            Append a provenance page
+        </label>
+
+        {# Stated up front rather than discovered in the file. Only PNG has an
+           alpha channel; a transparent page rendered to PDF or TIFF is drawn on
+           white, which is a decision the author should make knowingly. #}
+        <p class="fb-muted">A transparent page keeps its transparency in PNG only.
+            PDF and TIFF render it white.</p>
+
+        {# Filled by the preflight, before anything is rendered: a warning
+           attached to a file that is already written is a warning nobody acts
+           on. #}
+        <div id="fb_export_warnings" class="fb-export-warnings"></div>
+
+        <div class="fb-banner-actions">
+            <span id="fb_export_status" class="fb-muted" role="status" aria-live="polite"></span>
+            {# This plugin's own buttons, not core's .sidebar-action. The
+               figure page links viewer.css for the borrowed channel widget
+               alone; making the export dialog depend on it too would tie the
+               look of a Figure Builder control to a stylesheet that is here
+               for something else entirely. #}
+            <a id="fb_export_download" class="fb-button" href="#" download hidden>
+                <span class="fas fa-download"></span> Download
+            </a>
+            <button type="button" id="fb_export_stop" class="fb-button" hidden>Stop</button>
+            <button type="button" id="fb_export_start" class="fb-button fb-button-primary">Export</button>
+            <button type="button" id="fb_export_cancel" class="fb-button">Close</button>
+        </div>
+    </dialog>
+
+    <div id="fb_conflict_banner" class="fb-banner fb-banner-warning" hidden>
+        <span class="fas fa-code-branch"></span>
+        <div>
+            <strong>Changed in another session.</strong>
+            <div class="fb-banner-detail">Someone &mdash; probably another tab &mdash; saved this
+                figure since this one loaded. Reloading discards the edits made here.</div>
+            <div class="fb-banner-actions">
+                <button id="fb_conflict_reload" class="fb-button" type="button">Reload theirs</button>
+            </div>
+        </div>
+    </div>
+
+    <div id="fb_unreadable_banner" class="fb-banner fb-banner-danger" hidden>
+        <span class="fas fa-triangle-exclamation"></span>
+        <div>
+            <strong>This figure could not be opened.</strong>
+            <div id="fb_unreadable_detail" class="fb-banner-detail"></div>
+        </div>
+    </div>
+
+    {# Nothing in here is a column. The canvas runs the full width of the body
+       and the rail and the tray are cards lying on top of it -- which is why
+       .fb-main comes FIRST: it is the only flex child that takes space, and the
+       two cards are positioned against the body and out of the flow. Quick Edit
+       is the exception, and takes its 420px from the canvas, because reframing
+       a panel means watching the figure change as you do it. #}
+    <div class="fb-body">
+        <main class="fb-main" id="fb_main">
+            {# Optional, off by default and remembered per browser. Two
+               <canvas> strips rather than a wall of positioned ticks: a ruler
+               at 1 mm resolution across an A4 page is 210 elements that have to
+               be rebuilt on every zoom and every scroll. #}
+            <canvas class="fb-ruler fb-ruler-h" id="fb_ruler_h" aria-hidden="true"></canvas>
+            <canvas class="fb-ruler fb-ruler-v" id="fb_ruler_v" aria-hidden="true"></canvas>
+            <div class="fb-ruler-corner" id="fb_ruler_corner" aria-hidden="true"></div>
+
+            <div class="fb-canvas-scroll" id="fb_canvas_scroll">
+                {# The sheet and the two things that belong to it, shrink-wrapped
+                   and centred as one block: centred independently, the caption
+                   and the button would drift off the page edges they are
+                   supposed to line up with. #}
+                <div class="fb-sheet">
+                    <div class="fb-sheet-caption" id="fb_sheet_caption"></div>
+                    <div class="fb-page" id="fb_page">
+                        {# Under the panels, and children of the page so they
+                           scale with it: a grid drawn in screen pixels drifts
+                           off the millimetres it is supposed to represent the
+                           moment the zoom changes. #}
+                        <div class="fb-page-grid" id="fb_page_grid" aria-hidden="true"></div>
+                        <div class="fb-page-margins" id="fb_page_margins" aria-hidden="true"></div>
+                        <div class="fb-page-surface" id="fb_page_surface"></div>
+                        {# Guides and the marquee live above the panels and take
+                           no pointer events, so a snap line can never be what a
+                           drag grabs. #}
+                        <div class="fb-page-guides" id="fb_page_guides" aria-hidden="true"></div>
+                    </div>
+
+                    {# Under the page and as wide as it. Inside the scroll
+                       surface rather than in the status bar, so it scrolls away
+                       with the sheet it follows: it is part of the document,
+                       not part of the window. #}
+                    <button type="button" id="fb_page_add" class="fb-add-page">
+                        <span class="fas fa-plus" aria-hidden="true"></span> Add page
+                    </button>
+                </div>
+            </div>
+
+            {# Never re-rendered by the canvas. See the file comment. #}
+            <div class="fb-overlay-layer" id="fb_overlay_layer"></div>
+        </main>
+
+        {# Level 1: the only controls that are always visible, and there are
+           four of them. Everything else is contextual, in a menu, or on the
+           right-click.
+
+           There is no Select tool. Selecting is what the pointer does when it
+           is not doing anything else: the drawing tools are one-shot and hand
+           the pointer back the moment they have placed something, and clicking
+           the desk drops one armed by mistake. A button for "no tool" would be
+           a light that is on almost always, and a click nobody needs to make.
+
+           Scale bar and Legend are not here either. They act on a SELECTION,
+           they have real settings behind them, and both already exist in the
+           floating bar next to the panels they change -- up here they were a
+           second, blunter copy of the same switch, dimmed most of the time.
+
+           Labelled, at the cost of twenty pixels of width: four icons in a
+           stack with nothing under them is four things to hover before
+           starting, every session, because "a square" is not a word -- and
+           this rail is the first thing a new user has to read. #}
+        <nav class="fb-tool-rail fb-card" id="fb_tool_rail" aria-label="Figure tools">
+            {# The one rail item that opens a panel rather than arming a tool.
+               The badge is what stops a capture arriving into a closed drawer
+               from looking like a capture that was lost. #}
+            <div class="fb-tool-holder">
+                <button type="button" class="fb-tool is-active" id="fb_tool_panels"
+                        title="Panels captured for this figure"
+                        aria-haspopup="true" aria-expanded="true"
+                        aria-controls="fb_tray_panel">
+                    <span class="fas fa-images" aria-hidden="true"></span>
+                    <span class="fb-tool-label">Panels</span>
+                </button>
+                <span class="fb-tool-badge" id="fb_tray_badge" aria-hidden="true"></span>
+            </div>
+
+            <div class="fb-tool-rail-gap"></div>
+
+            <button type="button" class="fb-tool" data-tool="text"
+                    title="Text" aria-pressed="false">
+                <span class="fas fa-font" aria-hidden="true"></span>
+                <span class="fb-tool-label">Text</span>
+            </button>
+            {# Two menus rather than four buttons, and split where the CONTROLS
+               differ: a rectangle and an ellipse have a fill and are dragged
+               out as a box, a line and an arrow have two ends and are dragged
+               out along one. Four permanent icons would double the rail to
+               save one click on the rarer three. #}
+            <button type="button" class="fb-tool" id="fb_tool_shapes"
+                    title="Shapes" aria-haspopup="true" aria-expanded="false"
+                    aria-pressed="false">
+                <span class="fas fa-shapes" aria-hidden="true"></span>
+                <span class="fb-tool-label">Shapes</span>
+            </button>
+            <button type="button" class="fb-tool" id="fb_tool_lines"
+                    title="Lines and arrows" aria-haspopup="true" aria-expanded="false"
+                    aria-pressed="false">
+                <span class="fas fa-arrow-right-long" aria-hidden="true"></span>
+                <span class="fb-tool-label">Lines</span>
+            </button>
+        </nav>
+
+        {# The text sidebar. CONTEXTUAL, and that is the whole distinction from
+           the fixed properties column this workspace deleted: it is present
+           only while a text object is selected or being typed into, so the
+           canvas keeps the full width for everything else anyone does here.
+
+           It carries text FORMATTING and nothing else. Actions that apply to
+           any object -- arrange, align, group, duplicate, delete -- belong to
+           the bar that floats over the selection, which is one shared component
+           for every object kind rather than a list rebuilt per type.
+
+           `.fb-side-panel` is what it shares with the tray below: ONE strip
+           beside the rail, holding one panel at a time, at one size and in one
+           place. Which of them is in it is FigureWorkspace.showSidebar's to
+           say, and neither hides or shows itself -- two panels each answering
+           that for themselves is what drew this one underneath the tray, where
+           it was invisible and still took every click on the overlap. #}
+        <aside class="fb-side-panel fb-text-panel fb-card" id="fb_text_panel"
+               aria-label="Text properties" hidden></aside>
+
+        {# What this figure is made of. Panels arrive here from the viewer and
+           are dragged onto the page; nothing is ever placed automatically at
+           capture time, because composition is a different sitting from
+           exploration.
+
+           A card the rail opens, with its own title and its own way out.
+           Open on arrival: a figure page whose panels were behind a closed
+           drawer would look, on the day it is reopened, like a figure that had
+           lost them. #}
+        <aside class="fb-side-panel fb-tray-panel fb-card" id="fb_tray_panel"
+               aria-label="Panels">
+            <div class="fb-side-heading">
+                <span class="fb-side-title">Panels</span>
+                <span id="fb_tray_count" class="fb-tray-count"></span>
+                <button type="button" id="fb_tray_close" class="fb-icon-button"
+                        title="Close">
+                    <span class="fas fa-xmark" aria-hidden="true"></span>
+                </button>
+            </div>
+
+            {# Where the next panels come from, at the top of the thing they
+               land in.
+
+               Two routes, because a figure is made of two kinds of thing. A
+               project opens that project's viewer with THIS figure already
+               chosen as the capture destination, so the fields taken over
+               there arrive in this tray and the dock's "Figure Canvas" is the
+               way back. An image file is for the schematic or the plot that
+               was never in Plexora, and it lands in the figure alone.
+
+               A menu rather than two buttons: one is a page load and the other
+               is a file dialog, and neither is used often enough to spend a
+               permanent row of a narrow card on. The file input lives here now
+               rather than in the rail -- it is a way of adding a panel, and
+               this is where adding panels is. #}
+            <div class="fb-tray-add">
+                <button type="button" id="fb_tray_add" class="fb-button fb-tray-add-button"
+                        aria-haspopup="true" aria-expanded="false">
+                    <span class="fas fa-plus" aria-hidden="true"></span> Add panels
+                </button>
+                <input type="file" id="fb_add_image_input" accept="image/*" multiple hidden>
+            </div>
+            {# Shown only once the tray is long enough for finding something in
+               it to be work -- which is sooner now that the names are behind a
+               hover.
+
+               "Filter", not "Search": it narrows the grid under it as the
+               characters arrive and there is nothing to submit. The × and Esc
+               are the way back out, because a filter you have forgotten is on
+               looks exactly like a tray that has lost panels. #}
+            <div class="fb-tray-search" id="fb_tray_search_wrap" hidden>
+                <span class="fas fa-magnifying-glass" aria-hidden="true"></span>
+                <input type="search" id="fb_tray_search" placeholder="Filter panels"
+                       autocomplete="off" spellcheck="false" aria-label="Filter panels">
+                <button type="button" id="fb_tray_search_clear" class="fb-tray-search-clear"
+                        title="Clear filter (Esc)" hidden>
+                    <span class="fas fa-xmark" aria-hidden="true"></span>
+                </button>
+            </div>
+            <div class="fb-tray-strip" id="fb_tray_strip" role="listbox" aria-multiselectable="true"></div>
+            <div class="fb-tray-empty" id="fb_tray_empty" hidden>
+                <p class="fb-muted">Captured panels land here.</p>
+                <p class="fb-muted">Use <strong>Add panels</strong> to open a project and
+                    capture a field, or drop an image file onto the page.</p>
+            </div>
+        </aside>
+
+        {# Quick Edit: the microscopy view behind one panel, adjusted without
+           leaving the canvas.
+
+           The channel controls below the preview are CORE's -- a second
+           ViewerSidebar instance driving the markup below, which carries core's
+           own classes and `fbqe_`-prefixed ids so the two instances can never
+           find each other's elements. Writing a second channel widget here
+           would be two implementations of colour, contrast and ordering that
+           agree until the day one of them is fixed, and a user who has to learn
+           the second one.
+
+           Deliberately NOT a second scientific viewer: there is no OSD, no tile
+           stack, no overlays and no plugins in here. Anything past reframing
+           and channels is what "Open in Main Viewer" is for. #}
+        <aside class="fb-quickedit" id="fb_quickedit" hidden aria-label="Quick Edit">
+            <header class="fb-quickedit-head">
+                <span class="fb-quickedit-title" id="fb_quickedit_title"></span>
+                <button type="button" id="fb_quickedit_close" class="fb-icon-button"
+                        title="Cancel">
+                    <span class="fas fa-xmark"></span>
+                </button>
+            </header>
+
+            <div class="fb-quickedit-view">
+                <canvas id="fb_quickedit_canvas"></canvas>
+            </div>
+            <p class="fb-muted fb-quickedit-note" id="fb_quickedit_note">
+                Drag to reposition, scroll to zoom. The bright rectangle is what the
+                panel will show.
+            </p>
+
+            <div class="fb-quickedit-channels" id="fb_quickedit_channels">
+                <div class="selected-count">
+                    <span id="fbqe_num-selected-channels">0</span>
+                    <span>active</span>
+                    <span class="selected-count-max">&middot; <span id="fbqe_max-channels">15</span> max</span>
+                </div>
+                <div id="fbqe_channel_slot_list" class="channel-slot-list"></div>
+                <button id="fbqe_add_channel_button" class="sidebar-action secondary" type="button">
+                    <span class="fas fa-plus"></span>
+                    Add Channel
+                </button>
+            </div>
+
+            <footer class="fb-quickedit-actions">
+                <button type="button" id="fb_quickedit_main" class="fb-button">
+                    Open in Main Viewer
+                </button>
+                <div class="fb-topbar-spacer"></div>
+                <button type="button" id="fb_quickedit_cancel" class="fb-button">
+                    Cancel
+                </button>
+                <button type="button" id="fb_quickedit_done" class="fb-button fb-button-primary">Done</button>
+            </footer>
+        </aside>
+    </div>
+
+    {# What is on the page, and what the pointer can do to it. The
+       topbar acts on the figure; this acts on the view of it. #}
+    <div class="fb-statusbar">
+        <span id="fb_object_count" class="fb-statusbar-count"></span>
+        <span class="fb-statusbar-hint">
+            <kbd>⌘</kbd>-scroll to zoom &middot; <kbd>Space</kbd>-drag to pan
+        </span>
+        <div class="fb-topbar-spacer"></div>
+        {# The only thing down here anyone clicks, so it is the only thing down
+           here in a card. The count and the hint stay on the desk. #}
+        <div class="fb-bar-cluster" role="group" aria-label="Zoom">
+            <button type="button" id="fb_zoom_out" class="fb-icon-button" title="Zoom out (⌘−)">
+                <span class="fas fa-minus" aria-hidden="true"></span>
+            </button>
+            <button type="button" id="fb_zoom_readout" class="fb-zoom-readout"
+                    title="Zoom" aria-haspopup="true" aria-expanded="false">100%</button>
+            <button type="button" id="fb_zoom_in" class="fb-icon-button" title="Zoom in (⌘=)">
+                <span class="fas fa-plus" aria-hidden="true"></span>
+            </button>
+            <span class="fb-bar-divider" aria-hidden="true"></span>
+            <button type="button" id="fb_zoom_fit" class="fb-icon-button" title="Fit page (⌘0)">
+                <span class="fas fa-expand" aria-hidden="true"></span>
+            </button>
+        </div>
+    </div>
+</div>

plexora/plugins/gating/__init__.py

@@ -0,0 +1,76 @@
+"""Marker-threshold gating: Plexora's first plugin.
+
+Everything gating owns lives under this directory -- server code, client
+assets, templates and tests -- so the whole feature can be read, moved or
+removed as one unit.
+
+Kept deliberately light: this module is imported whenever gating is activated,
+and its only job is to describe the plugin. The Blueprint is built by a factory
+at install time so that reading the descriptor does not drag in
+scipy/sklearn/anndata/h5py.
+"""
+
+from plexora.api.plugin import Plugin, Requires
+
+VERSION = "20260824_icon_names"
+
+
+def _blueprint():
+    from plexora.plugins.gating.server.routes import gating_bp
+
+    return gating_bp
+
+
+PLUGIN = Plugin(
+    name="gating",
+    label="Thresholding",
+    version=VERSION,
+    blueprint_factory=_blueprint,
+    # Templates are namespaced by plugin name, so two plugins can both ship a
+    # "panel.html" without colliding in Flask's shared template lookup.
+    panels={
+        "tool_panel_slot": "gating/panel.html",
+        "tool_panel_legacy_slot": "gating/legacy.html",
+    },
+    # Filenames within this plugin's own static/ directory. Core turns them
+    # into base-URL-safe, version-stamped URLs -- a plugin never writes a path
+    # that assumes where the app is mounted.
+    # gatingApi.js first: the other two construct GatingApi at init.
+    scripts=("gatingApi.js", "csvGatingList.js", "gatingSidebarController.js"),
+    styles=("gating.css",),
+    # Gating thresholds feature-table columns, so a project without one has
+    # nothing to gate; it needs the marker/metadata split to know WHICH columns
+    # to offer, and the three roles it resolves through dataset.schema (cell id
+    # to report selections, x/y to keep coordinates out of the marker list).
+    #
+    # How cells are drawn is deliberately NOT declared here. Gating paints
+    # per-cell results over the image, but the project answers that itself --
+    # the mask if there is one, centroids otherwise (see project.cell_layer).
+    #
+    # Which matrix holds those values IS declared, because a threshold is a
+    # number on an axis: set against raw counts it means nothing on a
+    # log-transformed copy of the same data, and nothing about the values says
+    # which of the two the file handed over.
+    #
+    # Segmentation is offered, not demanded: gating still works with centroids
+    # alone. Listing it as optional is what lets core ask at the right moment
+    # instead of this plugin growing its own file-path box.
+    #
+    # image_id is demanded, and used to be optional. It is only safely optional
+    # when the table covers a single image, and nothing establishes that:
+    # deciding it needs to know which column is the image id, which is the
+    # question itself. The import-time guard only fires when a column-name
+    # heuristic recognises the name, so a table keyed on "roi" or "core" gets
+    # imported whole and draws several images' cells over one image. Asking is
+    # the only honest form -- and "this data has only one image" is one of the
+    # answers, so a genuinely single-image project is not made to invent a
+    # column it does not have.
+    requires=Requires(
+        table=True,
+        markers=True,
+        features=True,
+        roles=("cell_id", "x", "y", "image_id"),
+        optional=("segmentation",),
+    ),
+    owns_cell_layer=True,
+)