Confused about thie differences between this and SL4A
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 920
- PR merge metrics
- No merged PRs in 30d
Description
So it looks like the scripting layer for android accomplishes a lot of the same goals as the termux-api package. I'm not sure how usable SL4A actually is, although it does seem to be a part of a number of different services like tasker and qpython.
I looked to see if the termux-api was using SL4A, or what the differences are, and I couldn't find any relevant discussion.
Does it make sense to use SL4A with termux? Is there any change of a plugin happening to make that easier to do?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the linked SL4A project with termux-api and reviewing the existing discussion about how they differ. Clarify whether Termux integration or a plugin is actually wanted; the issue does not identify a file, test, entry point, or concrete completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- cli, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100