What each frus release brings
View All Tags
The system around the window, screen readers, and phones on any computer. An application now reaches what a desktop offers beyond its window; a screen reader can use it on every platform, the web included; and a phone or a tablet can be tried on any computer.
Tooling, start-up and pictures. The frus command grows from creating a project into the whole
loop, true hot reload on every platform included. Applications start faster and survive a lost
GPU, and pictures are decoded at the size they are shown.
The first release since the crates went on crates.io, and a large one: three weeks of reviewing widgets and painting one by one, and of adding the pieces that were simply missing. It breaks things, as a pre-alpha release may.
A short release, and a milestone: from 0.2.1, the ten library crates are on crates.io, and an application depends on frus with one line.
The second tagged release, 286 milestones after the first. It is still not an API commitment, but frus moves a long way from where 0.1.0 left it: applications are made of components now, with a router whose location is the browser's address.
The first tagged release: a point in the history that can be cited, cloned and diffed. 277 milestones went into it. It is not an API commitment: nothing here is stable yet, and the public surface will move.