W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2007

[whatwg] Why Canvas?

From: Křištof Želechovski <giecrilj@stegny.2a.pl>
Date: Wed, 1 Aug 2007 07:00:52 +0200
Message-ID: <000a01c7d3f8$fd486a00$4d01010a@IBM42F76C011DF>
I think it can already be done using DHTML overlays.  Thus no instant
amazing breakthrough is to be expected.
Chris

-----Original Message-----
From: whatwg-bounces@lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of WeBMartians
Sent: Wednesday, August 01, 2007 1:34 AM
To: whatwg at whatwg.org
Subject: [whatwg] Why Canvas?

With <canvas> a relatively stable (and implemented, actually) tag, this may
be a doubtful question. However, I can't think of any answer, so here
goes...

Why <canvas>?

Why not allow the graphics primitives to operate on any element (not just
<canvas>) that has a height and width that may be expressed in picture
elements... ...even window.screen with its .availHeight, .availWidth,
.height, and .width (yeah, I know, the Screen object is actually a
JavaScript object, not an HTML DOM object)?

The utility is amazing: a tutorial option could then lead a user through a
page or series of pages, circling/outlining an input item ("Fill in this,
first!"), then circling a set of, say, radio buttons ("Now, select one of
these!"), and, finally, circling the Submit button ("Congratulations! You
did it!"). You can see how this would give an instant advantage in
Total-Ownership-Cost to Web Applications.

===
B. de Graaf - WeBMartians at Verizon.net 
Received on Tuesday, 31 July 2007 22:00:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:36 UTC