Releases: Blazor-Diagrams/Blazor.Diagrams
Releases · Blazor-Diagrams/Blazor.Diagrams
3.0.0 beta 1
.NET 6!
A lot of things changed in this version, a lot of breaking changes were introduced but I believe it was necessary.
Many changes were required to make everything clearer, customizable and cleaner (code wise).
I'm aiming to completely decouple the Core library from the UI, because I'm thinking of giving MAUI Diagrams a try very soon!
https://www.nuget.org/packages/Z.Blazor.Diagrams.Core/3.0.0-beta.1
https://www.nuget.org/packages/Z.Blazor.Diagrams/3.0.0-beta.1
Added
BlazorDiagramclass (inheritsDiagram) to the blazor package to replace the old Core oneBlazorDiagramOptionsthat inherit from the other diagram options to add Blazor (UI) specific optionsBlazor.Diagrams.Models.SvgNodeModelclass to represent a node that needs to be rendered in the SVG layerGetBehavior<T>method toDiagramin order to retrieve a registered behaviorKeyboardShortcutsBehaviorclass which handles keyboard shortcuts/actions:SetShortcut: sets an action (Func<Diagrambase, ValueTask>) to be executed whenever the specified combination is pressedRemoveShortcut: removes a defined action (if it exists)
KeyboardShortcutsDefaultscontaining the default shortcuts that were deleted (DeleteSelectionandGrouping)- Anchors functionality:
- An Anchor determines where on an element the link will connect
- Instead of links requiring the source and target to be either both nodes or both ports, there is now only one
SourceandTargetof typeAnchor - This lets the link not worry about the details of from/to where its going, as long as the anchor provides it with its position when asked for
- Current implementations:
SinglePortAnchor: Specifies that the connection point is a specific port (supports shape & alignment)ShapeIntersectionAnchor: Specifies that the connection point is the intersection of a line with the node's shapeDynamicAnchor: Specifies that the connection point is one of the given positions (closest)
- Virtual
IShape GetShape()method on nodes (defaultRectangle) and ports (defaultCircle) Options.LinksLayerOrderto indicate the order of the links layer (svg for blazor)Options.NodesLayerOrderto indicate the order of the nodes layer (html for blazor)- Support for SVG groups that also represent children as a hierarchy (
SvgGroupModel) - Node renderer will now append, in addition to
node locked, the classesselected grouped IHasBoundsandIHasShapeinterfaces to both nodes and portsIPositionProviderto encapsulate how certain positions are calculated given a model- They are used for dynamic anchors and controls for now
BoundsBasedPositionProviderreturns the position based on the bounds of the model (e.g. (0.5, 0.5) would be the center)ShapeAnglePositionProviderreturns the position as the point at the angle of the shapeLinkPathPositionProviderreturns the position based on the link's path (getPointAtLength)
- Links have a reference to
Diagramnow PointerEnterandPointerLeaveevents for nodes and links for nowGeneratedPathResultandPathstoBaseLinkModelto always have access to the actual pathsControlsfeature (beta):- They are things that can show up on top of nodes/links and can even be clicked to be executed
- Their UI is also picked up from the registered components
Controldesignates a control that has a position and will be rendered if visibleExecutableControldesignates a control that has a position and will be executed when pressed (PointerDown event)- Default controls for now are:
BoundaryControlshows the model's boundaryRemoveControlshows a button that when clicked, removes the model from the diagramDragNewLinkshows a button that when clicked, starts a new link dragging from that node
GridWidgeta background grid that moves with the diagram instead of being fixed like in the Snap to grid example- More unit tests
Changed
- Core package changes:
- Web dependency was removed from the Core package
Diagramis now abstract- These changes were done to decouple the core from the rendering, in the future we might have a MAUI renderer
- Web dependency was removed from the Core package
Diagram.GetComponentForModelnow accepts acheckSubclassesargument (defaulttrue)- Constraints now must return a
ValueTask<bool>instead of a simplebool - Renamed
AllLinkstoPortLinksfor more clarity on which links, sinceLinkscontains the others - Dragging links from ports will now follow the mouse at the same pace minus 5 pixels so that it doesn't go on top of the link it self or other ports
- How groups are rendered
GroupRendererwill take care of rendering the group with the appropriate style and classes- Only
GroupNodesis required,GroupLinkswas deleted because all links are shown in the svg layer (with appropriate order)
Diagram.AddGroupwill now return the added group- All
Mouseevents have been converted toPointerevents PathGeneratornow returnSvgPathinstead of just stringsNavigatorWidgetwas rewritten to be faster, lighter, WORKING and customizable- It now can also take the shape of the nodes into account (rect and ellipse for now)
Fixed
- Virtualization throwing a JSException (#155)
- Ports not rendering correctly because of the missing
@key(#220) - Link not refreshing when a new vertex is created, which was showing out of link
Removed
DefaultNodeComponentandDefaultLinkComponentoptions (seeGetComponentForModelchanges)RenderLayerfrom the Core package and all its usageDeleteSelectionBehaviorsince there is a new keyboard shortcuts systemGroupingBehaviorsince there is a new keyboard shortcuts systemBaseLinkModelExtensionssince it was Obselete- Unnecessary port refreshes when dragging a link ends or when link snapping
ShapeDefinerdelegate and constructor arguments on nodes since delegates can't be serializedTouchXevents
2.1.6
2.1.4
Added
MouseDoubleClick(500ms interval) event inDiagram.GetScreenPointinDiagramin order to get the screen points from a diagram point (e.g. node position).Titleproperty inNodeModel, used by the default node widget.
Fixed
ZoomToFitnot triggeringZoomChangedevent.SourceNodeandTargetNodenot being set inBaseLinkModelwhen the ports change.
2.1.3
Added
- Multiple demo projects by TrevorDArcyEvans showing:
- Minimal project setup
- Custom nodes & links
- GraphShape layout algorithms
Fixed
2.1.2
2.1.1
2.1.0
Added
ScaleFactorzoom option (@joezearing)- Add
Constraintsoptions which gives you more control on what happens in the diagram:ShouldDeleteNode: Whether a selected node should be deleted or notShouldDeleteLink: Whether a selected link should be deleted or notShouldDeleteGroup: Whether a selected group should be deleted or not
DeleteSelectionBehaviorunit tests
Changes
- Batched more things
2.0.0
Added
GroupUngroupedevent (not the greatest name 😄)- Touch events
TouchStart,TouchMoveandTouchEnd - Mobile support
- Dragging new links from ports
- Selecting models
- Panning
- Dragging movables
RemoveGroupmethod to delete a group and all its children- Pressing DEL on a selected group will now remove it
- Ability for links to be segmentable (by setting
Segmentabletotrue)- Clicking a segmentable link will add a new vertex in that position
- Vertices are movable models, which mean you can drag them to reposition them
- Double clicking a vertex will delete it
- Link routers
- Routers are functions that take into account a link's vertices, and decide whether to add more points along the path
- They are specified using
Options.Links.DefaultRouteror by settingRouterin links - There are currently two routers,
Routers.NormalandRouters.Orthogonal - You can provide your own router by simply respecting the delegate
Router
- Link path generators
- Path generators are functions that takes as input a link's route, and return a list of generated SVG paths (strings), as well as the position and angle of the source/target markers
- They are specified using
Options.Links.DefaultPathGeneratoror by settingPathGeneratorin links - There are currently two generators,
PathGenerators.StraightandPathGenerators.Smooth - You can provide your own generator by simply respecting the delegate
PathGenerator
- On-the-fly link markers
- A link can either have a
SourceMarkerorTargetMarker - Link markers are SVG Paths with a known width (to calculate angle and where to cut the links)
- Static markers are available (e.g.
LinkMarker.Arrow) as well as utility methods to create known shapes
- A link can either have a
MouseClickevent, which only fires if the model (or canvas) in question didn't move, as opposed to MouseUpdata-X-idHTML attributes to nodes, ports and links- Abstract
BaseLinkModel,LinkModelnow inherits from it- All the parts of the library now refer to
BaseLinkModelinstead ofLinkModel(e.g. PortModel.Links)
- All the parts of the library now refer to
Color,SelectedColorandWidthproperties toLinkModel- Link labels
- Can have custom models, using
RegisterModelComponent - Due to the limitation of SVGs in Blazor, labels aren't interactive and must be created using
MarkupString - They can have a specified distance
- A number between 0 and 1: Position relative to the link's length
- A positive number, greater than 1: Position away from the start
- A negative number, less than 0: Position away from the end
- They can have an offset (Point)
- Can have custom models, using
- Link snapping
- While the user is dragging a link, it will try to find the closest port it can attach the link to
- Options (in
DiagramOptions.Links):EnableSnappingandSnappingRadius
GetBoundsextension method onIEnumerable<NodeModel>- Expose
Paddingproperty inGroupModel Factoryoption toOptions.Links- This is a delegate (
BaseLinkModel LinkFactory(DiagramManager diagram, PortModel sourcePort)) to let you control how links are created
- This is a delegate (
Groups(of typeDiagramGroupOptions) option toDiagramOptionsEnabledoption controls whether users are allow to group nodes together or notKeyboardShortcut(Func<KeyboardEventArgs, bool>) controls what keys need to be pressed to trigger the behaviorFactorylets you control how groups are created
GetRelativePointmethod toDiagram- This method gives the relative mouse point on the canvas
SelectionBoxWidget- If used, holding SHIFT and clicking then dragging will show a selection box that selects all models intersecting with it
- Minified versions of all assets
- Observe document body mutations to update canvas container
- Ability to add/remove children after the group is created
Diagramnow also inheritsModel- Ability to suspend refreshes in
Diagramby settingDiagram.SuspendRefreshtotrue- As the name suggests, this will stop the method
Refreshfrom triggering the eventChanged, which tries to re-render the UI
- As the name suggests, this will stop the method
Batch(Action action)inDiagram.- This is just a helper method that suspends refreshes, runs the action and then refreshes
- This is now used internally in node/link layers to only trigger 1 UI re-render
- Add
FillColorparameter toNavigatorWidget - Ability to create links between two nodes directly, without needing ports
- This depends on the shape of the nodes, which can be defined by providing a
ShapeDefinerinNodeModel's constructor - The default shape definer is
Shapes.Rectangle - Currently, there is only the Rectangle and Ellipse (including Circle) shapes, others will be added later
- This also works for groups, since groups are nodes
- This depends on the shape of the nodes, which can be defined by providing a
- Unit tests
Changed
- Renamed
DiagramManagertoDiagram - Remove need to specify
Namein diagram'sCascadingValue - Separate Nodes/Links from DiagramManager, they are now layers (
Diagram.NodesandDiagram.Links) -
- Adding/Removing nodes or links is now done inside these layers (e.g.
Diagram.Nodes.Add) - Added/Removed events are now inside these layers, not in the diagram (e.g.
Diagram.Links.Added)
- Adding/Removing nodes or links is now done inside these layers (e.g.
LinkAttachedevent removed (TargetPortChangedis the alternative)- It is now mandatory to add nodes to diagram before creating groups
SelectionChangedevent only contains the model now, useSelectedproperty- Removed
SelectedModelsin favor ofGetSelectedModels(), this is because we don't hold a list of selected models anymore (unnecessary) - Renamed
DiagramSubManagertoBehavior, it makes more sense RegisterBehaviornow takes as an argument the behavior instance to add. No need to useActivator.CreateInstancefor something like this, as it just slows things down- Removed
LinkTypeenum - Removed
DefaultLinkTypelink option - Removed
DefaultLinkModellink option - Removed
GetNodesRectmethod from DiagramManager (useGetBounds) - Removed diagram dependency from
GroupModel(was only usingGetNodesRect) - Renamed
GetRelativePointtoGetRelativeMousePoint- This method gives the relative mouse point inside the diagram, taking into account the current pan & zoom
Widgetsare inside theDiagramCanvasnow- This change is necessary so that widgets with absolute position have their relative parent be the canvas
- Renamed
Navigatorwidget toNavigatorWidget - Allow empty groups
- Compare received JS sizes (width and height) with precision of 0.0001
- In most cases, sizes retrieved from JS (especially with a zoom <> 1) can't be compared accurately (e.g.
80and79.9999975). We fix this by comparing with a tolerance.
- In most cases, sizes retrieved from JS (especially with a zoom <> 1) can't be compared accurately (e.g.
- Update ports dimensions only if Initialized is false
- This avoids useless re-renders/JS calls when node is re-visible
NodeModel.Portsis now aIReadOnlyList<PortModel>BaseLinkModelExtensionsis now obsolete- Moved everything in
Blazor.Diagrams.Core.Models.CoretoBlazor.Diagrams.Core.Geometry- This includes
Point,SizeandRectangle - This is to better structure things in the project, the new
Geometrynamespace will contain many other things related to it
- This includes
- Only render links when ports/nodes are initialized (position and/or size received)
- This will avoid the weird flicker where links show at (0, 0) then move to the correct position
Fixed
- Remove links when groups are removed
- Issue where links are clickable outside the visible stroke
pointer-eventsis now set tovisiblePaintedinstead ofall
MouseUpevent bubbles up fromPortModeltoNodeModelSizenot taking into account zoom when nodes become visible again- Only allow link creation using left mouse button
- JS errors in razor pages without a diagram
- CustomNodeWidget was movable from text input
- All users who create custom nodes with HTML inputs should use
x:stopPropagationonmousedown,mousemoveandmouseupto prevent the node from being movable through inputs.
- All users who create custom nodes with HTML inputs should use
- Deleted nodes from groups would still show them
NavigatorWidgetnot handling negative node positions- Panning with right click. It is now disallowed
- PortRender not taking into account its parent's
RenderLayer- Ports on SVG nodes will now render as
<g>elements
- Ports on SVG nodes will now render as
- Useless refreshes when diagram
Containervalues didn't change