|
1 | 1 | # @openpatch/java-memory-playground |
2 | 2 |
|
| 3 | +## 0.2.3 |
| 4 | + |
| 5 | +### Patch Changes |
| 6 | + |
| 7 | +- [`4c2c88a`](https://github.com/openpatch/java-memory-playground/commit/4c2c88a1cc48680c84027b343ef1766bba20284a) Thanks [@mikebarkmin](https://github.com/mikebarkmin)! - Lay the bottom bar out in rows, and make "Your turn" a heading. |
| 8 | + |
| 9 | + Everything was one wrapping row, so on an exercise step the prompt sat between the description and |
| 10 | + the buttons — the one place in the row where a call to action reads as a caption. The description |
| 11 | + competed with the controls for the same line, and on a narrow canvas the whole thing became a pile. |
| 12 | + |
| 13 | + The bar now has three parts: the prompt as a heading across the top of the card, the step's |
| 14 | + description under it, and the controls on their own line. The collector joins the end of that |
| 15 | + controls line rather than standing in a group of its own, so a plain diagram is still the single |
| 16 | + row it was, and the result of checking an exercise stays beside the button that produced it. |
| 17 | + |
| 18 | + The step bar dissolves into the bottom bar (`display: contents`) instead of being a box inside it, |
| 19 | + which is what lets the heading span the full width and the collector share the controls' line. It |
| 20 | + still stands on its own for anyone rendering the component outside the bar. |
| 21 | + |
| 22 | +- [`e5e2b33`](https://github.com/openpatch/java-memory-playground/commit/e5e2b336042025104bd1b83d3cce8fe58b0b487f) Thanks [@mikebarkmin](https://github.com/mikebarkmin)! - Show a step's whole label, and the whole result of checking an exercise. |
| 23 | + |
| 24 | + The label was clipped with an ellipsis at 260px. On an exercise step the label is the task, so a |
| 25 | + reader was being asked to build something the sentence no longer said — and the result of pressing |
| 26 | + Check listed the attributes that were wrong on a single unbreakable line. |
| 27 | + |
| 28 | + Both now wrap. They are also the only two things in the step bar allowed to give up width when the |
| 29 | + bar is short of it: a button cannot be read at half a word, but a sentence reads fine over three |
| 30 | + lines. The measure is capped so that a long note breaks into lines rather than stretching the bar |
| 31 | + across the canvas, and a Java identifier longer than the measure breaks mid-word rather than |
| 32 | + hanging out of the bar. |
| 33 | + |
| 34 | +- [`e5e2b33`](https://github.com/openpatch/java-memory-playground/commit/e5e2b336042025104bd1b83d3cce8fe58b0b487f) Thanks [@mikebarkmin](https://github.com/mikebarkmin)! - State the font size of the playground's own controls, so an embedded playground's toolbar is not |
| 35 | + resized by its host. |
| 36 | + |
| 37 | + Form controls do not inherit `font-size`, so in a page of its own the buttons and inputs sat at the |
| 38 | + browser's ~13px default and the container's 24px — the size the _diagram_ is drawn at — never |
| 39 | + reached them. A host page with a normalize stylesheet (`button, input { font-size: 100% }`) makes |
| 40 | + them inherit after all, and Save, Download (PNG) and the rest then came out at 24px. In a Hyperbook |
| 41 | + the toolbar was roughly twice the width of the diagram beneath it. |
| 42 | + |
| 43 | + The sizes are now written down rather than left to the browser, so they are the same wherever the |
| 44 | + playground is embedded. Nothing changes in the standalone app. |
| 45 | + |
3 | 46 | ## 0.2.2 |
4 | 47 |
|
5 | 48 | ### Patch Changes |
|
0 commit comments