Skip to content

issues Search Results · repo:processing/p5.js language:JavaScript

Filter by

0 results
 (86 ms)

0 results

inprocessing/p5.js (press backspace or delete to remove)

Most appropriate sub-area of p5.js? - [ ] Accessibility - [x] Color - [ ] Core/Environment/Rendering - [ ] Data - [ ] DOM - [ ] Events - [ ] Image - [ ] IO - [ ] Math - [ ] Typography ...
Area:Color
p5.js 2.0
  • epibyte
  • Opened 
    3 hours ago
  • #7998

z### Increasing access Currently there isn t a way in p5.strands to pass data between one hook in e.g. the vertex shader and another hook in the vertex shader. You can do it between vertex/fragment with ...
Enhancement
p5.strands
  • davepagurek
  • Opened 
    16 hours ago
  • #7995

Right now, many (but not all!) shader hooks involve taking in a struct, modifying it, then returning it, e.g.: getObjectInputs((inputs) = { inputs.position.x += 10; return inputs; }) We ...
p5.strands
  • davepagurek
  • Opened 
    17 hours ago
  • #7994

Right now, to create a shader with p5.strands, we have a lot of brackets, e.g. baseMaterialShader().modify(() = { ... }). It may not be obvious to users that baseMaterialShader() is a function (that s ...
p5.strands
  • davepagurek
  • Opened 
    17 hours ago
  • #7993

Increasing access While I think we ve made great progress in making shaders easier for newcomers to write, there are a few more things that I think are still relatively complex new constructs that are ...
Area:WebGL
Enhancement
p5.strands
  • davepagurek
  • Opened 
    17 hours ago
  • #7992

Most appropriate sub-area of p5.js? - [ ] Accessibility - [ ] Color - [ ] Core/Environment/Rendering - [ ] Data - [ ] DOM - [ ] Events - [ ] Image - [ ] IO - [ ] Math - [ ] Typography ...
Bug
  • shawdm
  • 2
  • Opened 
    21 hours ago
  • #7986

Most appropriate sub-area of p5.js? - [ ] Accessibility - [ ] Color - [ ] Core/Environment/Rendering - [ ] Data - [ ] DOM - [ ] Events - [ ] Image - [ ] IO - [ ] Math - [x] Typography ...
Area:Typography
Bug
  • Iancam
  • 3
  • Opened 
    yesterday
  • #7984

Most appropriate sub-area of p5.js? - [ ] Accessibility - [ ] Color - [ ] Core/Environment/Rendering - [ ] Data - [ ] DOM - [ ] Events - [ ] Image - [ ] IO - [ ] Math - [x] Typography ...
Area:Typography
p5.js 2.0
  • zekewattles
  • 5
  • Opened 
    7 days ago
  • #7979

Increasing access GitHub’s auto‑link / auto‑close keywords (Resolves #123, Fixes #123, etc.) only work when a PR targets the default branch (main). For PRs into dev-2.0, the keywords are ignored. Example: ...
DevOps
Feature Request
  • perminder-17
  • 2
  • Opened 
    10 days ago
  • #7975

Increasing access Reducing bandwidth requirements 4x for users opting into modern library usage. Most appropriate sub-area of p5.js? - [ ] Accessibility - [ ] Color - [ ] Core/Environment/Rendering ...
Feature Request
  • nickswalker
  • 1
  • Opened 
    10 days ago
  • #7974
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub