1

Here are its docs: https://processing.org/reference. Processing is described as a 'language built with the purpose of teaching non-programmers the fundamentals of computer programming in a visual context'.

However, how does this language relate to the real-world computer graphics tools?

For example:

  • Is it similar to some low-level library maybe?
  • Is the concept of a repeating draw() { background(255) } (in order to draw each new frame of an animation) used in real-world libraries?
  • Are the same methods/concepts used (pushMatrix, popMatrix, rotate, translate)?

1 Answers1

1

It does not relate to low level libraries. Yes, usually each frame is drawn separately, nothing can change if i dont change anything. However the draw loop is often handled by somebody else in for example game engines, etc. So in fact processing is often lower level stuff than what many people would do day to day.

Pushing matrix state is pretty common, it exists even in graphics languages from 1970's.

joojaa
  • 8,437
  • 1
  • 24
  • 47
  • It does not relate to low level libraries., > So in fact processing is often lower level stuff than what many people would do day to day. --- So does it relate to low-level libraries or not?

    – Evgenia Karunus Mar 24 '18 at 00:21
  • @lakesare No it does not. Lower, does not mean low. In fact low level graphics libraries are rare, mainly because modern systems really dont want you poking in the fabric of the OS. So even something as fundamental as OpenGL is a high level library youd need to go into something like Vulkan to go low enough to be considered low level. But without this kind if high level abstraction it would be impossible to be compatible across devices. – joojaa Mar 24 '18 at 08:50