한국분은 An introduction for WPF NodeGraph( Korean ) 를 참고하세요.
Sample Project : https://github.com/lifeisforu/NodeGraph/raw/master/Documents/NodeGraphCalculator.zip
Nuget Release :
WPF control librarty for node graph.
This library is inspired by a BlueprintEditor of UnrealEngine4. Below image shows a snapshot of a sample using this library. It makes two integers as array, and print values in top-left corner of screen during loop.
A node can be divided as 3 parts, shown in below image; Node itself, FlowPorts, PropertyPorts.
- A FlowPort is used for specifying a execution flow between two nodes. The connection can be made for a FlowPort with different direction. For example, an input FlowPort can be connected with an output FlowPort.
- A PropertyPort is used for specifying data-transfer between two nodes. The connection can be made for a PropertyPort with differenct direction. For example, an input PropertyPort can be connected with an output PropertyPort.
This provide below features:
- Creating/Destroying FlowChart.
- Creating/Destroying Node.
- Custom Node ViewModel and Styling.
- Creating/Destroying NodeFlowPort.
- Custom NodeFlowPort ViewModel and Styling.
- Supporting PropertyEditor for default types( bool, byte, short, int, long, float, double, string, enum, Media.Color, etc. I will add more type editors in the future and have a plan to support custom editor ).
- Creating/Destroying NodePropertyPort.
- Custom NodePropertyPort ViewModel and Styling.
- Creating/Destroying Connector.
- Custom Connector ViewModel and Styling.
- Supporting Zoom & Pan.
- Supporting miscellaneous selection mode.
- Supporting History( undo/redo ).
- Serialization/Deserialization for XML.
First, in solution explorer, open context menu and select "Manage Nuget Packages...".
And, in filter text box, search "nodegraph" and press a "Install" button.
Then, popup window will be opened. And it shows you that "Lifeisforu.NodeGraph" and "PropertyTools.Wpf" will be installed.
And then assemblies will be added in "References".
- Drag-Drop between ports : Connects.
- Ctrl + Left on port : Disconnects.
-
Left : Select node and deselect all.
-
Ctrl + Left : XOR selection.
-
Shift + Left : Additive selection.
-
Alt + Left : Subtractive selection.
-
Ctrl + Left Dragging : XOR selection.
-
Shift + Left Dragging : Additive selection.
-
Alt + Left Dragging: Subtractive selection.
-
Ctrl + "A" : Select all nodes.
- "Delete" : Delete selected nodes.
- "F" : Focus selected nodes.
- "A" : Focus all nodes.
- Right Dragging on flowchart : Panning.
NodeGraph supports MVVM( Model-View-ViewModel ) pattern.
All Model classes have their own attribute. I'll explain it later, all attributes could override ViewModel.
If you don't need special ViewModel or View, you can create node with basic appearances and behaviors just by adding attributes.
Creating FlowChartView is start by adding NodeGraph.dll assembly as your project's reference. If you already downloaded it with Nuget Manager, it is not needed( Notice : Don't forget add "PropertyTools.Wpf" ).
Then, you can add a namespace in XAML of a Visual element. As you can see above, Model, View, ViewModel namespaces exsit. So you should add namespace for View. In my case, I have added name of "ngv". And then you can add "FlowChartView".
"NodeGraphSamples/MainWindow.xaml"
<Window x:Class="NodeGraphSamples.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:local="clr-namespace:NodeGraphSamples"
xmlns:ngv="clr-namespace:NodeGraph.View;assembly=NodeGraph"
mc:Ignorable="d"
Title="MainWindow" Height="450" Width="800">
<Grid>
<ngv:FlowChartView DataContext="{Binding Path=FlowChartViewModel,
RelativeSource={RelativeSource AncestorType={x:Type local:MainWindow}}}"/>
</Grid>
</Window>All Model instances in NodeGrpah could be created only by NodeGraphManager.
"NodeGraphSamples/MainWindow.xaml.cs"
public NodeGraph.ViewModel.FlowChartViewModel FlowChartViewModel
{
get { return ( NodeGraph.ViewModel.FlowChartViewModel )GetValue( FlowChartViewModelProperty ); }
set { SetValue( FlowChartViewModelProperty, value ); }
}
public static readonly DependencyProperty FlowChartViewModelProperty =
DependencyProperty.Register( "FlowChartViewModel", typeof( NodeGraph.ViewModel.FlowChartViewModel ),
typeof( MainWindow ), new PropertyMetadata( null ) );
[...]
private void MainWindow_Loaded( object sender, RoutedEventArgs e )
{
NodeGraph.Model.FlowChart flowChart = NodeGraph.NodeGraphManager.CreateFlowChart(
false, Guid.NewGuid(), typeof( NodeGraph.Model.FlowChart ) );
FlowChartViewModel = flowChart.ViewModel;
[ ... ]
}If you create FlowChart instance, FlowChartViewModel is created automatically with it. So you can bind it.
NodeGraphManager.CreateFlowChart() is defined as below.
"NodeGraph/NodeGraphManager.cs"
/// <summary>
/// Create FlowChart with FlowChartViewModel.
/// </summary>
/// <param name="isDeserializing">Is in deserializing routine?
/// If it is true, OnCreate() callback will not be called, otherwise OnPostLoad will be called.</param>
/// <param name="guid">Guid of this FlowChart.</param>
/// <param name="flowChartModelType">Type of FlowChart to be created.</param>
/// <returns>Created FlowChart instance</returns>
public static FlowChart CreateFlowChart( bool isDeserializing, Guid guid, Type flowChartModelType )<About all other parameters, I'll explain them later in other articles. Let's look third parameter. It specifices type of FlowChart. It is important, becuase it's attribute determines ViewModel of FlowChart.
For example, a basic FlowChart class is defined as below.
"NodeGraph/Model/FlowChart.cs"
[FlowChart()]
public class FlowChart : ModelBase
{
[ ... ]
}FlowChartAttribute class is defined as below.
"NodeGraph/Model/FlowChartAttribute.cs"
[AttributeUsage( AttributeTargets.Class )]
public class FlowChartAttribute : Attribute
{
public Type ViewModelType = typeof( FlowChartViewModel );
public FlowChartAttribute()
{
if( !typeof( FlowChartViewModel ).IsAssignableFrom( ViewModelType ) )
throw new ArgumentException( "ViewModelType of FlowChartAttribute must be subclass of FlowChartViewModel" );
}
}If you want, you can override ViewModelType. CreateFlowChart() will get ViewModel from the attribute.
By now, you can see an empty FlowChartView.
Now, let's create nodes. By now, we don't have UI which could create nodes. So, we will create node with ContextMenu.
First, add ContextMenu-related event handlers to MainWindow.
"NodeGraphSamples/MainWindow.xaml.cs"
private void MainWindow_Loaded( object sender, RoutedEventArgs e )
{
[ ... ]
NodeGraphManager.BuildFlowChartContextMenu += NodeGraphManager_BuildFlowChartContextMenu;
NodeGraphManager.BuildNodeContextMenu += NodeGraphManager_BuildNodeContextMenu;
NodeGraphManager.BuildFlowPortContextMenu += NodeGraphManager_BuildFlowPortContextMenu;
NodeGraphManager.BuildPropertyPortContextMenu += NodeGraphManager_BuildPropertyPortContextMenu;
[ ... ]
}Then, when NodeGraphManager_BuildFlowChartContextMenu event invoked, add menu items to ContextMenu.
"NodeGraphSamples/MainWindow.xaml.cs"
List<Type> _NodeTypes = new List<Type>()
{
typeof( Model.AutoOutputFlow ),
typeof( Model.AutoInOutFlow ),
typeof( Model.DynamicOutputFlow ),
typeof( Model.AutoNodeProperty ),
typeof( Model.DynamicNodeProperty ),
};
private Point _ContextMenuLocation;
private bool NodeGraphManager_BuildFlowChartContextMenu( object sender, BuildContextMenuArgs args )
{
ItemCollection items = args.ContextMenu.Items;
_ContextMenuLocation = args.ModelSpaceMouseLocation;
items.Clear();
foreach( var nodeType in _NodeTypes )
{
MenuItem menuItem = new MenuItem();
var NodeAttrs = nodeType.GetCustomAttributes( typeof( NodeAttribute ), false ) as NodeAttribute[];
if( 1 != NodeAttrs.Length )
throw new ArgumentException( string.Format( "{0} must have NodeAttribute", nodeType.Name ) );
menuItem.Header = "Create " + NodeAttrs[ 0 ].Header;
menuItem.CommandParameter = nodeType;
menuItem.Click += FlowChart_ContextMenuItem_Click;
items.Add( menuItem );
}
return ( 0 < items.Count );
}In above code snippets, types in _NodeTypes are pre-defined nodes I have been created. The mechanism is simple. While iterating _NodeTypes, get NodeAttribute attribute from each type. NodeAttribute contains appearances info of the node, among them, select "Header" field and set it as Header of MenuItem. And pass node's type to CommandParameter. It is to create a node with the type, when we click the menu item. _ContextMenuLocation is used for position of the node that will be created.
Now, you can see ContextMenu when you click mouse right button.
What will happen, if you click "Create AutoOutputFlow" item. Let's find out.
"NodeGraphSamples/MainWindow.xaml.cs"
protected virtual void FlowChart_ContextMenuItem_Click( object sender, RoutedEventArgs e )
{
MenuItem menuItem = sender as MenuItem;
Type nodeType = menuItem.CommandParameter as Type;
NodeGraph.View.FlowChartView flowChartView = FlowChartViewModel.View;
Point nodePos = flowChartView.ZoomAndPan.MatrixInv.Transform(
new Point( _ContextMenuLocation.X, _ContextMenuLocation.Y ) );
Node node = NodeGraphManager.CreateNode(
false, Guid.NewGuid(), FlowChartViewModel.Model, nodeType, nodePos.X, nodePos.Y, 0 );
}As mentioned earlier, "ALL" Model instances must be created by NodeGraphManager. In here, we could call NodeGraphManager.CreateNode() method.
This method is defined as below.
"NodeGraph/NodeGraphManager.cs"
/// <summary>
/// Create Node with NodeViewModel.
/// </summary>
/// <param name="isDeserializing">Is in deserializing routine?
/// If it is true, OnCreate() callback will not be called, otherwise OnPostLoad will be called.
/// If it is true, Node's attribute will not be evaluated. That means flows and properties will not be created automatically by attributes.
/// All flows and properties will be created during deserialization process.</param>
/// <param name="guid">Guid for this Node.</param>
/// <param name="flowChart">Owner FlowChart.</param>
/// <param name="nodeType">Type of this node.</param>
/// <param name="x">Location along X axis( Canvas.Left ).</param>
/// <param name="y">Location along Y axis( Canvas.Top )</param>
/// <param name="ZIndex">Z index( Canvas.ZIndex ).</param>
/// <param name="nodeViewModelTypeOverride">NodeViewModel to override.</param>
/// <param name="flowPortViewModelTypeOverride">FlowPortViewModel to override.</param>
/// <param name="propertyPortViewModelTypeOverride">PropertyPortViewmodel to override.</param>
/// <returns>Created node instance.</returns>
public static Node CreateNode( bool isDeserializing, Guid guid, FlowChart flowChart,
Type nodeType, double x, double y, int ZIndex,
Type nodeViewModelTypeOverride = null, Type flowPortViewModelTypeOverride = null,
Type propertyPortViewModelTypeOverride = null )In this method, it has not only Node type but also XXXOverride types. Becuase I predict that, in the case of Node, ViewModel of Nodes are frequently replaced with other type of ViewModel, so I make additional ViewModel types. About the exmaple of this case, I will explain it later in other articles.
In above code snippets, to determine node's lcoation, you can see that I used a MatrixInv. Becuase mouse position is in ViewSpace, we must transform it to model space. These codes are a bit messy, in later, I have a plan to add some method like NodeGraphManager.CreateNodeViewSpace().
Anyway, if you click "Create AutoOutputFlow", you can see that a node named "AutoOutputFlow" will be created.
Let's see an implementation of this class.
"NodeGraphSample/Model/AutoOutputFlow"
[Node()]
[NodeFlowPort( "Output", "", false )]
public class AutoOutputFlow : Node
{
#region Constructor
/// <summary>
/// Never call this constructor directly. Use Node.Create() method.
/// </summary>
public AutoOutputFlow( Guid guid, FlowChart flowChart ) : base( guid, flowChart )
{
Header = "AutoInOutFlow";
HeaderBackgroundColor = Brushes.Maroon;
}
#endregion // Constructor
}So Simple!!! There are two attributes and one construtor. You just need to define a class with attributes.
In Constructor you can specify Header, HeaderBackgroundColor, HeaderFontColor, and in NodeAttribute you can specify ViewModel.
"NodeGraph/Model/NodeAttribute"
[AttributeUsage( AttributeTargets.Class | AttributeTargets.Struct | AttributeTargets.Enum )]
public class NodeAttribute : Attribute
{
public Type ViewModelType = typeof( NodeViewModel );
public string Header;
public string HeaderBackgroundColor = "Black";
public string HeaderFontColor = "White";
public bool AllowCircularConnection = false;
public NodeAttribute( string header )
{
Header = header;
if( !typeof( NodeViewModel ).IsAssignableFrom( ViewModelType ) )
throw new ArgumentException( "ViewModelType of NodeAttribute must be subclass of NodeViewModel" );
}
}There is an output FlowPort in AutoOutputFlow node. It is automatically added by adding attribute like below.
"NodeGraph/Model/NodeFlowPortAttribute.cs"
[AttributeUsage( AttributeTargets.Class | AttributeTargets.Struct | AttributeTargets.Enum, AllowMultiple = true ) ]
public class NodeFlowPortAttribute : NodePortAttribute
{
public Type ViewModelType = typeof( NodeFlowPortViewModel );
public NodeFlowPortAttribute( string name, string displayName, bool isInput ) : base( displayName, isInput )
{
Name = name;
AllowMultipleInput = true;
AllowMultipleOutput = false;
if( !typeof( NodeFlowPortViewModel ).IsAssignableFrom( ViewModelType ) )
throw new ArgumentException( "ViewModelType of NodeFlowPortAttribute must be subclass of NodeFlowPortViewModel" );
}
}NodeFlowPortAttribute is derived from NodePortAttribute. It defines common appearances and behavior of a port.
"NodeGraph/Model/NodePortAttribute.cs"
[AttributeUsage( AttributeTargets.Class | AttributeTargets.Struct | AttributeTargets.Enum )]
public class NodePortAttribute : Attribute
{
public string Name = string.Empty;
public string DisplayName = string.Empty;
public bool IsInput = false;
public bool AllowMultipleInput = false;
public bool AllowMultipleOutput = false;
public NodePortAttribute( string displayName, bool isInput )
{
DisplayName = displayName;
IsInput = isInput;
}
}Now, Let's create a node with PropertyPort. If you click "Create AutoNodeProperty", below node will be created.
As you can expect, this is acheived by adding simple attribute.
"NodeGraphSamples/Model/AutoNodeProperty.cs"
[Node()]
[NodeFlowPort( "Input", "", true )]
[NodeFlowPort( "Output", "", false )]
public class AutoNodeProperty : Node
{
#region Input Properties
[NodePropertyPort( "Input 0", typeof( double ), true, DefaultValue = 0.0 )]
public double InputValue0;
[NodePropertyPort( "Input 1", typeof( double ), true, DefaultValue = 0.0 )]
public double InputValue1;
#endregion // Input Properteis
#region Output Properties
[NodePropertyPort( "Output 0", typeof( double ), false, DefaultValue = 0.0 )]
public object OutputValue0;
[NodePropertyPort( "Output 1", typeof( double ), false, DefaultValue = 0.0 )]
public object OutputValue1;
[NodePropertyPort( "Output 2", typeof( double ), false, DefaultValue = 0.0 )]
public object OutputValue2;
#endregion // Output Properties
#region Constructor
/// <summary>
/// Never call this constructor directly. Use Node.Create() method.
/// </summary>
public AutoNodeProperty( Guid guid, FlowChart flowChart, bool allowCircularConnection ) : base( guid, flowChart, allowCircularConnection )
{
Header = "AutoInOutFlow";
HeaderBackgroundColor = Brushes.DarkBlue;
}
#endregion // Constructor
}NodePropertyPortAttribute is derived from NodePortAttribute. And it is defined as below.
"NodeGraphSamples/Model/NodePropertyPortAttribute.cs"
[AttributeUsage( AttributeTargets.Field | AttributeTargets.Property )]
public class NodePropertyPortAttribute : NodePortAttribute
{
public Type Type;
public Type ViewModelType = typeof( NodePropertyPortViewModel );
public object DefaultValue;
public NodePropertyPortAttribute( string displayName, Type type, bool isInput ) : base( displayName, isInput )
{
Type = type;
IsInput = isInput;
AllowMultipleInput = false;
AllowMultipleOutput = true;
if( !typeof( NodePropertyPortViewModel ).IsAssignableFrom( ViewModelType ) )
throw new ArgumentException( "ViewModelType of NodePropertyAttribute must be subclass of NodePropertyPortViewModel" );
}
}By now, I have introduced about static creation of FlowPort by using attributes. But you can create a FlowPort dynamically. If you click "Create DynmaicOutputFlow", below node will be created.
Two FlowPorts are statically created by attributes, and 1 FlowPort( DynamicMulipleOutput ) is dynamically created.
"NodeGraphSamples/Model/DynamicOutputFlow.cs"
[Node( "DynamicOutputFlow", HeaderBackgroundColor = "Maroon", HeaderFontColor = "White" )]
[NodeFlowPort( "Input", "AutoInput", true )]
[NodeFlowPort( "Output", "AutoOutput", false )]
public class DynamicOutputFlow : Node
{
[ ... ]
#region Overrides Node
public override void OnCreate()
{
base.OnCreate();
NodeGraphManager.CreateNodeFlowPort( false, Guid.NewGuid(), this, "Output2", "DynamicMultipleOutput", false, false, true );
}
#endregion // Overrides Node.
}In OnCreate() method, you can see that NodeGraphManager.CreateNodeFlowPort() create a port. Most parameters are same with fields of attributes.
"NodeGraph/NodeGraphManager.cs"
/// <summary>
/// Create NodeFlowPort with NodeFlwoPortViewModel.
/// </summary>
/// <param name="isDeserializing">Is in deserializing routine?
/// If it is true, OnCreate() callback will not be called, otherwise OnPostLoad will be called.</param>
/// <param name="guid">Guid for this port.</param>
/// <param name="node">Owner of this port.</param>
/// <param name="name">Name of port.</param>
/// <param name="displayName">Display name of port.</param>
/// <param name="isInput">Is input port?</param>
/// <param name="allowMultipleInput">Multiple inputs are allowed for this port?</param>
/// <param name="allowMultipleOutput">Multiple outputs are allowed for this port?</param>
/// <param name="portViewModelTypeOverride">ViewModelType to override.</param>
/// <returns>Created NodeFlwoPort instance.</returns>
public static NodeFlowPort CreateNodeFlowPort( bool isDeserializing, Guid guid, Node node, string name,
string displayName, bool isInput, bool allowMultipleInput, bool allowMultipleOutput,
Type portViewModelTypeOverride = null )PropertyPort can be also created dynamically. If you click "Create DynamicNodeProperty", below node will be created.
One dynamic input PropertyNode, and one dynamic output PropertyNode are created.
"NodeGraphSamples/Model/DynamicNodeProperty.cs"
public struct MyStruct
{
public bool Bool;
public int Int32;
public double Double;
};
[Node()]
[NodeFlowPort( "Input", "", true )]
[NodeFlowPort( "Output", "", false )]
public class DynamicNodeProperty : Node
{
[ ... ]
#region Overrides Node
public override void OnCreate()
{
base.OnCreate();
NodeGraphManager.CreateNodePropertyPort(
false, Guid.NewGuid(), this, "Input1", "Dynamic Input 1", true, false, false,
typeof( double ), 0.0 );
NodeGraphManager.CreateNodePropertyPort(
false, Guid.NewGuid(), this, "Output2", "Dynamic Output 2", false, false, true,
typeof( MyStruct ), new MyStruct() );
}
#endregion // Overrides Node
}You can see that NodeGraphManager.CreateNodePropertyPort() creates nodes.
"NodeGraph/NodeGraphManager.cs"
/// <summary>
/// Create PropertyPort with PropertyPortViewModel.
/// </summary>
/// <param name="isDeserializing">Is in deserializing routine?
/// If it is true, OnCreate() callback will not be called, otherwise OnPostLoad will be called.</param>
/// <param name="guid">Guid for this port.</param>
/// <param name="node">Owner of this port.</param>
/// <param name="name">Name of port.</param>
/// <param name="displayName">Display name of port.</param>
/// <param name="isInput">Is input port?</param>
/// <param name="allowMultipleInput">Multiple inputs are allowed for this port?</param>
/// <param name="allowMultipleOutput">Multiple outputs are allowed for this port?</param>
/// <param name="valueType">Type of property value.</param>
/// <param name="defaultValue">Default property value.</param>
// <param name="portViewModelTypeOverride">ViewModelType to override.</param>
/// <returns>Created NodePropertyPort instance.</returns>
public static NodePropertyPort CreateNodePropertyPort( bool isDeserializing, Guid guid, Node node, string name,
string displayName, bool isInput, bool allowMultipleInput, bool allowMultipleOutput,
Type valueType, object defaultValue, Type portViewModelTypeOverride = null )Elements of NodeGraph are categorized by Model-View-ViewModel. ALL Model instances are created by NodeGraphManager, it also create ViewModel instances. And ViewModels determine their Views.
Model class specify type of ViewModel, and appearances info is determined statically by attributes or dynamically by calling methods of NodeGraphManager.