PyBreeze Modular Architecture

System Design · flowchart diagram · MIT

This diagram illustrates the modular architecture of PyBreeze, an IDE built with PySide6, showcasing its core JEditor, various automation menus, subprocess

Source: https://github.com/Integration-Automation/PyBreeze/blob/65aa9f9fee91003b82d355b7f15b599e1d4cb6a5/README/README_zh-CN.md
Curated by Integration-Automation
PyBreeze IDE PySide6 Architecture Flowchart Automation System Design

Mermaid source

flowchart TB
    UI["PyBreeze UI · PySide6"]

    subgraph Editor["JEditor 基础编辑器"]
        direction LR
        E1["代码编辑器 + 标签页"]
        E2["文件树"]
        E3["语法高亮"]
        E4["插件系统"]
    end

    subgraph Automation["自动化菜单"]
        direction LR
        A1["APITestka"]
        A2["AutoControl"]
        A3["WebRunner"]
        A4["LoadDensity"]
        A5["FileAutomation"]
        A6["MailThunder"]
        A7["TestPioneer"]
    end

    subgraph Executors["子进程执行器 · TaskProcessManager"]
        direction LR
        X1["je_api_testka"]
        X2["je_auto_control"]
        X3["je_web_runner"]
        X4["je_load_density"]
        X5["automation-file"]
        X6["je-mail-thunder"]
        X7["test_pioneer"]
    end

    subgraph Tools["工具"]
        direction LR
        T1["SSH · paramiko"]
        T2["AI 代码审查"]
        T3["CoT 提示词编辑器"]
        T4["Skill 提示词编辑器"]
        T5["Skill Send GUI"]
        T6["架构图编辑器"]
        T7["JupyterLab"]
    end

    subgraph Install["安装菜单"]
        direction LR
        I1["模块安装器"]
        I2["构建工具"]
    end

    UI --> Editor
    UI --> Automation
    UI --> Tools
    UI --> Install

    A1 --> X1
    A2 --> X2
    A3 --> X3
    A4 --> X4
    A5 --> X5
    A6 --> X6
    A7 --> X7

What this diagram shows

This flowchart details the modular architecture of PyBreeze, an IDE built using PySide6. It highlights the main UI, the JEditor (core editor with code editing, file tree, syntax highlighting, and plugin system), various automation menus (APITestka, AutoControl, WebRunner, LoadDensity, FileAutomation, MailThunder, TestPioneer), and their corresponding subprocess executors (e.g., je_api_testka). Additionally, it shows integrated tools like SSH (paramiko), AI code review, prompt editors, and JupyterLab, along with an installation menu for modules and build tools.

When to use it

Use this diagram when designing or understanding the architecture of a modular Integrated Development Environment (IDE), an application with a plugin system, or a system that orchestrates multiple subprocesses for automation and tooling. It's also useful for visualizing how a GUI application integrates various backend services and external tools.

How to adapt it for your project

This architecture can be adapted by swapping out the UI framework (e.g., from PySide6 to another GUI library), adding new automation modules and their corresponding executors, integrating different sets of development tools, or modifying the plugin system to support various extension types. The subprocess execution model can be extended to support containerized environments or remote execution.

Key concepts