You
seem to think that because Android is made a certain way, it has to
be efficient. That is really stupid. Do you want to say that the
Libre3 app is smaller and faster than Juggluco?
I never said such a thing, I analyzed the code on how the resources actually worked, thats all. I don't have a problem with that you don't try to do everything in the most Java and Android way possible...
I never said I think Android is efficient. My point would have been that we're looking in the territory of micro-optimizations that end up making little improvements in the grand scheme of things, but are overall reducing the readability and maintainability of our code. Finding a good middle way and not reinventing every wheel is, to me, a basic tenet of application development that isn't stuck in the 80s.
That said, I think Juggluco is in the current form SUPER efficient with resources. That is absolutely commendable and awesome. I don't want to ruin that at all.
And for the record, I think the Libre 3 original app is absolutely terrible when it comes to memory usage as it has a some sort of memory leak (not in the literal sense, it accumulates data) that will, over time, make it become larger and larger, and also slower and slower. It uses like 400 mb for me now (according to Android settings, that likely doesn't include shared memory usage)
This is in the end a medical application that many people are trying to rely on and some here have already been burned by the opaque situation that, for example, broke itself with updates and are now ending up to stop updating ever again. And it's supposed to be their own fault for using "hacked apks" (I don't think anyone did that) or having a "corner case". I think that's somewhat... irresponsible. Maybe it would be better to have a big disclaimer on the page. That this is essentially beta software that tries to reverse engineer and reimplement a closed, proprietary system and that there may be errors.
I am not trying to find fault, I am trying to make the situation better for everyone and I am willing to put some work into cooperating on that. I made an app that uses the glucodata broadcast to show it on the always-on-display, and I am leaving my pants down figuratively on this: sinni800/glucodata-aod - glucodata-aod - mgs git (metalgearsonic.de). The code is probably pretty bad (primarily the GUI code), but it was the first thing I made in Android Studio.
Regarding the translation: Since the types are hidden in the headers, there was really no way I could have knowm how many bytes are reserved for each of those, its would be a good idea to document these byte length limitations on the site, I think.
Zitat
these structures already sit in installed programs
This is honestly why GNU gettext was made, to access translation strings. This is a micro-optimization that is now locking out less fortunate languages like German because of our word length.
"Benachrichtigung" has a shorter, good word for German: "Mitteilung", which is only 11 characters including null termination.