What are the strengths and weaknesses of the various libraries of the GWT holding?

I am currently developing website development skills and I think it would be interesting to create a program like Paint. I would like to use something like an HTML5 element, but I want it to be useful in IE (I do not expect IE 6 to be compatible with it, but IE 7+ will be nice.)

I still know about the vaadin graphics library, but I was not happy with that. I also reviewed the Google proposal, but it has been deprecated since then and is not recommended.

So what else is there and what is the strength / weakness? I do not agree with the GWT, so any suggestions regarding a different route are also welcome.

+4
source share
2 answers

Oookay ... it will be a little to write ...

About a year ago there was an incubator project with Canvas support. Moreover, they not only supported the html5 canvas tag, but also had vml emulation for IE6 and higher.

The incubator project was then discontinued, and they moved a lot of material to the main line, including Canvas.

Unfortunately, the emulation was not good enough (html5 canvas is procedural, vml is declarative), so emulation could not do 100% in the same way as its own html5 canvas. They killed the emulation.

Then there are projects that use ex-canvas. This is a javascript emulation library that is used, for example, by gflot. I have not tested it yet, but it was a common way to include IE in the use of canvas tags.

Thirdly, now I am using gwt graphics. This is a good library that does NOT use html5 canvas, but instead embeds svg in a browser that supports this. In other browsers, for example, IE vml is used. Both are declarative why they are more compatible.

So you need to decide where to go :)

All the best, Thomas

+1
source

raphael4gwt may be what you want (http://g.raphaeljs.com/). Also you can easily draw any vector graphic interface. It is based on SVG and VML on IE <9.0, so you should not have problems with the browser. Example Paint as a program .

0
source

All Articles