From 343dcfc1f650cc4b4ff41466c6ce4fa9efb14483 Mon Sep 17 00:00:00 2001 From: ssw Date: Thu, 2 Jul 2026 20:37:28 +0800 Subject: [PATCH] =?UTF-8?q?docs(web-patches):=20=E8=A1=A5=E5=85=85=20jnpf?= =?UTF-8?q?=20=E8=87=AA=E7=A0=94=20autoLayout=20=E5=AE=9E=E7=8E=B0?= =?UTF-8?q?=E7=BB=86=E8=8A=82=20(=E5=AE=9E=E6=B5=8B=E9=A9=B1=E5=8A=A8,=202?= =?UTF-8?q?026-07-02)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 实测重新读 web 源码: jnpf 不用 bpmn.js 内置 autoLayout, 在 web/apps/jnpf-web-apps-main/src/components/FlowProcess/src/propPanel/components/FlowButton.vue:354-478 自研 Sugiyama 简化算法: - 闭环检测 - BPMNTreeBuilder 构建树 - BFS 遍历 + 多分支汇合节点 y 居中 (incoming > 1) - 碰撞算法 (按层避免重叠) - 自动分层 + 偏移 - sequenceFlow 自动走线 之前我下结论'分支点乱是 bpmn.js 算法不好'是错的: 1. jnpf 自研算法 (line 370-475) 已经处理多 gateway 多分支 2. 实际'乱'原因是用户 rebuild main dist 之前是旧版, rebuild 后就好了 修正点: - doc 加上 jnpf 自研算法完整说明 (用户实测后纠正了我) - 实际链路: web-patch 改 jnpf-bpmn → jnpf-bpmn dist 重 build → main dist 重 build → 浏览器加载 (3 步都要做) --- .../_jnpf-bpmn-autoLayout-on-open.md | 51 ++++++++++++++++++- 1 file changed, 49 insertions(+), 2 deletions(-) diff --git a/docs/web-patches/_jnpf-bpmn-autoLayout-on-open.md b/docs/web-patches/_jnpf-bpmn-autoLayout-on-open.md index b58592f..4e18d41 100644 --- a/docs/web-patches/_jnpf-bpmn-autoLayout-on-open.md +++ b/docs/web-patches/_jnpf-bpmn-autoLayout-on-open.md @@ -37,16 +37,63 @@ String deploymentId = flowAbleUrl.deployFlowAble(flowXml, templateJsonId); jnpf/bpmn 包编辑器打开时**不**自动调用 autoLayout: ```js -// jnpf/前端/jnpf-bpmn/src/components/bpmn/src/index.vue:148 +// jnpf/前端/jnpf-bpmn/src/components/bpmn/src/index.vue:148 (原文) if ((props.isPreview && props.isFreeType) || (props.flowXml && Object.keys(props.flowNodes)?.length === 0)) props.handleAutoLayoutByHorizontal(); ``` 触发条件: isPreview + isFreeType, 或 flowNodes 为空。**dacli workflow create 后 flowNodes 有值, 触发不命中。** +## jnpf 自研的 autoLayout 实现 (关键发现) + +`handleAutoLayoutByHorizontal` **不是 bpmn.js 内置算法**, 是 jnpf 在 `jnpf/前端/jnpf-web-apps-main/src/components/FlowProcess/src/propPanel/components/FlowButton.vue:354-478` **自研的 Sugiyama 简化算法**: + +```js +// FlowButton.vue:354-478 完整算法 +function handleAutoLayoutByHorizontal() { + // 1. 闭环检测 — 避免环状流程 + if (NodeUtils.getEndlessLoop(props.bpmn)?.length > 0) { ... return } + + // 2. 画布缩放 100% + props.bpmn.get('canvas').zoom(1) + + // 3. 设置 jnpfData layout=horizontal + props.bpmn?.get('jnpfData').setValue('layout', { value: 'horizontal' }) + + // 4. 构建树状数据结构 + const treeBuilder = new BPMNTreeBuilder(elementRegistry.getAll()) + const bpmnTree = treeBuilder.constructTree() + + // 5. BFS 遍历 + 多分支汇合节点 y 居中 (关键) + treeBuilder.bpmnTraverseTreeBFS(bpmnTree, (node) => { + if (incoming?.length > 1) { + let y = 0 + incoming.forEach(connect => { y += connect.source.y }) + y = y / incoming.length // 多源 y 居中 + node.offset = { x: node.offset.x, y } + } + }, 'horizontal') + + // 6. 碰撞算法 (按层避免重叠) + treeBuilder.handleCollisionsByLevel(list, 'horizontal') + + // 7. 格式化画布 + 自动分层 + treeBuilder.formatCanvasHorizontal(list, modeling, elementRegistry) + + // 8. 移动节点 + 更新连线 waypoint + list.forEach(item => modeling.moveShape(element, { x: deltaX, y: 0 })) + treeBuilder.updateConnectionWaypoints(item, modeling, 'horizontal') +} +``` + +**关键点**: jnpf 的 BPMNTreeBuilder **处理多 gateway + 多分支**: +- incoming.length > 1 → y 取平均 (避免分支乱) +- handleCollisionsByLevel → 按层避免重叠 +- updateConnectionWaypoints → sequenceFlow 自动走线绕过节点 + ## 修复 (web-patch) -修改 `jnpf/前端/jnpf-bpmn/src/components/bpmn/src/index.vue:148`: +修改 `jnpf/前端/jnpf-bpmn/src/components/bpmn/src/index.vue:210`: ```diff - if ((props.isPreview && props.isFreeType) || (props.flowXml && Object.keys(props.flowNodes)?.length === 0)) props.handleAutoLayoutByHorizontal();