rojohound
Minor issues:
1) Using floats, as for example created by random(), in the color fields of the gradient function produces a javascript error.
For example:
"rgb(" & random(255) & ", 128, 128)" outputs a "...line 493 (col undefined)" error
"rgb(" & round(random(255)) & ", 128, 128)" works as expected (and any other expression generating an integer)
2) The gradient style "horizontal" reads "hoizontal".
3) Using floats, as for example created by random(), in the color field of the fill function does not produce a javascript error, but isn't working either. The canvas will be filled with black instead of the specified color.
For example:
"rgb(" & random(255) & ", 128, 128)" fills with black
"rgb(" & round(random(255)) & ", 128, 128)" works as expected
4) Using floats, as for example created by random(), in any field of the floodfill function does not produce a javascript error nor fill with black, but isn't working either. Javascript doesn't answer anymore and one can only stop the script.
For example:
random(100) in the x or y field, "rgb(" & random(255) & ", 128, 128)" in the color field, all lead to the script having to be stopped
round(random(100)) in the x or y field, or "rgb(" & round(random(255)) & ", 128, 128)" work as expected.
There may be other functions as well with inconsistencies, but I only tested those three.
I propose that all functions behave the same. If it isn't possible to convert float to int within the plugin, then it would be best to just draw black. If you feel uncomfortable with just drawing then all three should output a javascript error.