I found out that if you program using Carbon you have "Icon Services"
and with that you have access to a large amount of system icons. (See
http://developer.apple.com/documentation/Carbon/Reference/IconServices/icon_serv
ices.pdf
from page 85 and down for all available constants)
A bit strange that these system icons are not available through Cocoa.
I did find a class named IconFamily ( available here
http://homepage.mac.com/troy_stephens/software/objects/IconFamily/ )
that seems to wrap access to the Carbon "Icon Services" for use in
Cocoa. I'm not sure if this is what I need but I will try this out.
Thank you for Jaspers Housers' link. He was already on top of my list
for designing my icons if my programming for the mac becomes a success.
(currently I'm just learning Cocoa but I'm a developer for Windows by
occupation).
There are 2 things I know:
1) Icon/graphic design can make or break your apps success.
2) I personally can not design appealing graphics but I do appreciate
them.
I'm only worried that letting others design my graphics is going to be
too expensive for a hobby Mac developer like me.
Tim
> > I'm hoping to find common images like the gear on action buttons and a
> > + and - sign, maybe a folder image, alert images (yellow triangle) or
[quoted text clipped - 19 lines]
>
> patrick
Patrick Machielse - 22 Jul 2006 12:43 GMT
> I found out that if you program using Carbon you have "Icon Services" and
> with that you have access to a large amount of system icons. (See
> http://developer.apple.com/documentation/Carbon/Reference/IconServices/ico
> n_services.pdf from page 85 and down for all available constants)
Look nice. I'm going to have to read that ;-)
> A bit strange that these system icons are not available through Cocoa.
Well, there _may_ be a way in Cocoa, although it might not use the
'imageNamed:' method. For instance, if you wan't access to program or
file icons, you can use the NSWorkspace methods:
iconForFile:
iconForFiles:
iconForFileType:
Even if Cocoa doesn't offer the functionality you need, there is nothing
stopping us from using Carbon calls from within our Cococa code. That's
the beauty of Objective-C being C as well. Carbon is not deprecated, and
in fact there are numerous occasions where you have to 'drop down' to
Carbon, when Cocoa doesn't offer some functionality. Sometimes
inconvenient, but on the other hand it keeps Cocoa managable, and
prevents unneccesary duplication between frameworks.
> There are 2 things I know:
> 1) Icon/graphic design can make or break your apps success.
> 2) I personally can not design appealing graphics but I do appreciate
> them.
Yes, designing the icon can be harder than writing the code ;-)
patrick
Simon Slavin - 24 Jul 2006 23:49 GMT
On 22/07/2006, halt001@gmail.com wrote in message
<1153562313.142414.186280@b28g2000cwb.googlegroups.com>:
> A bit strange that these system icons are not available through Cocoa.
No it's not.
These icons are used by system routines. The routines may one day change:
instead of a still icon they might show an animation. Or they may change
to something that doesn't need an icon at all: the need for that function
might go away entirely. Therefore accessing any of these icons directly
is almost definitely going to be the wrong thing to do. If you want one
of these icons, call the system routine that causes it to be displayed.
That way, when the system's behaviour changes, your program will
automatically change its behaviour to match.
If you want to design your own icon, do so. If you want to study a System
icon to make a variant of it, get it on the screen and do a screen-dump.
But don't feel bound to copy the System's look: it may change.
Simon.

Signature
http://www.hearsay.demon.co.uk