[Roadmap] Plan JEditor next-generation editor platform

[JE-Chen]

Summary

This draft PR establishes the implementation roadmap for the next generation of JEditor.

It covers:

• UI redesign
• customizable shortcuts
• complete translation dictionaries
• Anthropic AI backend
• severity-aware LSP diagnostics in Problems
• DAP debugger
• workspace / multi-root projects
• remote development moved into JEditor core
• Tree-sitter syntax parsing/highlighting
• an embeddable editor component
• Qt/JEditor editor-development tutorials

The roadmap is intentionally dependency-driven. It proposes a small core/service boundary first, then
moves workspace, language services, debugging and remote execution behind reusable interfaces before
splitting out the embeddable component.

Current-state notes

JEditor already has important foundations: configurable shortcuts, multiple translations, LSP
sessions/diagnostics, a pdb-oriented debugger, LangChain/OpenAI chat, EditorMain(extend=True),
EditorWidget/library APIs, plugin registration and Sphinx documentation.

This means the work should be evolutionary rather than a wholesale rewrite.

Planned milestones

• M0 — Foundation and compatibility boundary
• M1 — UI redesign + commands/shortcuts + i18n completion
• M2 — Tree-sitter + unified diagnostics/severity model
• M3 — Workspace + multi-root
• M4 — DAP debugger
• M5 — AI provider abstraction + Anthropic
• M6 — Remote development in JEditor core
• M7 — Embeddable editor component
• M8 — Tutorial and architecture documentation

Review questions

Before implementation starts, please review:

1. Is dev the correct integration branch for these milestones?
2. Is the M0 service boundary small enough, or should any service be deferred?
3. Should SSH be the first remote transport, or should another transport be prioritized?
4. Is the proposed standalone/embedded/IDE layering compatible with downstream users such as PyBreeze?
5. Which milestones should be split into separate tracking issues?

No feature implementation is included in this PR yet; this is the planning/architecture PR.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}