<div><div><div><div><br><div class="gmail_quote">On Fri, Jan 21, 2011 at 10:52 AM, Reece Dunn <span dir="ltr"><<a href="mailto:msclrhd@googlemail.com">msclrhd@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 21 January 2011 08:36, Damjan Jovanovic <<a href="mailto:damjan.jov@gmail.com">damjan.jov@gmail.com</a>> wrote:<br>
> Should we reconsider libicns? Apple's APIs obviously can't be relied upon.<br>
<br>
</div>You could always:<br>
<br>
1. �check for native support (including presence of<br>
kIconServices16PixelDataARGB) and use if present;<br>
2. �check for libicns and use it if present;<br>
3. �disable ICNS support.<br>
<br>
using autoconf checks. That way, support is enabled where available<br>
(instead of relying on OS version detection logic).<br>
<br>
NOTE: the libicns check is optional as it would require maintaining<br>
both native OSX and libicns versions.<br>
<font color="#888888"><br>
- Reece<br>
</font></blockquote></div><br></div></div></div></div><div>About option 3:</div><div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8">December 2010 desktop OS market share, Wikimedia stats:<div>
Intel MacOS X 10.4 � 0.49%<div><div>Ubuntu 10.10 � 0.25%<div>Ubuntu 10.04 � 0.34%.</div><div><br></div><div>If distribution of Wine users among Linux and MacOS is roughly equal, then even if we disable icons on�only Intel MacOS X 10.4, it will break for almost as many users as are using Ubuntu 10.04 and 10.10 put together.</div>
</div></div></div></div><div><br></div><div>Damjan</div><div><br></div>