OK - time for an update. Here's what I did (am about to push to the master branch):
1. Created SVGCanvas object in the library, as an SVG-based, drop-in alternative to GWTCanvas. Every attempt has been made by me to make the API 100% compatible with GWTCanvas. 2. Modified examples/gwtcanvas so that it also contains a demo app called SVGCanvasDemo alongside the usual GWTCanvasDemo. The new app just wraps and subclasses the old one, substituting an SVGCanvas object for the GWTCanvas one. None of the demo application code is changed other than that (except for the next bit). 3. Added a fillText() call to the demo since it is in Pyjamas' version of GWTCanvas. Also added it to SVGCanvas, and added an empty method to the IE GWTCanvas adapter (since there is currently no VML drawText code there) so the example doesn't break on IE. 4. Added SVGCanvasDemo.py to the build.sh and __main__.py files so that it builds the SVG version. NOTE that the SVG version is not included in the examples index.html summary. This because SVG is pretty bogus on most browsers, so it really should only be used for Firefox. Can be used on Safari and/or Opera in a pinch, but GWTCanvas works fine on those. In short, this change should not affect the 99.9% of the world who are happy with the current GWTCanvas. If you need to support a very large canvas on Firefox/Windows, then SVGCanvas is the ticket for you. git push coming soon to a repo near you.... Rich Newpol On Tue, Feb 21, 2012 at 11:08 AM, lkcl luke <[email protected]> wrote: > On Tue, Feb 21, 2012 at 3:52 PM, Rich Newpol <[email protected]> > wrote: > > >> of course it bloody well is! ... like... you had to ask? :) > > > > > > My corner of the world seems so insignificant at times :) > > yeahh, unfortunately that's what everyone thinks, but the amazing > thing about such small "insignificant" contributions is that when > combined they become powerful and significant. > > ... that's evolution, baby :) > > > > Hm, so the override is in my app - simply to *prevent* my app from using > > SVGCanvas on browsers other than Firefox, > > ah good ok. > > > because a lot of them still don't know how to spell SVG in a standard > way. > > doh! > > > The SVGCanvas widget itself > > doesn't know or care about any of it...SOOoooo, should I cook up a new > > sample or perhaps tweak an existing Canvas sample? > > new one please, unless you can make _two_ versions of the same > widget, side-by-side, one with the override and one with not. > > l.
