Repository navigation
Replies: 2 comments
|
This proposal is solid and well-scoped. Answers to your questions: 1. Layout preference — offer both as a toggle. The force-directed layout is useful during exploration (edge following, cluster emergence), but the ring layout is better once you know which memory you want to center on. A toggle button above the graph is the right UX. 2. Re-center on click — yes, this is the most valuable single feature. Being able to shift perspective to any node without a page reload or API round-trip makes the graph genuinely usable for navigation rather than just display. 3. Priority order — I agree with your table: concentric ring layout + re-center (P1), degree slider (P2), edge arc/curve classification (P2). The sidebar (P3) can come later. This would make a great community contribution. The scope is well-defined (~600 LOC in |
|
Tracking issue on Codeberg: https://codeberg.org/doobidoo/mcp-memory-service/issues/264 Development moved to Codeberg in June 2026 while this account was suspended, and Codeberg has no Discussions feature — so the accepted proposal moves across as an issue and this thread stays here as the design record. The new issue carries the decisions from my comment above rather than restating the proposal: both layouts as a toggle, re-center on click as the highest-value single feature, and the P1/P2/P3 order from your table. It also notes the one thing not in the original scope discussion — the dashboard JS has no automated test coverage, so a layout change needs browser verification and screenshots on the PR. Still a good community contribution, and the offer stands: open a draft PR early rather than after the implementation is finished. |
Uh oh!
There was an error while loading. Please reload this page.
Proposal: Add Concentric Ring Layout to Interactive Graph Visualization
After evaluating the knwler knowledge graph tool (MIT licensed), I'd like to propose adopting some of its visualization concepts for our Interactive Graph Visualization dashboard.
Current State
Our graph visualization uses D3.js v7.9 with a force-directed layout. It supports zoom, pan, drag, hover tooltips, and node/edge coloring by memory type and relationship type.
What knwler does differently
knwler uses a concentric ring layout (BFS-based) with vanilla JS + SVG:
See their Human Rights example for a live demo.
Proposed Features (prioritized)
What we would NOT take
Questions for the community
References
src/mcp_memory_service/web/static/app.jsGET /api/analytics/graph-visualizationAll reactions