@@ -78,21 +78,26 @@ _ setLocationRelativeTo(null) was removed, will it be missed?
7878_ deal with applySettings() change (maybe not a problem?)
7979
8080
81- python has to use launch() instead of open()
82- map() is bad for Python (and JavaScript?)
81+ cross-language awkwardness
82+ _ python has to use launch() instead of open()
83+ _ map() is bad for Python and JavaScript
8384
8485
85- under consideration
86- _ break PUtil out from PApplet
87- _ break more api with Processing 3?
88- _ use enums for everything (fixes auto-completion)
89- _ add chaining operations
90- _ min() and max() to use varargs
86+ breaking api
87+ _ bring back chaining in JSON (and add to XML)
88+ _ add chaining operations to PVector
89+ _ https://github.com/processing/processing/issues/257
9190_ move to enums instead of PConstants?
9291_ helps textMode() only accept valid entries
9392_ really nice for auto-complete
9493_ prevents hundreds of entries from coming up w/ auto-complete
9594_ downside: breaks compatibility big time
95+ _ min() and max() to use varargs
96+ _ https://github.com/processing/processing/issues/3027
97+
98+
99+ under consideration
100+ _ break PUtil out from PApplet
96101_ fix the registered methods doc, stop/dispose working
97102_ Casey needs to nudge people about libraries, so we need to fix this
98103_ pause(), resume(), start(), stop() clarifications
@@ -129,9 +134,6 @@ _ save the constructor for the version that actually copies data
129134_ the table pointer version will be speedy and allow chaining
130135
131136
132- later
133- _ bring back chaining in JSON (and add to XML)
134- _ maybe once we make the PVector change
135137_ bezierSegment() function to do equal-length segments
136138_ https://github.com/processing/processing/issues/2919
137139
0 commit comments