nature-of-code / noc-book-2-archive

Repository for The Nature of Code book with p5.js

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

PVector ==> p5.Vector in text?

joeyklee opened this issue · comments

A question about terminology:

  • Do we explicitly use: p5.Vector() to create vectors or rather createVector()?
  • In the text do we replace PVector with p5.Vector?

createVector() should definitely be used! (There is no equivalent in Processing). I think I will probably go between saying explicitly p5.Vector and just "vector" when writing more generally about a vector object. I'll have to think about this a bit more.

Sounds good. In the beginning when you introduce vector operations, there's a kind of back and forth between brewing up your own vector class and showing how it works in p5. I did a first pass in nature-of-code/noc-book-2#28 and hopefully it make sense :)

Noting that in a lot of cases where I previously save "PVector" it makes more sense to refer to them as lower-case "vector" or "vectors." p5.Vector can be reserved for special cases specific to p5 implementation itself. Reflecting this in my pass over Chapter 1.

These are being fixed during the editing and re-writing process