Does anyone want to hear from the teeth?
Do more.
Report the work situation as needed:
I have started to fully apply SVG, And the whole person is comparing chicken blood. I found that I can always find chicken blood and inject it myself. In fact, I have studied the practicality of SVG six months ago. I would like to write an article in August.ArticleIt compares PNG, css3, and SVG, and points out the biggest drawback of SVG at that time: SVG can only be in background or link at that time, which means that SVG is as independent from HTML as IFRAME, in this way, the SVG technology is independent of the team, and cannot cooperate with HTML, CSS, and js to work together. This was a huge loss I had studied with great excitement half a year ago, and then I gave up.
A routine check was performed about a month ago. It was unexpectedly found that inline SVG in HTML5 appeared in the list, and ie9, ff4, and chrome 7 both supported. SVG can be inline! OMG! You don't know. I immediately scream! I started to plan and use it directly when I rolled up my sleeves. Through the practical use in the real environment during this period, I had a new experience and a comparison with PNG and css3, I am still thinking, and there are still many drawbacks and restrictions. The day before yesterday, for a general and concise design, I thought of the early morning for the coding of a small icon, I tried a variety of storage methods and tried countless extraction methods. I still couldn't find the perfect solution after I checked the SVG tutorial and turned it over. Finally, I had no choice but to make a compromise. In this case, the number of bytes that achieve the same visual effect is reduced from> 40 K to 3 K, and the real-time rendering is instantly displayed. Unfortunately, the pursuit of perfection is not perfect, and I am still worried, because the perfect situation only requires about 1 K.
The night before, I tried SVG effects for HTML elements again. Naturally, you know, sorry, I scream again. Although it is still very thin and not practical, it points out a future: You can perform various filter rendering like PS on html. What's different is that PS is "cganimation ", SVG is "real-time rendering "! For example, use Gaussian blur to create a depth of field on the page! This is the effect that I had always desired when I designed a pop-up window many years ago. In today's popular hierarchical design, there has never been a depth of field. Should you scream ???!!!
Lossy jpg-> lossless PNG-> finite vector css3-> native vector SVG-> inexplicable canvas.Canvas is something that I haven't touched yet. Currently, SVG is suitable for processing small elements, while canvas is a larger and more free canvas. No matter what you do, it doesn't matter. One way slowly drops, and I will walk over and slowly drop, and you will not see me.
Any path, as long as the kung fu is deep, the iron rod is ground into a needle.
Of course, I don't pretend to be objective and objective. My point of view has always been as brilliant as blood: if we look at Adobe Flash and Ms sliverlight from a macro perspective, it even includes Apple's object C, which is located in the north and south of Hongda river. In the face of open HTML5, where can we find a way out!