PApplet's PGraphics instance

Core Library Questions

jedierikb

in Core Library Questions • 9 months ago

PApplet's PGraphics instance, g, is not documented in the API.

Is there a reason it is not listed in the API? Is there a better way to access PApplet's PGraphics?

Because it is not documented, it is not being supported in processing.js. This leads to complications in developing code to run on both platforms.

Replies(3)

PhiLho

Re: PApplet's PGraphics instance

9 months ago

It is not documented in the reference, but being a public variable, it is documented in the JavaDoc...

jedierikb

Re: PApplet's PGraphics instance

9 months ago

Unless it is added to the API, it looks like it is not going to be added to processing.js.

Pomax said on Jan 13, 2013:

→ State changed from “new” to “wont-fix”

"g" is not part of the Processing API, it's the underlying Java graphics class, and should under no circumstances be accessed in a Processing sketch. Doing so "voids your warrant", since you've escaped to plain Java, and all bets are off. Processing.js will not support the full Java API or its class and method hierarchies, only Processing's API.

https://processing-js.lighthouseapp.com/projects/41284/tickets/1916-g-variable-feature-of-processingorg-not-available-in-processingjs#ticket-1916-4

I can appreciate his hesitation to include it for the reasons given, but if 'g' is here to stay (and I believe it has been around for a long time), how can we petition to make it part of the API or get 'blessed' in some other way?

GoToLoop

Re: PApplet's PGraphics instance

9 months ago

There are 2 forked philosophies here.

Make a pure Processing API. Everything else must be cut off, even though that would be easy cheesy to implement. Like System.out.println() acceptable as println() is a big no-no. :D
Try to convert everything which is relatively feasible to Processing API. Be it Java, Pyhton, Ruby, etc. Make Processing API running on that environment as complete, comfortable and flexible as possible.

Top Reply