Skip to content

compress-core (2/3): the in-app Compression page, settings and usage panels - #1

Open
manjughosa wants to merge 2 commits into
compress-core-1-corefrom
compress-core-2-page
Open

manjughosa wants to merge 2 commits into
compress-core-1-corefrom
compress-core-2-page

Conversation

@manjughosa

Copy link
Copy Markdown
Owner

What

Stacked on magpie-community#532 (base is compress-core-1-core of this fork; the real target is magpie-community:main — open a PR from compress-core-2-page → upstream main after magpie-community#532 merges, or just merge this diff together with magpie-community#532).

Adds the UI layer of compress-core:

  • page (page/index.html + app.js/view.js/ui.js/audit.js): sandboxed — no network, _magpie/bridge.js only, --magpie-* variables so both themes follow magpie. A compression gauge, preset switch, one row per strategy, recent requests.
  • panels: a compact settings panel and a usage panel (end of Usage › Overview).
  • rebuildable artifacts: page/engines.js (mirror of catalog.js, asserted byte-identical by a test) and page/lab-engine.bundle.js (esbuild IIFE for the lab bench).
  • the two UI suites (page-catalog, page-save-flow) rejoin the runners: 24 suites.

cases.json, engines and tests are untouched from magpie-community#532.

…d usage panels

The sandboxed page (no network, _magpie bridge only), two panels,
catalog mirror + lab bundle (both rebuildable artifacts), and their
suites back in the runners (24 suites).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant