- From: Charles Pritchard <chuck@jumis.com>
- Date: Sun, 03 Oct 2010 17:08:49 -0700
- To: Ian Hickson <ian@hixie.ch>
- CC: Richard Schwerdtfeger <schwer@us.ibm.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>
On 10/3/2010 4:55 PM, Ian Hickson wrote: > On Sun, 3 Oct 2010, Charles Pritchard wrote: >> On 10/3/2010 4:46 PM, Ian Hickson wrote: >>> On Sun, 3 Oct 2010, Charles Pritchard wrote: >>>> I'm going to come out for this. A virtual keyboard is essentially a >>>> text editor using nothing but radio buttons. >>> I meant something with radio buttons being used purely for their >>> graphical effect, as in: >>> >>> http://junkyard.damowmow.com/441 >> So, you were being sarcastic? > No more so than the people suggesting that writing a text editor in > <canvas> is a good idea. Many people have used <div contentEditable> with editors like f*ck and have expressed interest in alternatives. I've had people approach me asking about text editing in <canvas>, they were not being sarcastic. Mozilla is not playing a joke on the world with their Bespin related product. And I'm certainly not wasting money to be a funny-man, when I invest in text editing with canvas. As a technical underpinning, Canvas exposes the same system 2d API that many browsers use for their rendering. I write the same code they do, I use DOM APIs, valid HTML elements, CSS semantics; why the disrespect dude? -Charles
Received on Monday, 4 October 2010 00:35:48 UTC