Original Summary

Hi everyone! I've been developing OrthoDiagrams, a native desktop application for designing and organizing entity-relationship diagrams. I wanted a tool that keeps database models separate from their visual representations, with clean diagrams, portable project files, and no mandatory cloud services. The current Alpha (v0.1.352) includes: Multiple models and diagrams within a single project. A Model Explorer for tables, views, relationships, and other model objects. Visual ER modeling with crow's foot relationships and automatic layout. Column editing, constraints, indexes, and model mappings. Modeling support for PostgreSQL, Oracle, MySQL, SQL Server, SQLite, DuckDB, and other dialects. Import from PostgreSQL, Oracle, CSV, Mermaid, and draw.io. Export to PDF, SVG, Mermaid, and draw.io. Local JSON project files and light/dark themes. It's built with C++ and Qt, and the Alpha is available for Windows, Linux, and macOS. The software is still experimental, and some features are unfinished. I'm currently looking for feedback from developers who work with database schemas and ER diagrams. I'd particularly like to know: Does the model-first approach make sense for your workflow? Which import/export formats matter most to you? What would make you consider using a desktop modeling tool? Website and Alpha download: https://orthodiagrams.com/ I'd appreciate any feedback, especially on usability and the overall modeling experience.   submitted by   /u/H4z4rd_Z [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/19 11:11:03