Free application framework software for mac

Do you need a starting point for a application that uses multiple document windows?

Do you want to maintain a menu that shows a list of the open windows?

Do you have documents that you need to save when closed and thus need to write code that asks the user whether he wants to save, discard or cancel?

Then get TTs App Frame. It is a RB1 compatible project with documented source code that takes care of all this for you.

The Authorization.framework is a simple Objective-C wrapper around Apples Security framework. It provides an Authorization object which can be used to authenticate users and run tools with privileges.

It is simply a convinience class. I didnt like having all those Security framework calls all over the place in my code and came up with this to clean things up and make using the Security framework features easier.

The PYMIDI Framework provides a set of classes and utility functions for communicating via MIDI, both with physical devices (MIDI interfaces, MIDI controllers, etc.) and with other MIDI software.

It provides a nice Objective-C interface to the basics of CoreMIDI while still allowing you to access the underlying CoreMIDI objects for advanced stuff.

It makes a couple of normally difficult things very easy: generating good human readable endpoint names, saving references to endpoints in files, etc.

Template.framework provides a simple Template object for use with parsing template files. It uses only Foundation classes and can be used with command line tools.

It is currently used by StartupItem Manager to create the property list and shell scripts used in the StartupItems it creates.

Application Enhancer (APE) is a system used in our and third-party products that helps them to enhance and redefine various applications behavior running on your system.
What exactly is Application Enhancer? It is a combination of a Framework (a collection of commonly used code that can be re-used across different Application Enhancer modules) and a system daemon (faceless background application).
Application Enhancer performs its task by loading plugins (Application Enhancer modules, or APEs for short) containing executable code into the running applications.
Once loaded, the APE module performs the needed modifications (such as redefining the minimize window action, or customizing the standard Apple menu) on the launched application memory space, never touching any files on disk, utilizing set of functions defined in the Application Enhancer framework.
To help the APE modules to be loaded into newly launched applications, the Application Enhancer daemon (aped) is used.
Can Application Enhancer or its modules crash your system? Due to the nature of the method, Application Enhancer or its modules potentially can crash individual applications if there is a bug in the module or in the application being modified (sometimes APE modules expose "hidden" bugs in the applications).
If you suspect Application Enhancer or its modules cause crashes, you can always temporarily disable the Application Enhancer system.
There are a number of technologies incorporated into our products that attempt to make sure your applications are safe: Haxie CrashGuard makes sure the application is not modified if it has recently crashed;
APE Check makes sure no damaged APE modules are loaded; moreover, all of our products are going through a tedious beta testing process to make sure it runs as expected.
However, even if an individual application crashes, this cannot bring down the whole system due to the fact it has the protected memory and the Application Enhancer operates in user memory space, which means it cannot affect the system itself or processes belonging to other users (in this regard, Kernel Extensions (kext) are much more dangerous as they operate on the lowest possible level and have access to all memory and processes; because of that, Kernel Extensions can cause "kernel panics", while Application Enhancer cannot, as they dont have access to the kernel memory space).
Does Application Enhancer slow down the system? Due to the fact that more code has to be loaded at the application launch time, Application Enhancer can increase the application launch time (usually in the range of 40-60 ms per Application Enhancer module loaded on a modern Mac).
Once loaded, most Application Enhancer modules stay latent and will not hog your processor. We are constantly working on improving the situation, so please make sure you always run the latest versions of our products.
The technology behind Application Enhancer system has been in research and development for more than 2 years now, and many of our products are using it.
Main features:
- Provides capabilities to use Application Enhancer modules.
- Completely free of charge.
Enhancements:
- .Fixed a bug with corrupt Application Enhancers directory causing Application Enhancers preference pane to fail to load.
- Did some optimizations for the Mac OS X 10.4.9 update.

DOM Framework is a Cocoa framework for manipulating XML-data in applications, similar to JDOM and XOM for Java. Also contains an XML parser, a formatter for pretty-printing XML and XPath-support.
Enhancements:
- Huge API-changes. I have rethought some parts of the framework, and changed added, removed and changed names of methods everywhere. Sorry, but it had to be done. Youll get a ton of build errors if you try to recompile with the new version.
- The core of the framework now consist of a set of protocols that define the DOM API, and a corresponding set of classes that implement that API.
- Rewrote the XPath engine, now compiles expressions. Handles most things, but still a bit short on predicates (although only quite complex predicates, or predicates with functions and calculations in them fail).
- New namespace handling, which works.
- New parser/builder architecture.
- New builder built on top of the widely used XML-parser Expat, as well as a simple plug-in architecture for builders. It works much better than the old CoreFoundation builder.
- Support for alternative implementations of the core node classes, and mixing of implementations.
- The outputter can render elements inlined (no newline before or after).
- Added a document fragment class.
- Added some classes for encapsulation traversals of the DOM tree.
- Rewrote the formatter with the new traversal classes.
- New postprocessor API (for handling things like XInclude).