How do blocks become real C++ code?

The short answer

Blocks are not “toy syntax” — they are a visual shell around real C++. Every block corresponds to a piece of actual C++ code, and the code pane updates as you snap blocks together. Blocks simply change the order of learning: understand the structure first, meet the syntax second.

How the blocks are grouped

The toolbox groups blocks by topic and colour-codes them, so you never hunt through a flat list:

• Program structure — program skeleton and statement order
• Input / output — print to the console, read input
• Initialisation & data types — integers, decimals, characters, booleans
• Operators — arithmetic, comparison, logic
• Control structures — conditions and loops
• Functions — definition and calls
• Arrays & strings, pointers & references, structs
• Algorithms — classic patterns, enumeration simulation, sorting, binary search

The grouping follows the usual teaching order of C++ textbooks, so learners build a “think in modules” habit instead of random trial and error.

Three stages: from dragging to typing

1. Watch the shape. Ignore the code for now; focus on how blocks snap and what the program outputs. This builds intuition about “order → result”.
2. Read the mapping. Start watching the code pane and match “this block = this line”. Run after every few blocks and compare the output with your expectation.
3. Drop the blocks. Try rewriting the same logic in the code editor page without looking; when stuck, switch back and compare. This is the cheapest route from blocks to hand-written code.

Two features people miss

1. Live code preview

The build area and the code area are always in sync. Do not wait until the end to look at the code — reading it while building is what makes the syntax stick.

2. Exporting block snapshots

You can export the current block structure as a JSON snapshot: handy for backups, for sharing with classmates, or for a teacher who wants to hand out a template that students continue from.

FAQ