Re: .oafinfo and icons

[Miguel de Icaza <miguel helixcode com>]

> > But we won't care about that, since we're more likely to have local
> > .oafinfo files than non-local ones. To quote miguel:
> 
> You still need to handle the non-local case.

For the non-local case, the worst case scenario is you get the stock
icon.  What is the problem with this?

In two years since we have been using CORBA, I have seen barely people
using remote setups.  It is not even a common setup, and not
something you distribute to your friends typically.

And if you do, you do not pass only a .oafinfo file, you typically
hand over an RPM that would nicely include your .oafinfo, and your
nice icon.

> Yes, but this is not "use a solution because it works for one thing" land
> either.

It works for 99.99% of the cases.  For the 0.01% it will just mean
that you have to copy another file.

Also, adding the icon to the .oafinfo file means that 100% of the
existing tools can not be used to edit the icon and that special
handling needs to be done for 100% of these tools.

The option "use the filename" works with every existing tool.  So I
think we need to get our priorities right here.
Miguel.