On Wed, Nov 24, 2010 at 2:23 PM, Tab Atkins Jr. <span dir="ltr"><<a href="mailto:jackalmage@gmail.com">jackalmage@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
For example, I've recently been playing with fractals in canvas, and<br>
temporarily set my blog to have a screen-filling canvas z-index'd<br>
below the content, filled with an interactive fractal (the mandelbrot<br>
set, overlaid with the julia set for the point your mouse was over).<br>
It would be better/cleaner/easier/more semantic to just draw directly<br>
into the <body> background, which is what I was faking with abspos and<br>
z-index.<br></blockquote><div><br>OK.<br><br></div><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">How about just using canvas() to refer to setImageElement() things?<br>
</blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
This retains the flexibility that setImageElement has over<br>
getCSSCanvasContext, while removing the weirdness of transparently<br>
overriding #ids and keeping element() open to accept arbitrary<br>
selectors?<br></blockquote><div><br>Special syntax to refer to setImageElement elements would be OK, but I wouldn't choose "canvas()", since the element can also be a <video> or <img>.<br><br>How about element(<ident>) to refer to setImageElements, element(#id) for DOM IDs, and element(first(<selector>)) for selectors? (I don't necessarily endorse the idea of extending to selectors, FWIW, but I appreciate the desire to keep the possibility open.)<br>
<br></div></div>Rob<br>-- <br>"Now the Bereans were of more noble character than the
Thessalonians, for they received the message with great eagerness and
examined the Scriptures every day to see if what Paul said was true." [Acts 17:11]<br>