What is the goal of WAStaticHtmlCanvas? It has no users and doesn't do much...

I think Seaside's canvas API is really nice and would be useful even outside a 
seaside context.
At some point I had the idea to make a Pier-to-static-website exporter, in 
which case WAStaticHtmlCanvas 
would have been useful. There is already some existing code but it's a couple 
years old and probably needs a 
rewrite… so that shouldn't refrain you from refactoring.

One of my main goals in 2.9 is to make the various parts of Seaside (definitely
including the Canvas) useable without all the other parts, so I'm definitely in
favour of support what you're talking about.

I think there's a way to support that in a better way now. I'm picturing just 
giving
a regular canvas a rendering context with the appropriate document, whatever
actionUrl you want, and probably NO callback cache if you don't want callbacks.

I've just started trying again to refactor these a bit so we'll see where I get 
to.

Name: Seaside-Canvas-jf.52
Author: jf
Time: 21 February 2009, 12:58:35 pm
UUID: fb5e441f-901b-4eb2-9cd3-03ee8e614b4a
Ancestors: Seaside-Canvas-jf.51

http://code.google.com/p/seaside/issues/detail?id=31

There are no senders of WAStaticHtmlCanvas. The only thing it did was allow you 
to
hardcode a Document different from that in the RenderContext. Presumably this 
made
sense at some point in the past but you can just make a new RenderContext (or 
copy
one you already have) or change the document on the RenderContext. No need for a
special renderer to do this.