Skip to content

Releases

0.51.0

Choose a tag to compare

@timmo001 timmo001 released this 16 Nov 15:15
3855bfd

docs-kit can now deploy a docs site with Alchemy.

  • docs-kit: the new @timmo001/docs-kit/blume/worker export has blumeWorker, which reads the Worker Blume built into dist/ (its entry, compatibility settings, assets folder and the routes that run the Worker first). It returns them as the settings an Alchemy Cloudflare.Worker takes, so a site's alchemy.run.ts only adds the name and domain. The README's new Deploy section shows the whole stack.
  • tokens: released at the same version, with no changes.
  • ui: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • auth: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.

0.50.0

Choose a tag to compare

@timmo001 timmo001 released this 16 Nov 12:50
f7484ec

Ctrl, Cmd, Shift and middle clicks on a button's or card's link now open it the way they would on the link itself.

  • ui: a click on a gw-button pill around a slotted <a>, or on a gw-card that follows the link in its heading, now keeps the keys and button held. Ctrl or Cmd opens the link in a new tab, Shift in a new window and the middle button in a new tab, and a page's own router leaves those clicks alone instead of opening the link in place. The new followLink(link, event) helper does this for an app's own elements, such as a row that follows a link.
  • tokens: the groundwork-tokens build command keeps the original error as the cause when --targets doesn't parse.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • auth: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.49.0

Choose a tag to compare

@timmo001 timmo001 released this 15 Nov 18:43
e835951

Tables can keep a least height.

  • ui: gw-table takes --gw-table-min-height, the least height its frame takes, with no floor by default. The rows keep their own height and the space past the last one stays blank under it, so a short table doesn't jump as rows come, and a contained one grows from there up to --gw-table-max-height. The Display page's Table section shows it.
  • tokens: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • auth: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.48.0

Choose a tag to compare

@timmo001 timmo001 released this 15 Nov 18:32
0083d6d

Text over a picture can now sit just above a player's controls.

  • ui: overlayControls() gives the stage --gw-overlay-controls-height, the bar's visible height while it's over the picture and showing, following a finger that pulls it down, and 0px while it's hidden or under the picture. A note along the bottom of a picture can use it to sit above the bar and move down when the bar goes. The Behavior page's Controls over a picture and Text over media sections show how.
  • tokens: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • auth: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.47.0

Choose a tag to compare

@timmo001 timmo001 released this 15 Nov 17:55
f9fe9cc

A new package for client keys, so every client of a service gets a key of its own.

  • auth: @timmo001/groundwork-auth is new. generateKey makes a key shaped <service>_<kind>_<random><checksum>, with 256 random bits and a CRC32 checksum, and parseKey reads one back, turning away a mistyped or cut-short key before any lookup. hashKey gives the SHA-256 a service keeps, findByKey finds a client by its key in constant time, and bearer and readBearer write and read the Authorization header. ./client has the ClientRecord, NewKey, KeyExchangeRequest and SocketAuth Schemas and generateClientKey, and ./test-vectors.json has sample keys for services in other languages to check against. The Behavior page's Client keys section covers it.
  • tokens: released at the same version, with no changes.
  • ui: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.46.0

Choose a tag to compare

@timmo001 timmo001 released this 15 Nov 16:37
670a90a

Installable web apps get the rest of their pieces, buttons can show how their action went, and theme pickers put the app's own theme first.

  • pwa: watchVersion in ./update keeps a page on the server's release: on a 426 it takes the new build and reloads. ./server adds versionGuard (Effect HTTP middleware) and refuseOtherVersion (for fetch servers) to turn away calls from an old page, plus fileOptions, fileResponse and isPwaFile for serving the built files with the right caching. isHashed comes from the root export, ./build adds buildPwa, addHeadTags, pwaDefine and findShell, and ./vite adds a pwa() plugin for apps built with Vite, which is an optional peer. serveShell has better defaults. The PWA page covers each.
  • ui: gw-install-banner offers to install a web app, with Install and Not now, and stays closed once it's turned down. gw-action-button runs an action and shows how it went where it was pressed: a ring while it runs, then a check and its done label, or why it failed. The Feedback and Actions pages show them.
  • tokens: every theme has chart roles, chart-1 to chart-6 (--gw-color-chart-1 and on), for a chart's series. themeChoices(own?) builds a picker's list: the app's own theme first with no heading, the other core themes under Groundwork, then the optional ones by family.
  • docs-kit: the theme picker shows a choice with an empty family with no heading, so a site's own theme can sit at the top.
  • report: the theme picker puts the report's own theme first with no heading.
  • tui: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.

