<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
<title></title>
</head>
<body>
<p> </p>
<div style="margin: 5px 0px 5px 0px; font-family: monospace;">
On 22 March 2010 at 15:37 Alexandre Julliard <julliard@winehq.org> wrote:<br />
<br />
> Joel Holdsworth <joel@airwebreathe.org.uk> writes:<br />
><br />
> >> I still think that having to commit 10 source files per icon is not<br />
> >> acceptable, even with subdirectories.<br />
> > I agree it is a lot of source files, but I don't see that that's a problem if<br />
> > they're stored neatly within a resources subdirectory. user32.dll has a lot of<br />
> > images, but that's not a problem for this reason. In fact by creating resources<br />
> > subdirectories surely I'm tidying? because it unclutters the mix of resources<br />
> > and source code in many dlls.<br />
> ><br />
> > The issue is that the 9 images are never going to go away - a full XP icon has<br />
> > at least 9 independant hand crafted images to go into it. Vista and 7 icons have<br />
> > even more.<br />
><br />
> As far as I understand it's possible to store everything in a single SVG<br />
> file. I don't know if tools like inkscape can support this directly, but<br />
> it's all XML so a simple perl wrapper should be able to do anything we<br />
> need.<br />
</div>
<p style="margin: 0px;"> </p>
It is possible with a multipage SVG (which Inkscape doesn't support yet, and can't be rendered RSVG) and embedded bitmaps for the hand tweaked images (which are at beta stage AFAIK). That's bad news, but these obstacles can be overcome by me spending a lot of my time (which these days is in really short supply) writing scripts in Perl, but that would require me to use Perl (which I don't know and would have to learn)*, and could take several more months.<br />
<br />
It would also require a dependancy on some kind of command line image handling tool like ImageMagick or Python image stuff (which I'm sure you won't like) because RSVG only renders to 32-bit, but we need to output to 4-bit and 8-bit without screwing up these palette (which may be very hard).<br />
<br />
The end result would be 1 file rather than 9, but in a format which is harder even than ico for artists to work with given the state of todays tools.<br />
<br />
* I do use python though - is there any in the project?<br />
<br />
Speaking personally: This project has already taken me over a year to get this far, and after all this painstaking work I'm really keen to get it out to the world, but I'm so short of time right now, and it feels like every time I try and submit, there are more of these never ending hoops to jump through. From my perspective I won't abandon this work that I've spent so much time on, but it's becoming this never ending nightmare of obstacles. I'm looking at the big picture and wondering; is turning a very minor mess of 9 files into 1 per icon really the best use of my time, when I could be productively contributing to areas of need within the FOSS world that will have a real effect on FOSS users.<br />
<br />
I want to keep pursuing this and I respect your opinion very much as the veteron maintainer of this project. Your uncompromising comittment to quality has resulted in an excellent and long standing project, it's just that I'm finding the lack of flexibility quite hard to cope with. Is there no way we could compromise on this?<br />
<br />
Joel<br />
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
</body>
</html>