Lesson plan

SIMBL

SIMBL (short for SIMple Bundle Loader, formerly Smart InputManager Bundle Loader, and pronounced like symbol or cymbal), is a discontinued application enhancement (InputManager bundle) loader for Mac OS X developed by Mike Solomon. It helps third-party developers modify and add functionality to applications developed with the Cocoa environment without access to the source code. SIMBL loads code via the InputManager system, which was developed to support foreign input methods. Plugins using SIMBL have advantages over normal InputManager modifications such as targeted code loading into specific applications. Designed for Solomon's PithHelmet, SIMBL is now used by other developers. The most popular use of SIMBL is to add functionality to the Apple Safari web browser which did not have an Apple-authorized plugin system until version 5 in 2010. SIMBL was developed in response to the restrictive licensing and costs of Application Enhancer and the drawbacks of loading code blindly through the InputManager mechanism.

Back to article

Article summary

SIMBL (short for SIMple Bundle Loader, formerly Smart InputManager Bundle Loader, and pronounced like symbol or cymbal), is a discontinued application enhancement (InputManager bundle) loader for Mac OS X developed by Mike Solomon. It helps third-party developers modify and add functionality to applications developed with the Cocoa environment without access to the source code. SIMBL loads code via the InputManager system, which was developed to support foreign input methods. Plugins using SIMBL have advantages over normal InputManager modifications such as targeted code loading into specific applications. Designed for Solomon's PithHelmet, SIMBL is now used by other developers. The most popular use of SIMBL is to add functionality to the Apple Safari web browser which did not have an Apple-authorized plugin system until version 5 in 2010. SIMBL was developed in response to the restrictive licensing and costs of Application Enhancer and the drawbacks of loading code blindly through the InputManager mechanism.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.