0.45.0

Choose a tag to compare

@timmo001 timmo001 released this 15 Nov 00:57
52267b4

Small controls in a scrolling row keep their full hit area on a touch screen.

  • ui: a gw-row with scroll leaves room above and below its children for their hit areas, as it already does between them, so a tap just above or below a small button in a scrolling row of presets or filters reaches it rather than being cut off by the track. Nothing changes with a mouse. The Spacing page says so.
  • tokens: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.44.0

Choose a tag to compare

@timmo001 timmo001 released this 15 Nov 00:53
800e02b

Overlays that block the pointer now block the keyboard too.

  • ui: gw-popover, gw-sheet and gw-date-picker's calendar are modal to the keyboard as well as the pointer: Tab and Shift+Tab stay inside, wrapping at the ends, so the focus can't slip to the page behind and leave Esc with nothing to close. Each is marked aria-modal="true". gw-menu-button's menu closes on Tab, and the focus moves on from its button, as a menu should. The new trapTab(event, surface) and tabbables(element) helpers do the same for an app's own modal popup; the Overlays page's new The keyboard section shows how.
  • tokens: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.43.0

Choose a tag to compare

@timmo001 timmo001 released this 14 Nov 23:20
502a029

Fixes for overlays over a full-screen or sideways player.

  • ui: gw-volume's popover is live, so moving its slider never asks "Discard your changes?" on close, and its backdrop dims the page by 15%. A popover, sheet, menu or dialog that opens from an overlayControls bar while the bar is hidden now takes presses and scrolls, rather than letting them through to the picture: anything open in the top layer resets pointer-events and cursor. An overlay shown outside the full-screen element warns once in the console, since Chromium makes it inert there; the Overlays page's new Full screen section says to keep them inside the element that goes full screen.
  • tokens: released at the same version, with no changes.
  • tui: released at the same version, with no changes.
  • report: released at the same version, with no changes.
  • pwa: released at the same version, with no changes.
  • mobile: released at the same version, with no changes.
  • desktop: released at the same version, with no changes.
  • docs-kit: released at the same version, with no changes.

0.42.0

Choose a tag to compare

@timmo001 timmo001 released this 14 Nov 22:39
55777d8

Touch targets: every control reaches --gw-target-min on a touch screen, and no two hit areas overlap, table headings and fields included.

Breaking

  • On a touch screen, gw-table's headings are 44px tall rather than 40px, and a sortable column's heading at least 44px wide. --gw-table-header-height still sets the height.
  • On a touch screen, gw-row's gap is at least 12px (--gw-target-min less 2rem), so two 32px buttons' hit areas meet without overlapping. --gw-row-target-gap: 0px turns it off; with a mouse nothing changes.
  • On a touch screen, every gw-segmented option is at least 44px across, not only with overflow.
  • On a touch screen, gw-calendar's days (and gw-date-picker's) are 44px rather than 40px, still shrinking so seven fit across a phone.
  • On a touch screen, gw-checkbox and gw-switch are at least 44px tall, so ones stacked in a list don't overlap each other's hit areas.

Added

  • --gw-row-target-gap on gw-row: the least gap on a touch screen.

Fixed

  • gw-table's sort buttons were their text's height, about 17px, with nothing past their edges. The whole heading cell is now the button's hit area, so it reaches the target without reaching into the heading beside it or the first row.
  • Fields had no hit area past their edges, so the table's search field and other short fields were under 44px on a touch screen. gw-input, gw-select and gw-date-picker now take a press just above or below them, keeping their look, and a press there focuses the input. The password reveal button and the (i) button get hit areas too, the (i) one never reaching over the field.
  • gw-option-list's search row (in a searchable select) focuses its field from anywhere in the row.
  • gw-app-bar's menu button and gw-section's collapse toggle had no hit area past their edges.
  • gw-code's toolbar buttons overlapped each other's hit areas, and gw-banner cut its buttons' hit areas off; both make room on a touch screen now.
  • gw-control-group's sections reached into their neighbors; each is now at least --gw-target-min wide.

Docs

  • Spacing: Touch targets lists what grows on a touch screen (fields, toggle options, calendar days, control group sections, table headings and row gaps) and how to turn each off.
  • The groundwork-interfaces skill's touch target item says how a tight toolbar keeps hit areas apart: max(gap, --gw-target-min less the controls' height).