backupRoswaal has moved to roswaal.app. These pages are a backup copy.Go to roswaal.app

0.60.x✎

Every toolbar is drawn, with its buttons named.

0.60.x2026-09-16

FeatureChangeBugfixEditorDesignerDocs

Every toolbar is drawn, with its buttons named.

Releases

  1. 0.60.4The canvas behind the graph toolbars reaches its own edges.New2026-09-16
  2. 0.60.3The graph toolbars float over a canvas again.New2026-09-16
  3. 0.60.2A drawn toolbar sits on the page rather than in the list.New2026-09-16
  4. 0.60.1A canary build says so, on every page.New2026-09-16
  5. 0.60.0Every toolbar is drawn, with its buttons named.New2026-09-16

Warning

Worth knowing before you upgrade.
  • 0.60.1Nothing changes for the stable build: it carries no canary mark, no banner and no noindex. If you are reading this anywhere but the canary site, none of it is on your screen.
  • 0.60.1The site workflow now takes its base path from the repository's own name rather than a hard-coded one, so both repositories publish correctly from the same file.
  • 0.60.0The bars are drawn in your own theme, at your own window width, rather than photographed — so a bar wider than the reading column scrolls sideways. The position of each control is written out in the list beneath it as well, which is what the page falls back on with no pointer and no script.
  • 0.60.0Nothing in a drawn bar does anything when you click it. It is a picture of a control, not the control.

Added

  • 0.60.1The canary channel. Roswaal now builds from two lines: the stable one, and a canary where work lands first. A canary build wears a yellow canary mark beside the version, on the editor, on Node Design and on the documentation — and carries a banner above them saying what that means, with a link to the stable build.
  • 0.60.1The documentation's canary says something sharper than the editor's: these pages describe a build that is not out, so what they say may not be in the version you have.
  • 0.60.1Canary pages are marked noindex, so the unreleased copy of the documentation does not compete with the real one in search results.
  • 0.60.0A new page under Getting started, Toolbars. Five bars drawn as they appear — the editor's top bar, the three floating groups over a graph, a node map's row, Node Design's header and this window's — each with every control named underneath it.
  • 0.60.0Docs, Node Design and Settings are named and placed. They are the last three icons on the editor's top bar, in that order, and the page says so in words as well as in the picture.
  • 0.60.0A table of how to get from any of the three windows to the other two.
  • 0.60.0The drawn bars point at their own documentation. Hover a control and its row in the list lights; hover a row and the control lights. Tapping one keeps it lit, and brings it into view if the bar has scrolled sideways.
  • 0.60.0Both editors are drawn. The editor's top bar, Node Design's header and the documentation's own header each carry a switch between the build the daemon serves and the one that runs in a browser tab.
  • 0.60.0Every window of the browser preview now says it is one. The preview chip sits beside the version in the editor and in Node Design, and the links into it — the front page's first button, and Try it in your browser in the documentation's header — carry it too. If you can see the chip, your project is kept in that browser rather than in your repository.

Changed

  • 0.60.3The drawn graph toolbars sit on a full pane of canvas, grid and all, rather than on a strip that stopped where the tools stopped. The whole point of that picture is that the three groups float over a view which carries on past them, and a canvas cut to the size of its contents said the opposite.
  • 0.60.2The drawn bars are inset from their frames on Toolbars, with their own corners and a little of the app's background around them. Flush against the list underneath, a bar read as that list's top row rather than as the thing the list is about — and a control nobody reads as a control is not one they think to hover.
  • 0.60.1The build mark is one rule with two variants rather than one mark with an exception. A build wears canary or preview, never both: an unfinished build is unfinished whether it is in a browser tab or on your own machine.
  • 0.60.1The front page's first button carries whichever mark the site was built from, and the sentence under it agrees with it.
  • 0.60.0The front page says what the browser preview is, under the button that opens it. Its own tag is still the version: Roswaal is not a preview, the thing behind that one button is.
  • 0.60.0Getting started and Controls point at the new page. Controls is the keyboard and the mouse; the buttons are on Toolbars.
  • 0.60.0Creating custom nodes names the button that opens Node Design rather than saying it is on the toolbar.

Fixed

  • 0.60.4The grid behind the drawn graph toolbars stopped level with the tools, leaving a bare band above and below it inside the frame. 0.60.3 put the canvas on the right element and the gap around the tools on the wrong one: a margin, which collapsed straight back out through the element painting the canvas, so the pane ended up exactly as tall as its contents. The gap is padding now, inside the thing that paints.
  • 0.60.1The test suite read which build it was being run for. The site workflow sets the channel for the whole job, so the two tests that asked the front page what it looked like got the canary's answer and failed — on the canary only, after passing on every machine. They state which build they mean now, and the suite pins the channel so nothing can read it by accident again.
  • 0.60.1The canary mark was drawn in the preview's colour. The chip read canary and was painted accent blue, because the rule that colours it in a toolbar is more specific than the rule that says which colour a canary is. The colour is chosen on the chip itself now, so no amount of chrome around it can overrule what it is claiming.
  • 0.60.0Node Design in the browser preview did not say it was the preview. It is a whole window of that build and carried nothing; the chip was a one-off in the editor's toolbar rather than a rule. It is one component now, and every surface of that build renders it.
  • 0.60.0In the browser preview, the Docs button said it would show this project's packs. It opens the published documentation, which is a static site with no registry behind it and documents the built-in library only. The tooltip now says so; the button is unchanged, and a project's own packs are still documented in the editor the daemon serves.

Verified Articles