All icons should be SVG. We need to make this clear. If they're not available in SVG they should not be checked in. The Gnome SVG engine is optimised for Adobe Illustrator, we sometimes have problems because we focus the standard. However AI SVG files can be easily fixed to work. We should use CVS artwork module for sources. For 4.0 we would like scaleable icons available. The framework is there but is too slow just now. Question if an SVG screen saves is possible, yes if it uses the icon standard. Small sizes of icons should be rendered by hand because they never look good generated from SVG automaticlly. 16x16 and 22x22 and SVG should be all we want to deal with. The rest should be made at compile time or maybe on the fly and cached. If you cache icons this will take a lot of space in /home directories. QIconCache will happen in Qt 4 so we don't need to worry about it. It will be in memory not on hard disk. KSVG2 should be finished for KDE 4, it will be in the same state as KSVG 1 was before they stopped working on it. It will not need libart because Qt 4 will have everything needed. This will improve speed by 10 times because it uses OpenGL not XRender (which isn't always available anyway). DOM parser will soon become much faster too. QDOM will be faster in 4 but can not be faster than libxml2 because of the clever/hacky things libxml2 does. So choice is good. What else can be done with SVGs on the desktop? Background images would be great because they need to be scaled. Discussion of kdm themes being not as good as gdm. Ossi is working on this in kdenonbeta paid for by SuSE. Discussion on animated SVG icons, there are various technical ways to do this but no programs support it yet neither do the renderers. During development cycle for KDE 4 we could disable creation of PNGs and just make an X for any icons without an SVG. This will encourage creation of SVGs. Generally agreed to be a great idea. Icon theme shareing with Gnome. This has been worked with in Novell. There are lots more icons in KDE so the KDE icon sets fullful Gnome. SuSE did make a Crystal icon set for Gnome. Can we make Karbon good? There are no artists on the development team is one major issue. How far away from being good enough is Karbon? It is as far away as KSVG because it uses libart which is a dead end, will have to wait for Qt 4. Libart is not longer being developed much. Gnome's hope is librsvg and Cairo. Cairo is at a very early stage of development says WildFox. Wish for Karbon to be easier to compile without requireing to compile all of KOffice, this requires playing with Makefiles, WildFox says he'll make a script to make this easier. Being in KOffice means Karbon and Krita won't be installed with SuSE by default etc. Website, we should change it to standard KDE design. Not quite sure who the current maintainer is (Luci who does wiki.kde). The website should have a roadmap. Maybe a competition on kde-look telling them to follow new interface guidelines. Should we have a standard CSS file for KDE icons? This would be unlikely to be practacle or useable. Discussion on resizeable widgets for high resolution screens. This is a Qt problem but will have to happen eventually. Getting people to make artwork for KDE. Frank (Karli) suggests a page on kde-look with open beasties for artwork. Icon request page on kde-look with option for payment via paypal etc. Point that artist people don't look at bugs.kde.org so there needs to be a better interface. Point that icon requests need a lot of work, finding out what the icon should show etc not just drawing that, requests should include a description of what the icon contains.