Comments on: Bespin and Canvas: Part 1

By: Pictures on canvas

Pictures on canvas — Thu, 28 Jul 2011 05:23:29 +0000

Hi, this blog is really instructive. I would like to know more about this. Pictures on canvas

By: Jonathan Lin

Jonathan Lin — Tue, 19 Jan 2010 19:58:11 +0000

I was wondering if we could get bespin and the palm ares toolkit working on the palm pre browser. It would definitely be cool.

bespin.mozilla.org loads up on the pre browser, but I can’t log in as the log in bar is in a div that is not rendered on the pre browser.

I’m going to try a self hosted version of bespin next.

The next step is to make a pre app – just embed bespin as a general purpose code/text editor for the palm pre!

By: Bespin, the cloud, and Canvas | Broken Links

Bespin, the cloud, and Canvas | Broken Links — Mon, 05 Oct 2009 12:25:59 +0000

[...] created using JavaScript (only 62kb compressed, apparently) and the HTML5 canvas element (update: more on that implementation). Seeing other examples of what its capable of, I really need to start learning more about [...]

By: OnlineEditor (Syntax-Highlighting) - AJAX (Asynchronous JavaScripting and XML) Forum

Wed, 26 Aug 2009 09:18:28 +0000

[...] [...]

By: Knowtu » links for 2009-08-16

Knowtu » links for 2009-08-16 — Mon, 17 Aug 2009 01:05:00 +0000

[...] Bespin and Canvas: Part 1 « Ben Galbraith’s Blog (tags: canvas javascript) [...]

By: HTML 5 VS AJAX : l’amputation sera nécessaire | E-vidence

HTML 5 VS AJAX : l’amputation sera nécessaire | E-vidence — Sun, 22 Mar 2009 18:55:36 +0000

[...] une balise HTML 5, mais ne paniquez pas !), tels Bespin, qui ne definit qu’un aspect visuel. Le choix est largement justifié, mais ça ne change pas la problématique : sans JS, point de salut. Evidement, on peut toujours [...]

By: Simon Kenyon Shepard

Simon Kenyon Shepard — Tue, 17 Mar 2009 20:01:01 +0000

Hi Ben,

an interesting and deep thread to be sure, thanks for pointing me in it’s direction, it’s nice to see controversy produce some hard hitting results and dispelling some myths.
I’ve responded to your message here:
http://www.trisis.co.uk/blog/?p=113#comments

I’d be curious to know what lessons you guys have learn’t from doing this in Canvas, whether if speed and flexibility weren’t an issue and you could have done this successfully in XHTML/CSS/JS would you have?

By: Supporting the system clipboard in your Web applications; What a pain! on Dion Almaer's Blog

Thu, 26 Feb 2009 17:02:40 +0000

[...] Why Canvas? [...]

By: Ray Cromwell

Ray Cromwell — Sat, 21 Feb 2009 00:34:14 +0000

Hey, NeWS was a great for it’s time, and the idea of Postscript-like rendering surfaces lived on in DisplayPostscript on NeXT, and Quartz on OSX.

I don’t really see much different between building GUI toolkits for the canvas, vs building them for the DOM, the exception of the browser handling hit detection/event propagation, and CSS handling layout decisions. Otherwise, people already build completely custom widgets today which override tons of native browser behavior.

By: Chris Ryland

Chris Ryland — Sat, 21 Feb 2009 00:25:45 +0000

This is pretty amazing. Look forward to what you can do with it.

But the disturbing thought hit me: isn’t this just re-inventing NeWS, this time with Javascript instead of Postscript, and Canvas as the new Postscript-like rendering surface?

You even have to solve the same problem of building GUI toolkits for your Canvas-based “window server.”