Reflective Drawable Loader
Reflective Drawable Loader APK
0.0.3 ․ 8 years agoFree ․ Alexandros Schillings ⇣ Download APK (407.18 KB)
Sample project demonstrating the use of the Reflective Drawable Loader Library
What's Reflective Drawable Loader APK?
Reflective Drawable Loader is a app for Android, It's developed by Alexandros Schillings author.
First released on google play in 10 years ago and latest version released in 8 years ago.
This app has 498 download times on Google play and rated as 3.90 stars with 10 rated times.
This product is an app in Tools category. More infomartion of Reflective Drawable Loader on google play
This is a sample project demonstrating the use of the Reflective Drawable Loader Library.
The library (and code) can be found here: https://github.com/alt236/Reflective-Drawable-Loader---Android
Project Description
---
Were you ever in a situation where you had to access Drawables based on their names (for example if the Drawable names are stored in a DB) and you had to write long lookup tables converting the names into R.drawable.ids? And maintaining them?
This library is offering a way around it by using reflection to access the Drawable directly by name. You only need to include them as normal into your Res folder tree. It has been benchmarked at up to 5x faster than the platform's Resources.getIdentifier() method.
It is using LRU caching to mitigate the reflection time overhead for both reflection "hits" and "misses".
The library (and code) can be found here: https://github.com/alt236/Reflective-Drawable-Loader---Android
Project Description
---
Were you ever in a situation where you had to access Drawables based on their names (for example if the Drawable names are stored in a DB) and you had to write long lookup tables converting the names into R.drawable.ids? And maintaining them?
This library is offering a way around it by using reflection to access the Drawable directly by name. You only need to include them as normal into your Res folder tree. It has been benchmarked at up to 5x faster than the platform's Resources.getIdentifier() method.
It is using LRU caching to mitigate the reflection time overhead for both reflection "hits" and "misses".
