Skip to content
This repository was archived by the owner on Nov 7, 2026. It is now read-only.

Commit 08fcb21

Browse files
committed
Web 0.14.19: Bild mit Papier und Stift im Schreibtischtest (L7)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ugz28X1RBduq7uP6sxyG18
1 parent d492d9e commit 08fcb21

15 files changed

Lines changed: 860 additions & 679 deletions

‎CHANGELOG.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ The format is loosely inspired by Keep a Changelog.
88

99
### Changed
1010

11+
- **Web 0.14.19, picture for the desk check:** lesson 7, step „Der Schreibtischtest“, shows a hand-drawn sheet of paper with the swap trace table (a, b, hilf/temp/aux) and a pencil, own SVGs `l07-schreibtischtest-{de,en,pt}.svg` (de/en/pt).
1112
- **Web 0.14.18, upper and lower case, exercises „Warum läuft das nicht?“:** lesson 4 gets the new step „Groß- und Kleinschreibung“ (case-sensitive: `zahl`, `Zahl` and `ZAHL` are three names) with a structure chart exercise (`zahl` and `Zahl` both declared, `ZAHL` used), a Kompetenz item and a quiz question; glossary entry case-sensitive. Lessons 4–17 and 19 each get a Java exercise „Warum läuft das nicht?“: the start code doesn't run (misspelled variable such as `Alter`/`Grenze`/`properson`, variable used before it is created or never created, `system.out`, `.Length`, `charat`), the student reads the error message, fixes it and clicks Check (de/en/pt). The Code area now reports wrong case in Java words (`system.out.println`, `System.Out`, `Println`, `math.sqrt`, `text.Length()`, `name.charat(0)`) with the right spelling, blocks Run like javac and offers the 💡 fix; the simulation says „Unbekannte Variable: Zahl. Java unterscheidet Groß- und Kleinschreibung: Meintest du zahl?“ when the name exists in another case (all 21 languages).
1213
- **Web 0.14.17, hint on a missing line break:** when a Java exercise's output is right except that lines run together (e.g. `System.out.print` twice instead of `println`), the check now says „Fast! Es fehlt nur ein Zeilenumbruch …“ and explains print vs. println, instead of only showing a mismatch. `\n` inside an output now starts a new line, so `System.out.print("…\n")` counts like `println` (de/en/pt; all exercises).
1314
- **Web 0.14.16, „Im Editor öffnen“ under the Java examples in lessons 4–19:** every runnable Java example in the lesson text of lessons 4–19 now has the button „Im Editor öffnen“ (like the Mia example in lesson 4), so students can run and change it in Programmieren. Not in lesson 18, whose examples are a method and its call on their own, and not in cloze texts or games (de/en/pt).
Lines changed: 52 additions & 0 deletions
Loading
Lines changed: 52 additions & 0 deletions
Loading
Lines changed: 52 additions & 0 deletions
Loading

‎web/lessons/de/07-simulation-und-schreibtischtest.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,10 @@ Am Ende erscheint **Simulation beendet**. Geht etwas schief, bleibt die Simulati
5050

5151
Beim **Schreibtischtest** spielst du selbst den Computer. Du gehst das Struktogramm mit Stift und Papier durch und schreibst nach jedem Schritt die Werte der Variablen auf. Am besten machst du eine Tabelle: eine Spalte für den Schritt, eine für jede Variable und eine für die Ausgabe.
5252

53+
::: grafik l07-schreibtischtest-de.svg
54+
Ein Blatt Papier und ein Stift genügen: Du schreibst nach jedem Schritt die neuen Werte in eine neue Zeile.
55+
:::
56+
5357
Für das Diagramm oben sieht die Tabelle so aus:
5458

5559
| Schritt | a | b | hilf | Ausgabe |

‎web/lessons/en/07-simulation-und-schreibtischtest.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,10 @@ At the end, **Simulation finished.** appears. If something goes wrong, the simul
5050

5151
In a **desk check** you play the computer yourself. You go through the structure chart with pen and paper and write down the values of the variables after every step. It is best to make a table: one column for the step, one for each variable and one for the output.
5252

53+
::: grafik l07-schreibtischtest-en.svg
54+
A sheet of paper and a pen are all you need: after each step you write the new values in a new row.
55+
:::
56+
5357
For the diagram above, the table looks like this:
5458

5559
| Step | a | b | temp | Output |

‎web/lessons/pt/07-simulation-und-schreibtischtest.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,10 @@ No fim aparece **Simulação terminada.** Se algo correr mal, a simulação para
5050

5151
Num **teste de secretária** és tu o computador. Percorres o estrutograma com papel e caneta e anotas os valores das variáveis depois de cada passo. O melhor é fazer uma tabela: uma coluna para o passo, uma para cada variável e uma para a saída.
5252

53+
::: grafik l07-schreibtischtest-pt.svg
54+
Basta uma folha de papel e uma caneta: depois de cada passo escreves os novos valores numa nova linha.
55+
:::
56+
5357
Para o diagrama de cima, a tabela fica assim:
5458

5559
| Passo | a | b | aux | Saída |

‎web/package-lock.json‎

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎web/package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "visustruct-web",
33
"private": true,
4-
"version": "0.14.18",
4+
"version": "0.14.19",
55
"type": "module",
66
"scripts": {
77
"dev": "vite",

0 commit comments

Comments
 (0)