View-model driven graphs
MVVM Integration
Keep graph behavior in view models and visual composition in XAML.
Explore source ↗Capability
MVVM packages expose graph state, commands, selection, and connection workflows through bindable models suitable for application architecture and testing.
- 01
Bindable graph collections
- 02
Command-oriented editing
- 03
Testable selection and connection logic
- 04
XAML templates remain replaceable
How it composes
From intent
to working system.
Domain
Application models own graph meaning and data.
View model
Adapters expose position, sockets, commands, and notifications.
Binding
The editor binds to collections and selection state.
Template
Views render domain-specific nodes without changing the control.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package NodeEditorAvalonia.Mvvm<PackageReference Include="NodeEditorAvalonia.Mvvm" Version="VERSION" /><PackageVersion Include="NodeEditorAvalonia.Mvvm" Version="VERSION" />Nodes.Add(new NodeViewModel{ Title = "Transform", Position = new Point(320, 180)});Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.