Just last night I tested out a well known logo. It's an awesome design tool, but for delivery/bandwidth/reach it's hard to top PNG. I say this as someone who builds UIs with vector graphics. You can produce a PNG at twice the original size (for retina displays) and still have the filesize be an order of magnitude smaller - not to mention better coverage for legacy browsers (no need for javascript or polyfills). Unless you are showing very simple shapes/designs or specifically need to modify parts of the graphic with the app, there is not a whole lot of incentive to use SVG. SVG compressors may remove this, but I haven't tested it (feel free to edit if you have).when you export a PNG in Inkscape it did/does save the absolute path to this directory in the SVG when you save some SVG editors may store metadata in your SVGs, increasing file size and possibly unintentionally exposing data.your graphics are photos or other difficult to vectorize images.most people have a PNG compatible editor on their computer.existing tooling for creating PNG spritesheets.
Due to their text based nature, you don't need low-level libraries or powerful servers to create them. you can generate SVGs dynamically, either on the client or server.you can style SVGs and parts of SVGs with CSS (changing colors, outlines, etc.).you can embed SVGs and do real-time modifications to them with JavaScript and the DOM.you can scale them up/down will, such as to to a hover effect.it seamlessly supports browsers of any size, especially with css's background-size.
0 kommentar(er)
