Go to town guys!  ColorMap is meant to be extended, and SimpleColorMap is just to provide the most common needs.

As to shape and size, yeah, that needs to be done carefully because shape and size affect not only how the object looks but also how it responds to hit-testing.  Still, MASON's default mechanism for specifying size and other features (like outline) is in desperate need of improvement.  Anyway, if you want to add a variable shape mechanism, such as stars or regular polygons with variable numbers of sides, I'd start by looking at ShapePortrayal2D and maybe subclassing it.


On Jun 11, 2014, at 6:51 PM, Mark Coletti <[log in to unmask]> wrote:
> On Wed, Jun 11, 2014 at 5:31 PM, Joey Harrison <[log in to unmask]> wrote:
>> I'm seeing the need for a smarter colormap class and wondering if any of you have beaten me to it. Here are some of the capabilities I imagine in such a class:
>> Set bounds based on data (doubles):
>> - Set the bounds to the min and max
>> - Set the bounds to n standard deviations above/below the mean
>> - Set a non-linear scaling based on the shape of the distribution of the data
>> For integer data:
>> - Use a hashmap (or similar) to map any values to colors (currently the values have to be 0, 1, 2, ...)
> For that matter, the time might be ripe for a "two factor" color/shape map a la R.  Or even "tri factor" color/shape/size.  Yes, can be done manually, but it'd be nice to have some sort of convenience class to make implementation easier.