rectangle with 2 rounded corners

[pixelzoom]

From phetsims/sun#197 ...

Add support (to Shape?) for creating a Shape that is a rectangle with 2 of its adjacent corners rounded, and the other 2 corners squared.

[jonathanolson]

As a more general pattern, can we supply a cornerRadius for each corner, OR boolean flags for which corners are rounded, and which ones aren't?

I'd hate to have to handle "rectangle with 1 or 3 rounded corners" separately.

Thoughts?

[samreid]

What if someone asks for a partially rounded triangle?

[pixelzoom]

What if someone asks for a partially rounded triangle?

Then they have a blank slate to write their own, because there is no scenery.Triangle, and I don't see any triangle functions in kite.Shape.

[pixelzoom]

can we supply a cornerRadius for each corner,

Since the most common use case is to have the same radius for all rounded corners, this duplicates the problem that we have with scenery.Rectangle (phetsims/scenery#467).

OR boolean flags for which corners are rounded, and which ones aren't?

OK with me.

[jonathanolson]

Any preferences between reusing Shape.roundedRectangle or a new function, and also between optional arguments for corners:

function( x, y, width, height, arcw, arch, isUpperLeftSharp, isUpperRightSharp, isLowerRightSharp, isLowerLeftSharp )

or more of an options pattern:

function( x, y, width, height, { cornerRadius: ..., roundUpperLeft: false, ... } )

or any other combination?

[jonathanolson]

Marked for developer-meeting as an API question.

[pixelzoom]

9/24/15 dev meeting:

// function signature
Shape.roundedRectangleWithRadii = function( x, y, width, height, {
topLeftCornerRadius:
topRightCornerRadius: 
bottomLeftCornerRadius:
bottomRightCornerRadius: 
} ) { ... };

// use case
var cornerRadius = 20;
var rect = Shape.roundedRectangleWithRadii( 0, 0, 200, 100, {
topLeftCornerRadius: cornerRadius,
topRightCornerRadius: cornerRadius
} );

[jonathanolson]

Completed, assigning for review, and to consider not including "CornerRadius" in every corner option. Any opinion on:

// use case
var cornerRadius = 20;
var rect = Shape.roundedRectangleWithRadii( 0, 0, 200, 100, {
  topLeft: cornerRadius,
  topRight: cornerRadius
} );

[pixelzoom]

I guess the only reason to include "CornerRadius" in each option name would be if we think there will additional options. If we don't think there will be additional options, then I recommend renaming the options parameter to cornerRadii. Any other opinions?...

[pixelzoom]

Since Shape.roundedRectangleWithRadii is unlikely to be used for other types of rectangles, and is unlikely to have non-radii options, I think it's appropriate to change its signature to:

Shape.roundedRectangleWithRadii( x, y, width, height, cornerRadii )

where cornerRadii defaults to:

{
  topLeft: 0,
  topRight: 0,
  bottomLeft: 0,
  bottomRight: 0
}

[samreid]

The suggestion in #56 (comment) seems good to me.

[jbphet]

+1 for #56 (comment).

[jonathanolson]

Changed, assigning @pixelzoom for review.

[pixelzoom]

👍 Closing.

[jbphet]

Reopening - I believe the convention in other PhET libraries is to specify 2D options with the x value first and the y value second, e.g. leftTop instead of topLeft (see Node.js in Scenery). Shouldn't we follow the same convention here?

[pixelzoom]

OK with me. Back to @jonathanolson.

[samreid]

Yes, same convention please.