You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone! I am happy to tell you that I will be contributing to FES for this year's GSoC. I am mentored by @lm-n and @ghalestrilo. I am really excited to work on this project and be a part of this great community.
This enhancement is part of the first phase of my project.
FES's fesErrorMonitor catches errors which the browser shows. I will add more errors to the current list of errors, add the friendly error messages and unit tests.
Most appropriate sub-area of p5.js?
Accessibility (Web Accessibility)
Build tools and processes
Color
Core/Environment/Rendering
Data
DOM
Events
Friendly error system
Image
IO (Input/Output)
Localization
Math
Unit Testing
Typography
Utilities
WebGL
Other (specify if possible)
Feature enhancement details:
I will be adding the below-mentioned errors:
(Images taken from my GSoC proposal)
The text was updated successfully, but these errors were encountered:
How would this new feature help increase access to p5.js?
Hello everyone! I am happy to tell you that I will be contributing to FES for this year's GSoC. I am mentored by @lm-n and @ghalestrilo. I am really excited to work on this project and be a part of this great community.
This enhancement is part of the first phase of my project.
FES's
fesErrorMonitor
catches errors which the browser shows. I will add more errors to the current list of errors, add the friendly error messages and unit tests.Most appropriate sub-area of p5.js?
Feature enhancement details:
I will be adding the below-mentioned errors:
(Images taken from my GSoC proposal)
The text was updated successfully, but these errors were encountered: