Android中R.id如何从XML获取视图？解析R.id.textview及XML与Activity集成

Hey there! Let's break this down step by step since you're new to Android—this stuff can feel a bit magical at first, but it's actually pretty straightforward once you peek under the hood.

First off, the R class is an automatically generated file created by Android Studio (specifically the Android Asset Packaging Tool, aapt) every time you build your app. It's a final class that acts as a central registry for all your app's resources—think layouts, strings, drawables, and yes, the IDs you assign to UI elements.

Inside R, you'll find nested static classes like R.id, R.layout, R.string, etc. Each of these nested classes holds static integer constants that map to a specific resource. For example, R.id.textview is just a unique integer value that represents that specific TextView's ID in your app.

Let's start with when you define an ID in XML:

<TextView
    android:id="@+id/textview"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content" />

The @+id/textview syntax tells the build tool: "Hey, create a new ID called textview and add it to the R.id class."

When you build your app, aapt scans all your XML files, collects every resource (including these IDs), and generates a R.java file (you can find it in app/build/generated/not_namespaced_r_class_sources/debug/r/[your package name]/R.java if you want to peek). Inside this file, you'll see something like:

public final class R {
    public static final class id {
        public static final int textview = 0x7f080023;
    }
    // Other nested classes for layout, string, etc.
}

That hex number is just a unique integer assigned to your TextView's ID. When you use R.id.textview in code, you're just referencing this integer.

Here's the play-by-play of how your XML layout connects to your Activity:

1. Inflating the layout
   In your MainActivity's onCreate method, you call:

   setContentView(R.layout.activity_main);
   

   R.layout.activity_main is the integer ID for your XML layout file. The Android system uses this ID to locate the XML file, then parses it into a live tree of View objects in memory—so your XML's <TextView> becomes an actual TextView instance in your app's runtime.

2. Finding your TextView
   Once the layout is inflated, you can grab the TextView instance using:

   TextView myTextView = findViewById(R.id.textview);
   

   The findViewById method traverses the entire View tree, looking for the View with a matching integer ID (the one from R.id.textview). When it finds it, it returns the instance, so you can modify it (like calling myTextView.setText("Hello!")).

3. A modern alternative: View Binding
   These days, most developers use View Binding instead of findViewById because it's safer and less error-prone. When you enable View Binding in your build.gradle, Android generates a binding class for each layout (like ActivityMainBinding for activity_main.xml). You can use it like this:

   ActivityMainBinding binding = ActivityMainBinding.inflate(getLayoutInflater());
   setContentView(binding.getRoot());
   // Now you can access your TextView directly
   binding.textview.setText("Hello from View Binding!");
   

   This avoids typos (since the binding class uses the exact ID names from your XML) and eliminates null checks for views that exist in the layout.

内容的提问来源于stack exchange，提问作者judy