i have been developing much-revamped version of earlier android application. many additions , changes infrastructure, ui, , general organization necessary far easier start scratch new application , transplant of guts old 1 rather trying understand previous developer wrote , incrementally perform smaller surgeries.
i have source code previous developer, , contains several activities, fragments, classes, etc. know not being used in final build. make transplant process easy possible, there easy way find out of above components not being used in app?
a couple ideas come mind are:
- stepping through in debugger , taking note of components used (this seems super inefficient , terribly tedious process)
- add log message each component's oncreate/instantiation code , run through entire app (more efficient, still pain)
is there easy way this?
Comments
Post a Comment