FROM : Michael Vannorsdel
DATE : Sun May 18 00:46:23 2008
Well you didn't present the secret handshake that would open immediate
access to such information.
Actually, it was probably not brought up earlier as it's kind of an
unsaid list etiquette rule exercised by some not to critique someone's
choice of APIs unless specifically asked for. Most will try to
directly address your questions or problems no matter what APIs you
chose. It can be somewhat rude to flat out say your choice of APIs is
folly, and sometimes presumptuous that the specific APIs were not
chosen for reasons undisclosed in the original problem. If you're
open for API alternatives you can state so with something like "...is
there an easier or more reliable way to do this?". Otherwise some
will assume you have your reasons and will do their best to help make
the chosen APIs work for you.
NSWorkspace is an oft-overlooked class that contains many useful
external utilities. The class name doesn't exactly scream URL
launching or icon fetching, ect. Though I'm not sure what name would
completely describe NSWorkspace's broad ranged functionality.
On May 17, 2008, at 3:37 PM, Mike wrote:
> Adam R. Maxwell wrote:
>> On May 17, 2008, at 2:15 PM, Mike wrote:
>>> I solved the problem using the IconFamily library:
>>>
>>> http://iconfamily.sourceforge.net/
>> IMO, that's killing a mosquito with a shotgun :).
>>> It just astounds me there is no support for icons in Cocoa.
>> You can use -[NSImage initWithIconRef:] if you only support 10.5
>> and later. On 10.4 and earlier you can use -[NSWorkspace
>> iconForFileType:NSFileTypeForHFSTypeCode(kSomeIconCode)] if you
>> only need a 32x32 icon, but it's only a few lines of code to draw
>> an IconRef to an NSImage of the appropriate size.
>
> Oh NOW you tell me! :-)
DATE : Sun May 18 00:46:23 2008
Well you didn't present the secret handshake that would open immediate
access to such information.
Actually, it was probably not brought up earlier as it's kind of an
unsaid list etiquette rule exercised by some not to critique someone's
choice of APIs unless specifically asked for. Most will try to
directly address your questions or problems no matter what APIs you
chose. It can be somewhat rude to flat out say your choice of APIs is
folly, and sometimes presumptuous that the specific APIs were not
chosen for reasons undisclosed in the original problem. If you're
open for API alternatives you can state so with something like "...is
there an easier or more reliable way to do this?". Otherwise some
will assume you have your reasons and will do their best to help make
the chosen APIs work for you.
NSWorkspace is an oft-overlooked class that contains many useful
external utilities. The class name doesn't exactly scream URL
launching or icon fetching, ect. Though I'm not sure what name would
completely describe NSWorkspace's broad ranged functionality.
On May 17, 2008, at 3:37 PM, Mike wrote:
> Adam R. Maxwell wrote:
>> On May 17, 2008, at 2:15 PM, Mike wrote:
>>> I solved the problem using the IconFamily library:
>>>
>>> http://iconfamily.sourceforge.net/
>> IMO, that's killing a mosquito with a shotgun :).
>>> It just astounds me there is no support for icons in Cocoa.
>> You can use -[NSImage initWithIconRef:] if you only support 10.5
>> and later. On 10.4 and earlier you can use -[NSWorkspace
>> iconForFileType:NSFileTypeForHFSTypeCode(kSomeIconCode)] if you
>> only need a 32x32 icon, but it's only a few lines of code to draw
>> an IconRef to an NSImage of the appropriate size.
>
> Oh NOW you tell me! :-)
| Related mails | Author | Date |
|---|---|---|
| Michael Vannorsdel | May 17, 17:06 | |
| Michael Babin | May 17, 17:29 | |
| Mike | May 17, 22:16 | |
| Mike | May 17, 23:15 | |
| Adam R. Maxwell | May 17, 23:31 | |
| Mike | May 17, 23:37 | |
| Uli Kusterer | May 18, 00:16 | |
| Michael Vannorsdel | May 18, 00:46 |






Cocoa mail archive

