Feature request: Friendly Error System for Processing

Relevant sub-area for this feature?

Other (specify if possible)

Feature details

Feature description

During Google Summer of Code 2023, a Friendly Error Messages system for Processing (inspired by the p5.js Friendly Error System) was developed by Will Rabalais (@WillRabalais04) with mentorship by Sam Pottinger (@sampottinger). This work adds clearer, contextual error messages, documentation links, and debugger improvements.

However, this work was never included in Processing and is not available to users today.

This request is to review, update if needed, and include this work in a future Processing release.

Note: This is meant to document work completed during GSoC 2023 and to put a pin in it for future consideration. It does not signal urgency, assign responsibility, or presume the level of effort required. The goal is mainly to ensure this work is visible and not lost.

Benefits

• Improves error messages that are currently cryptic and hard to understand
• Helps beginners debug and learn more effectively
• Brings Processing closer to p5.js in terms of learning-centered tooling

Challenges

• Updating the 2023 code to match the current Processing codebase and UI system (Compose)
• Expanding test coverage and checking language server compatibility

Additional context

• Original PR (legacy Processing4 repo)
• GSoC 2023 Wrap-up post
• Will's Project report
• p5.js FES Contributor Docs
• Friendly Errors i18n Book

Screenshots

Would you like to help implement this feature?

No, I’m just suggesting the feature

Beginne mit der Durchsicht des ursprünglichen PR 771 und des GSoC 2023-Projektberichts, um die bestehende Implementierung von Friendly Error Messages zu verstehen. Vergleiche sie anschließend mit der aktuellen Processing-Codebasis und Compose UI, einschließlich ihrer Anforderungen an Tests und language-server. Als abgeschlossen gilt die Aufgabe, wenn ein aktualisiertes und geprüftes System in eine zukünftige Processing-Version integriert ist, mit erweiterter Abdeckung und kompatiblem Debugger-Verhalten.