Support more built-in functions

[gaocegege]

Now Processing.R supports draw, setting and some other functions but not enough.

ref https://processing.org/reference/

2D Primitives

• arc()
• ellipse()
• line()
• point()
• quad()
• rect()
• triangle()

Curves

• bezier()
• bezierDetail()
• bezierPoint()
• bezierTangent()
• curve()
• curveDetail()
• curvePoint()
• curveTangent()
• curveTightness()

Environments

• delay()
• displayDensity()
• focused
• frameCount
• frameRate()
• frameRate
• fullScreen()
• height
• noSmooth()
• pixelDensity()
• pixelHeight
• pixelWidth
• settings()
• size()
• smooth()
• width

3D Primitives

• box()
• sphere()
• sphereDetail()

Color

Setting

• background()
• clear()
• colorMode()
• fill()
• noFill()
• noStroke()
• stroke()

Creating & Reading

Blocked until #9

• alpha()
• blue()
• brightness()
• color()
• green()
• hue()
• lerpColor()
• red()
• saturation()

[PatrickMurphy]

Gaocegege, I am interested in contributing to this repo, If you have any direction of what issues, or what built in functions you would like to prioritize I would be happy to claim some of the work and send pull requests.

[gaocegege]

@PatrickMurphy Thanks for your interest 🎉

Today, I'll write some documentation about the architecture of Processing.R and tag some issues to "for new contributors". If you have any problems when you read the code, feel free to @ me in GitHub or https://gitter.im/gaocegege/Processing.R.

[gaocegege]

re @PatrickMurphy

ref #16 (comment) Processing.R will focus on 2D & 3D Primitives at the first.

Functions such as arc() and ellipse() are easy to implement. If you want to contribute, this is a good entrypoint :)

[jeremydouglass]

@gaocegege -- this built-in functions list includes cursor().

Is it part of the plan support mouse input and interaction like mouseX mouseY mousePressed() mouseReleased() -- or will the first phase stay focused on non-interactive sketches? Without mouse interaction there isn't much point in a cursor() command.

[jeremydouglass]

Also, should box() be crossed off the list? It looked like it was implemented for the 3d-cube.R example.

[gaocegege]

@jeremydouglass

box in Processing has two definitions: box(size) and box(w, h, d), I only implement one for the 3D example. I treat the example as a feasibility research, so I will add all 3d functions soon.

[gaocegege]

Hi, there are too many built-in functions in Processing, so I am not sure if I have the ability to implement all functions on my own in the first evaluation. I am trying to attract some contributors to Processing.R. We could also talk about the priority between the functions and have a more detailed plan.

[jeremydouglass]

@gaocegege --

You definitely should not try to implement all the built-ins on your own! Your plan to call for contributors is a good one.

I would suggest either removing cursor() from the list entirely or else putting it in its own section alongside with the other mouse related functions. Mouse interaction would probably be an advanced issue for a contributor, so if you decide to add a mouse section perhaps put it far down the list.

Strange, I thought you had implemented both versions of box:

https://github.com/gaocegege/Processing.R/blob/abec5d7a832ad05260eb7256c6a2ab514e3283b7/src/rprocessing/applet/BuiltinApplet.java#L213

[gaocegege]

Oh, I forgot that. 🤔 Thanks for your review.

[gaocegege]

Yeah, I will remove cursor from the list.

[gaocegege]

Now renjin supports float correctly, so no need to do this work manually.

[jeremydouglass]

Fastastic! Great ask, hooray for the Renjin core developers, and hooray for open source.

...and that should simplify hundreds of super calls.

[gaocegege]

See bedatadriven/renjin#319

Now I think we could close the issue 🎉

[jeremydouglass]

So at this point every method from the API is automatically inherited? And the only remaining issue is with variables -- width, height, frameCount, frameRate, looping, focused, etc?

[gaocegege]

Yes, I think so 🤔

[jeremydouglass]

Since this is closed, is there a separate, open issue for variables -- width, height, frameCount, frameRate, looping, focused etc.? They are currently listed on this closed issue, but not resolved.

Perhaps edit the issue and remove them from the list, and add them to a separate issue for "Built-in variables" (vs. built-in functions).

[jeremydouglass]

Similarly, "Creating & Reading" is listed in the issue as "Blocked until #9" -- if this is still true then create another separate issue for Creating and Reading built-ins and delete them from this closed issue built-ins list.

[gaocegege]

Thanks, I forget it.

ref #81 and #86

[jeremydouglass]

Let's clean up this old list. Can all the "blocked until 9" boxes be checked off now that #86 is closed?

[gaocegege]

All the functions in the list are supported.