See how your C#, the Unity package source, the compiled engine, and the shared canvas fit together.
UnderstandUpdated
On this page
Your own C# files sit at the top because they own the game’s behavior. Round Trip reads and shows them, then writes narrow changes back to them when you press Compile. The diagram uses ScoreCounter.cs from the Platformer sample as the example file.
Your C# stays above the Unity integration, while Core and Engine provide the model, C# parsing, layout, storage, and source-writing work underneath.
The middle layer is the Unity package source: the Explorer, UI Toolkit controls, indexing, settings, menus, and host adapters under Editor/ and Runtime/. You can read and extend that integration.
Under it sit RoundTrip.Core.dll and RoundTrip.Engine.dll plus their dependencies. Core defines the model of methods, nodes, pins, and connections. Engine reads C#, lays out diagrams, stores JSON settings, supports visual editing, and writes source changes. Neither layer depends on Unity types.
Beside the Unity integration is the io.bitquirky.graph package, which supplies the shared graph canvas and, on Unity 2022.3, loads the package’s SVG icons from their source. com.unity.vectorgraphics supplies vector rendering support.