Status Update
Comments
em...@google.com <em...@google.com> #2
I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.
@jvg, can you elaborate?
er...@google.com <er...@google.com>
aa...@google.com <aa...@google.com> #3
people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference
aa...@google.com <aa...@google.com>
an...@google.com <an...@google.com> #4
How about something like this?
I think having defined members be directly under the class node while references are nested in a group makes more sense.
Also note that the method refs have a
Description
See the video:https://screencast.googleplex.com/cast/NDY2NDcyOTkzMzk3MTQ1NnxlZDljZWQyNC0zNA
When wrapping is enabled, Logcat in Android Studio behaves weird, adds lots of empty lines. The logs (copy/pasted from
adb logcat
) are like this:And the giant space happens at the
09-24 14:39:47.570 3272 3331 E AppName : The Vulkan spec states:
line.System information: