About a week ago I had a similar inkling that we'd want a way of accessing as much of the canvas API as possible. Here's what I came up with:
https://gist.github.com/mgold/a7c3c393b90376b780f4948a78649c90 The horrible thing about this proposal is that it uses eval. This means it's hard for the JS runtime to optimize, and presents all kinds of security holes. Worse, if you ere to forgo sensible canvas rendering, you could use this to run arbitrary JS code from Elm strings you pass in. (You'd have to run the task, but still.) Without a lot of validation or type restrictions, it would be hard to prevent this, even if you could avoid calling eval. You'd still need to pass in client-generated strings to the canvas API functions. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
