02-Sep-2010

Framework and system daemon for adding functionality to apps and Mac OS X.

The Application Enhancer system allows you to enhance or redefine certain behaviors for applications running on your system.It provides a way for third-party enhancer modules to modify how your applications work.Application Enhancers cannot affect the core system - they operate on an application level, therefore, they cannot cause a whole Mac OS X system to crash.

The technology behind Application Enhancer system has been in research and development for more than 4 years now, and many of our haxies (includingWindowShade X, more...

What's New

Version 2.6.1:

You may have to restart after installing.

SDK Specific: Adjusts how kAPEMatchFlavorKey is interpreted. If an application is 64-bit (Adobe CS5), kAPEMatchFlavorCocoa will be used. If an application has LSRequiresCarbon or LSPrefersCarbon set (iTunes 10), it will be treated as if kAPEMatchFlavorCarbon is more...

Details

The Application Enhancer system allows you to enhance or redefine certain behaviors for applications running on your system.It provides a way for third-party enhancer modules to modify how your applications work.Application Enhancers cannot affect the core system - they operate on an application level, therefore, they cannot cause a whole Mac OS X system to crash.

The technology behind Application Enhancer system has been in research and development for more than 4 years now, and many of our haxies (includingWindowShade X, FruitMenu, Silk and others) are using it.

Features:

Provides capabilities to use Application Enhancer modules.

Completely free of charge.

Version 2.6.1:

You may have to restart after installing.

SDK Specific: Adjusts how kAPEMatchFlavorKey is interpreted. If an application is 64-bit (Adobe CS5), kAPEMatchFlavorCocoa will be used. If an application has LSRequiresCarbon or LSPrefersCarbon set (iTunes 10), it will be treated as if kAPEMatchFlavorCarbon is set.

APE Modules should never rely on the value of kAPEMatchFlavorKey as it often lies. Use dynamic runtime inspection instead.

This should address WSX 5.0.x not working in some applications until WSX can be properly updated.