Cracking the cocoa nut: user interface programming at runtime
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
This article introduces runtime toolkit overloading, a novel approach to help third-party developers modify the interaction and behavior of existing software applications without access to their underlying source code. We describe the abstractions provided by this approach as well as the mechanisms for implementing them in existing environments. We describe Scotty, a prototype implementation for Mac OS X Cocoa that enables developers to modify existing applications at runtime, and we demonstrate a collection of interaction and functional transformations on existing off-the-shelf applications. We show how Scotty helps a developer make sense of unfamiliar software, even without access to its source code. We further discuss what features of future environments would facilitate this kind of runtime software development.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Triggers and barriers to customizing software
Mackay, W. E. (1991) · Proceedings of the SIGCHI conference on Human factors in computing systems Reaching through technology - CHI '91 · doi:10.1145/108844.108867 · Cited by 364 · cited 1×
“Different approaches have been taken to bridge these gulfs by making software more flexible, including giving users more control over their software’s configuration [16], runtime behaviors [18, 8] and interfaces [21, 9], or by giving programmers more control over their language [15].”
MethodSelf-citationSikuli: using GUI screenshots for search and automation
Yeh, T., Chang, T.-H., & Miller, R. C. (2009) · Proceedings of the 22nd annual ACM symposium on User interface software and technology · doi:10.1145/1622176.1622213 · Cited by 346
Cited by
Interaction Proxies for Runtime Repair and Enhancement of Mobile Application Accessibility
Zhang, X., Ross, A. S., Caspi, A., Fogarty, J., & Wobbrock, J. O. (2017) · Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3025453.3025846 · Cited by 59
“More recently, Scotty examined runtime toolkit overloading, developing abstractions for implementing modifications in code injected directly into the interface runtime [20].”
BackgroundMethodUnderstanding the Usages, Lifecycle, and Opportunities of Screen Readers’ Plugins
Momotaz, F., Ehtesham-Ul-Haque, M., & Billah, S. M. (2023) · ACM Transactions on Accessible Computing · doi:10.1145/3582697 · Cited by 13
“Many applications support some degree of extensibility by the end-users through scripting, plugins, or extensions [28].”
Background
Metadata
- Authors
- Eagan, J. R., Beaudouin-Lafon, M., & Mackay, W. E.
- Venue
- Proceedings of the 24th annual ACM symposium on User interface software and technology
- Publisher
- ACM
- Published
- 2011-10-16
- Pages
- 225-234
- OpenAlex
- W2083298807
- Cited by
- 50
- References
- 2
- FWCI
- 3.52
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Cracking the cocoa nut: user interface programming at runtime. https://app.cochat.ai/papers/10.1145/2047196.2047226
- The paper
- Eagan, J. R., Beaudouin-Lafon, M., & Mackay, W. E. (2011). Cracking the cocoa nut: user interface programming at runtime. Proceedings of the 24th annual ACM symposium on User interface software and technology. https://doi.org/10.1145/2047196.2047226
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.