Free headers software for mac

Developers know how to weak link to the systemFramework of Mac OS X, while the header files in the various frameworks provide the prototypes of the functions available. CodeWarrior does not provide precompiled headers for CFM-based targets, only MACHO-based targets on OS X.

Flatten OS X Headers provides a flattened version of the many framework header files, and does some other interesting things.
The flattened headers can be used in CW 4, 5, 6,7, 8, and be precompiled.

he advantage then is that one can access any function, use any type, without worrying that it may not be defined. Obviously, the tool does not make the function pointers to call into the systemframework, but having these precompiled headers in a CFM-based target, makes the CarbonLib obsolete, and allows for the most updated "libs" available.

The files coming out of a pretty much all Digital cameras are in the Exif flavour of Jpeg files. Exif files are for the most part Jpeg files, but start with a different header block, and contain additional data sections with camera settings, as well as a preview thumbnail picture as part of the Exif header. Most editing / viewing software just skips past the Exif header and ignores it outright, so you normally dont notice its even there.
Because I am interested in photography, I am always curious just exactly what settings my fully automatic digital camera actually did end up using. Theres a few programs out there that can parse some of these headers, but I couldnd find one that I could compile to an executable, and none that actually figured out what the camera settings were from the various confusing ways in which the fields can be expressed.
Parsing the data of interest out of an Exif header is not straightforward. There is a large number of ways that simple data such as shutter speed or aperture setting can be expressed in inside of an Exif header. It can be an integer of various forms, or a fraction or floating point, which must subsequently be raised to a power to get the true value. Then it can be stored big-endian or little endian, and there are different fields for expressing the same values! It sounds like complete eveolutionary anarchy, but I think its just a comitee designed spec.
With all its complexity, interestingly enough, plain text ASCII would both be smaller in size and easier to parse! So I wrote this command line driven program to parse through the little file system in the Exif headers and extract the stuff I really care about: What the digital camera settings really were.
The other thing I realized is that the files coming out of most digital cameras contain an integral thumbnail as part of the Exif header. This thumbnail is used for flipping through really tiny images on the LCD, although most cameras, when viewing just one image on the LCD dont use it (too little detail).
This thumbnail takes up typically around 10k of data in the header. Once the picture is off the camera, even the software that comes with the camera doesnt use the thumbnail in the file, so its really just wasted space. So I added an option (-dt option) that reads the whole Jpeg image, figures out where the useful part of the Exif header ends, discards the thumbnail, and saves it back to disk. where the thumbnail is, and writes everything (including the rest of the Exif header) back Result: 10k space savings, with all the important information, including the digital camera information in the exif header intact. No loss of image quality, and very fast. So far all software I tried, including the software that comes with the digital cameras, has worked fine, and is still able to parse the Exif header.
Main features:
- Integral low-res Exif thumbnail
- Shutter speed
- Camera F-stop number
- Flash used (yes/no)
- Distance camera was focused at
- Focal length and calculate 35 mm equivalent focal length
- Image resolution
- Time and date picture was taken
- Camera make and model
- Up-right images according to rotation tag using jpegtran
- Set or relative adjust internal exif timestamps
- Re-name or date stamp fils according to exif timestamp
- Transfer exif headers between images
- Edit jpeg comments
- Delete exif or comment sections from jpeg images
Enhancements:
- Added -rgt (regenerate thumbnail) feature.
- Added -orp and -orl options.

Phoenix Slides 1.2.6 is described as a great and powerful full-screen slideshow program/image browser, for flipping through folders or disks full of images.

Phoenix Slides also does lossless JPEG transformations and can display EXIF data.

Major Features:

1. Fast (pre-cached) full-screen slideshows
2. Rotate/zoom in slideshow
3. Fast JPEG thumbnails (uses Epeg)
4. Lossless JPEG rotation
5. View EXIF data, JPEG comments
6. Search subfolders (recursively) for images
7. Move files to trash, set image as desktop
8. Supports drag and drop, Finder aliases
9. Localizations: Chinese (Traditional), German, French.

