You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have not measured the performance of the lib, but it shouldn't decrease it.
There are two ways where Philology is called:
1-. From code when you do something like getResources().getString(R.string.label)
2-. Every time you inflate a view, a transformer for that kind of view has been added to Philology and an string resource has been assigned on the xml file
The first case it works only as a proxy: if the value of R.string.label is in Philology use it, in another case delegates it on the Android System. The performance here is almost the same than if you don't use Philology
The second case could spend a bit more, because for every view Philology check if there is a transformer (It is O(1) because the implementation is a HashMap) and on an affirmative case read xml text attribute to use the most updated value of it.
One last point, Philology itself, because of the previous points, doesn't decrease the performance of your apps, but it could impact on performance if the injected dependencies (PhilologyRepositoryFactory, PhilologyRepository, ....) have an expensive runtime implementation
How is the performance of this library? Is it fast? Does it increase screen rendering time?
The text was updated successfully, but these errors were encountered: