Re: SVG icons

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: SVG icons
by Niels van Mourik on Sunday 25/Mar/2007, @20:53

Well, There is no such thing as a dumb question.

Icons are created in different sizes, like 16x16, 32x32 etc. Therefore they commit each icon 7 times =).

And yes, SVG is used, at least, that's where they create there icons in. But they compile them into png's so it wouldn't bloat the user's performance.

Tho Aaron came up with an interesting idea to use SVG images using caching: http://aseigo.blogspot.com/2007/03/efficient-scallable-icons.html

Related Links

·   Articles on Developer
·   Also by Niels van Mourik
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: SVG icons
by JSob on Monday 26/Mar/2007, @01:20

So if SVG is the "source" of the icons, shouldn't they be committed once, then png(s) built at compilation ?

[ Reply To This | View ]

Re: SVG icons
by superstoned on Monday 26/Mar/2007, @01:57

Many of these icons have to be build using inkscape, afaik that's the problem. There aren't many svg render engines having all the features these artists use...

[ Reply To This | View ]

Re: SVG icons
by Anon on Monday 26/Mar/2007, @02:40

Small (i.e. 16x16, 24x24 - even 48x48, sometimes) icons often need to be re-touched by hand, as automatic scaling cannot be relied upon to maintain the details, colours etc that the artists deem important.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I guess my process varies from time to time." -- George Staikos
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.