Enhancements:

• Works with Mac OS X 10.6 (Snow Leopard)
• When slideshow is running, slideshow no longer switches screens
• When running in random AND loop mode, re-randomize at the start of each loop
• Fixed crash on badly formatted ("field type mismatch") EXIF headers
• Improved Italian localization.

Requirements: Require Mac OS X 10.3 or later.

X-ess Errors provides error names and descriptions for error codes from the vaults of BSD and Carbon/Classic esoteria.

X-ess Errors matches the standard error codes used by OS X with their names and descriptions, as are provided in the OS X programming frameworks. Thats it. It doesnt tidy up your hard disk, help you with your Math 105 homework, or give you advice on how to make a move on the cute guy/girl in the cubicle down the aisle*. It just...produces...error information. Which can be quite helpful (or mystifying) at times.

These features are derived directly from headers provided by Apple Computer.

Email Searcher is a small script that finds all email addresses in the header or the body of selected Entourage or Outlook Express messages. The script can then create links between contacts that are in your address book, or you can make a new contact.

Machilles is a proxy that allows editing of outgoing HTTP headers, for use in testing web applications.
It also allows you to edit data sent in POST requests.
Inspired by Windows programs Achilles (and PenProxy).

To use Machilles, simply press start (assuming you have auto-setup enabled). Each time you type a URL in your web browser or navigate to any website, switch to Machilles. A drawer describing the Cookies, User-Agent, and Data in the request is shown. These fields are editable. To send the request, click send. Machilles makes it easy to send custom-made HTTP requests in order to test web applications.

With auto-setup Machilles will now set up the proxy for you. However if you choose (Auto-setup proxy), this may require user authentication. If you do not wish to authenticate, instructions for manual proxy set up can be found below in the section "manual proxy set up".

Intercept Client Data switches Machilles between stopping traffic and just allowing it to pass through. The difference between not intercepting and stopping the proxy is that while not intercepting, traffic is still routing through Machilles. It is intended as a fast switch between intercepting and not, because fully stopping the server after lengthy use may require authentication.

Intercept Requests allows the user to customize which requests are stopped. Since Machilles relies on the referer field to determine when to intercept requests (so that each image file on a webpage your browser requests wont be intercepted), and clicked links have referer fields filled out, Machilles gives you the option to change the intercepting pattern.

The local port is the port on your machine where Machilles listens. It is recommended that you block this port with your firewall, because Machilles is not intended to run as a public HTTP proxy, and running an open HTTP proxy on your machine is very often a security concern itself. You can typically ignore this field, unless you are setting up the proxy manually.

EOReporter is a command-line tool generate files (documentation, usually) based on information in an EOModel. Files can be generated on a per-entity, per-model, or per-model group basis. Some provided templates generate HTML documentation similar to the EOModeler list view. EOReporter is a direct descendant of the EOGenerator application.
It is possible (among other things) to generate PB.project and Makefiles (pre-OS X) that are always up-to-date with the entities in your models. It can also be used to generate HTML documentation similar to what is listed in EOModeler, create a script that can be used to removed obsolete entities from CVS, or turn an EOModel into an XML file.
Enhancements:
- Built as universal binary for use on Intel Macs.
- Added barebones EOF headers to allow compilation with WebObjects 5.3. Contributed by Mike Schrag.
- Updated with new MiscMerge; adds encoding support and fixes a few bugs.

MacSniffer is a front end to the built-in tcpdump packet sniffer on Mac OS X. MacSniffer allows you to view all of the traffic on a network connection, such as ethernet.

MacSniffer includes a filter editing interface and a filter library to easily construct and reuse packet filters to view a subset of all the traffic on the connection, such as just that destined for a specific host or port.

You can choose the level of detail you want captured, from just the minimal packet headers (showing source and destination hosts and ports) up to a full hex and ASCII dump of the packet contents.

MacSniffer can be useful for diagnosing many network problems, debugging client/server programs, and scanning for particular network exploits in real time.