Foblex Flow
Introduction
Overview
Nodes
Custom Nodes
Drag Handle
Node Selection
Resize Handle
Rotate Handle
Grouping
Drag to Group
Connectors
Node as Connector
Connector Inside Node
Connector Outlet
Limiting Connections
Connection Rules
Connectable Side
Updated
Connections
Drag to Connect
Drag to Reassign
Create Node on Connection Drop
Remove Connection on Drop
Assign Node to Connection on Drop
Auto Snap
Connection Types (Straight, Segment, Bezier, Adaptive Curve)
Custom Connection Type
Connection Behaviours
Connection Markers
Connection Content
New
Connection Waypoints
New
Custom Connections
Connection Connectable Side
New
Extensions
Add Node from Palette
Selection Area
Help in Positioning (Legacy)
Deprecated
Magnetic Lines
New
Magnetic Rects
New
Grid System
Minimap
Zoom
Updated
Background
Updated
Advanced
Large Scene Performance
Updated
Connection Redraw Performance
Updated
Cut/Copy/Paste
New
Undo/Redo
Undo/Redo V2
New
Dagre Layout (Directed Graph)
ELKJS Layout (Directed Graph)
Drag Start/End Events
Custom Event Triggers
Reference Apps
AI Low-Code Platform
New
DB Management
UML Diagram
Tournament Bracket
Foblex Flow

UML Architecture Diagram

Example

This page demonstrates how to build a custom diagram editor with @foblex/flow and Angular. The sample data is UML-styled, but the focus is the library integration patterns.

Library Building Blocks Used

  • f-flow as the interaction root.
  • f-canvas with fZoom for viewport and scale control.
  • fNode and fGroup for rendering movable graph elements.
  • fConnection with explicit routing sides, connection behavior, and line types.
  • Custom SVG markers via fMarker for relation semantics.
  • f-background and f-line-alignment for canvas readability.
  • Programmatic viewport controls: fit to screen and reset center.
  • Standalone Angular composition with local state for nodes, groups, and connections.

Why This Matters For The Library

@foblex/flow is domain-agnostic. This example shows how library primitives can be composed into a structured, production-style diagram surface with custom rendering and routing logic. You can replace UML data with any domain model and keep the same flow architecture.

Source Code

The full project source for this example is in:

Edit this page on GitHub