Lesson plan
Scripting Layer for Android
The Scripting Layer for Android (abridged as SL4A, and previously named Android Scripting Environment or ASE) is a discontinued library that allows the creation and running of scripts written in various scripting languages directly on Android devices. SL4A was designed for developers with its main branch no longer being under active development. These scripts have access to many of the APIs available to normal Java Android applications, but with a simplified interface. Scripts can be run interactively in a terminal, or in the background using the Android services architecture. Currently supported languages are: * Python using CPython * Perl * Ruby using JRuby * Lua * BeanShell * JavaScript using Rhino * Tcl * Rexx using BRexx SL4A was first announced by Google in June 2009, and was originally named "Android Scripting Environment" (ASE). It was, however, not an official Google product, even though many of its developers have worked for Google. It was originally developed by Damon Kohler, and had grown through the contributions of many developers.
Article summary
The Scripting Layer for Android (abridged as SL4A, and previously named Android Scripting Environment or ASE) is a discontinued library that allows the creation and running of scripts written in various scripting languages directly on Android devices. SL4A was designed for developers with its main branch no longer being under active development. These scripts have access to many of the APIs available to normal Java Android applications, but with a simplified interface. Scripts can be run interactively in a terminal, or in the background using the Android services architecture. Currently supported languages are: * Python using CPython * Perl * Ruby using JRuby * Lua * BeanShell * JavaScript using Rhino * Tcl * Rexx using BRexx SL4A was first announced by Google in June 2009, and was originally named "Android Scripting Environment" (ASE). It was, however, not an official Google product, even though many of its developers have worked for Google. It was originally developed by Damon Kohler, and had grown through the contributions of many developers.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- 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.