What ships
Inspect the exact source folders, plugin DLLs, and package dependencies included with Round Trip 0.89.0.
On this page
A Unity package can look like one black box in Package Manager. Round Trip has a sharper boundary: the parsing and source-writing engine is compiled, while its Unity editor integration is readable package source.
The package at a glance
Section titled “The package at a glance”The package id is io.bitquirky.roundtrip.engine. Version 0.89.0 declares Unity 2022.3 as its minimum and depends on:
| Package | Version | Job |
|---|---|---|
io.bitquirky.graph |
0.2.71 | Shared UI Toolkit graph canvas and graph preferences. |
com.unity.vectorgraphics |
2.0.0-preview.25 | Vector graphics support used by the Unity UI. |
Source you can read
Section titled “Source you can read”The package’s Unity integration ships as C# source. The exact top-level source and support folders under Editor/ are:
| Folder | Contents |
|---|---|
Authoring/ |
Class, method, declaration, source-edit, and authoring windows and services. |
Controls/ |
Explorer with its rails and inspector. This folder also holds the action menu, pending-changes panel and other editor controls. |
Git/ |
Method-row diff and restore actions, plus controls to stage or unstage. |
GraphPipeline/ |
Method graph conversion and render decisions. Comments and picker indexes also live here. |
GraphView/ |
Canvas interaction code, reroute views, manipulators, and variable drag support. |
Lifecycle/ |
Unity lifecycle definitions and settings seeding. |
Models/ |
Unity editor view state. |
Services/ |
Unity object and default-reference resolution. |
Undo/ |
Reversible graph editing actions. |
Usage/ |
Component usage and scene scanning. |
VersionControl/ |
Provider detection and changed-file status. |
Resources/ |
Round Trip UI Toolkit styles and product image resources. |
Icons/ |
Toolbar and authoring vector icons. |
Editor/ also contains root source files such as GraphControlWindow.cs, ClassIndexer.cs, RoundTripProjectSettings.cs, RoundTripGraphPreferences.cs, menu items, setup, asset paths, and the editor assembly definition.
The exact source and support folders under Runtime/ are:
| Folder or file | Contents |
|---|---|
Diagnostics/ |
Unity logging adapters. |
Lifecycle/ |
Runtime lifecycle settings records. |
Plugins/ |
The one compiled DLL set, used by both the runtime and editor assemblies. |
UnityExternalLayoutRoots.cs |
External source-root mapping for graph configuration. |
UnityLayoutStore.cs |
Unity host adapter for layout persistence. |
RoundTripGuardSettings.cs |
Serializable guard settings. |
RoundTripFieldDefaultsSettings.cs |
Serializable Field Defaults settings. |
io.bitquirky.roundtrip.engine.asmdef |
Runtime assembly definition. |
Compiled plugins
Section titled “Compiled plugins”Runtime/Plugins contains the compiled DLL set. Its import settings make it available to the Unity editor as well:
| DLL |
|---|
RoundTrip.Core.dll |
RoundTrip.Engine.dll |
Microsoft.Msagl.dll |
Microsoft.CodeAnalysis.dll |
Microsoft.CodeAnalysis.CSharp.dll |
Microsoft.CodeAnalysis.resources.dll |
Microsoft.CodeAnalysis.CSharp.resources.dll |
Microsoft.Bcl.AsyncInterfaces.dll |
System.Buffers.dll |
System.Collections.Immutable.dll |
System.Memory.dll |
System.Numerics.Vectors.dll |
System.Reflection.Metadata.dll |
System.Runtime.CompilerServices.Unsafe.dll |
System.Text.Encoding.CodePages.dll |
System.Text.Encodings.Web.dll |
System.Text.Json.dll |
System.Threading.Tasks.Extensions.dll |
The parser, graph layout, JSON persistence, and source writer are compiled. Every editor extension and Unity integration is source you can read and extend.
One plugin folder
Section titled “One plugin folder”The runtime and editor assemblies both load the shared model and engine dependencies from Runtime/Plugins. Earlier versions shipped an identical second copy under Editor/Plugins; removing it halved the package download without changing what either assembly loads.
The lower layers contain no Unity types. Unity-specific indexing, settings, object references, menus, controls, and window behavior stay in package source above that boundary.