TextView textview = (TextView)findViewById(R.id.textView);
button.setOnClickListener(
	new View.OnClickListener() {
		@Override
		public void onClick(View view) {
			textview.setText("Hello Android 426");
		}
});

• What is OnClickListener() -- interface
• Java: Interface with new keyword how is that possible?

  button.setOnClickListener(
  	new View.OnClickListener() {	<===== new() for an interface
  

Create an object but have no need to name the object's class
Generally, they are used whenever you need to override the method of a class or an interface.
Inner class likely either be an abstract class or an interface

Because the inner and outer classes have access to each other's instance variables and methods, this can often serve as if it were a class with two base classes.
Need only one object of a class and the class definition is very short -- Swing

Anonymous Inner Classes Commonly Used in GUI (Swing)	

• 11.4 Enabling View Binding
• A small change to the Gradle Scripts -> build.gradle (Module: AndroidSample.app)

  plugins {
     id 'com.android.application'
  android {
      buildFeatures {
          viewBinding true
      }
  
  

• 11.5 Using View Binding

  import com.example.androidsample.databinding.ActivityMainBinding; <==com.example.THIS_APP_NAME.
  
  private ActivityMainBinding binding;
  
  binding = ActivityMainBinding.inflate(getLayoutInflater());
  
  binding.textView.setText(); <== textView is the id name in XML
  
  TIP: need File->Sync Project With Gradle File
  

the biggest disadvantage of findViewById() being that it is possible to obtain
a reference to a view that has not yet been created within the layout, leading to 
a null pointer exception when an attempt is made to access the view’s properties.

• Google 'android menu tutorial' -- goal of 'learn and create'
• Menus | Android Developers -- useless, API and protocal, no solid example
• Steps to create a Android Menu - Medium -- no good, no complete code
• Android Option Menu Example - javatpoint -- good candidate, a little too much
• Android Options Menu with Examples - Tutlane -- another good candidate MAY have issue 'import android.support.v7.app.AppCompatActivity;'
• Menu in Android | Android Development Tutorial -- very good if RECENT, since a project for download
• Steps to implement Menu in Android - DataFlair -- very good, clean (winner today)
• Android Tutorial => Creating a Menu in an Activity -- not very good NO import
• Android Menus - GeeksforGeeks -- useless, no complete coding
• Android SDK: Implement an Options Menu -- too old

• Recent, on topic
• Complte coding WITH import
• Images are plus

1. res/menu/main_menu.xml

2. onCreateOptionsMenu() in your activity

3. onOptionsItemSelected()	

    < com.google.android.material.floatingactionbutton.FloatingActionButton
        android:id="@+id/fab"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_gravity="bottom|end"
        android:layout_marginEnd="@dimen/fab_margin"
        android:layout_marginBottom="16dp"
        app:srcCompat="@android:drawable/ic_dialog_email" />
		
        binding.fab.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                Snackbar.make(view, "Replace with your own action", Snackbar.LENGTH_LONG)
                        .setAction("Action", null).show();
            }
        });		

<menu xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    tools:context="com.example.a03_basic.MainActivity">
    <item
        android:id="@+id/action_settings"      <== HERE why @+id
        android:orderInCategory="100"
        android:title="@string/action_settings"
        app:showAsAction="never" />

<resources>
    <string name="app_name">A03-Basic
    <string name="action_settings">Settings      <== HERE @+id/action_settings

    <string name="first_fragment_label">First Fragment
    <string name="second_fragment_label">Second Fragment
    <string name="next">Next
    <string name="previous">Previous

    <string name="hello_first_fragment">Hello first fragment
    <string name="hello_second_fragment">Hello second fragment. Arg: %1$s

There are literally decades of lessons learned by programmers the hard way that all 
boil down to the maxim “abstract literal strings out of your code – you will thank me later.”

Define string/color/dimension/theme/ ... values descriptively in separate res/values/.xml	

@IBOutlet weak var lable: UILabel!

@IBAction func button(_ sender: Any) {
	lable.text = "Hello ios 426"
}