But, ctrl clicking on an application is going to allow me to extract the icons & images from it? say Mail for example, how would I go about extracting the toolbar icons?

#106607

When you unstuff an .app file on windows it changes into a normal folder :blink: :canadian:.

#106625

Lol, i dont mean look inside teh box in which you computer came with "view package contents", there is an option called view package contents, this will take you to the files of the app (works with konfabulator widgets as well, thank you photo678), if there are any icons, it will also work.

Else, there is this little app (look for it in versiontracker.com) called "iconverter", you drag anything (folder, image, icon, whatever basically) and you can set it up to extract the icon to a png, to a icns (if youre converting a .ico from windoze for example) or to a .ico.

Hope this helps

#106626

HAH!

Like I said my box wasn't exactly able to be turned on at that time.. guess there is a simple "show package contents".. neat stuff. Easy as pie.

Never knew the .app thing was really a .zip file. Learn something everyday.

AND, of course I knew you didn't mean look INSIDE the computer.. i already had the case open and didn't see any icons! :lol:

#106632

Originally posted by rjohnstone@Jan 28 2004, 10:51 AM
However, don't bother with any M$ writtem Mac apps.
They do not allow the package contents to be viewed.
Still trying to figure that one out.

Same here, however I came into a bit of information which *might* work, I would've tested it but the designers at work haven't let me use their macs in a while ( means pressing enter):

Apple .dfonts - what are they and how do I use them?
Abstracted and paraphrased from MacAddict August 2003
Mac files (including fonts) have two “forks” - a data fork and a resource fork. In Mac
OS9 and previous Mac OSs the fonts stored their data in the resource fork. In OS X that changed
and now fonts store their data in the data (“.d” font) fork. Obviously this created an
incompatibility between OS X fonts and OS 9.
There is, however, a way to convert .dfonts into usable OS 9 fonts. It requires the Mac
OS X Developer Tools to be installed. Then, in the Terminal:
1. Go to your fonts directory
(cd /Library/Fonts)
2. Touch the font you want to convert. This creates a new font file for use in Mac OS 9.
3. Copy the data fork from the OS X font into the resource fork of the OS 9 font:
(cp Baskerville.dfont Baskerville/rsrc)
4. Set the type and creator and register the new font:
(/Developer/Tools/Setfile -t FFIL -c DMOV Baskerville)

Well there you have it, it might be that the whole app is packaged and set in the data fork (the one you can normally see), the problem would be if it has both forks stuck in there. Might work, might not... food for thought. But remember BACK UP before doing this!

#106687