Android笔记

Eclipse 【ADT】 源

https://dl-ssl.google.com/android/eclipse

Notice that no matter what scenario causes the activity to stop, the system always calls onPause() before calling onStop().

Although the onPause() method is called before onStop(), you should use onStop() to perform larger, more CPU intensive shut-down operations, such as writing information to a database.

the system calls onStart() both when it creates your activity and when it restarts the activity from the stopped state.

Resumed

In this state, the activity is in the foreground and the user can interact with it. (Also sometimes referred to as the “running” state.)

Paused

In this state, the activity is partially obscured by another activity—the other activity that’s in the foreground is semi-transparent or doesn’t cover the entire screen. The paused activity does not receive user input and cannot execute any code.

Stopped

In this state, the activity is completely hidden and not visible to the user; it is considered to be in the background. While stopped, the activity instance and all its state information such as member variables is retained, but it cannot execute any code.

//保证当前的版本可以执行某段代码

1
2
3
if ( Build.VERSION.SDK_INT >=Build.VERSION_CODES.HONEYCOMB ) {

}
onCreate<—>onDestroy，执行一次；

onStart<—>onStop，循环；

onResume<—>onPause，循环；

In order for the Android system to restore the state of the views in your activity, each view must have a unique ID, supplied by the android:id attribute.

As the system begins to stop your activity, it calls onSaveInstanceState() (1) so you can specify additional state data you’d like to save in case the Activity instance must be recreated. If the activity is destroyed and the same instance must be recreated, the system passes the state data defined at (1) to both the onCreate() method (2) and the onRestoreInstanceState() method (3).

When your activity is recreated after it was previously destroyed, you can recover your saved state from the Bundle that the system passes your activity. Both the onCreate() and onRestoreInstanceState() callback methods receive the same Bundle that containes the instance state information.

Because the onCreate() method is called whether the system is creating a new instance of your activity or recreating a previous one, you must check whether the state Bundle is null before you attempt to read it. If it is null, then the system is creating a new instance of the activity, instead of restoring a previous one that was destroyed.

Instead of restoring the state during onCreate() you may choose to implement onRestoreInstanceState(), which the system calls after the onStart() method. The system calls onRestoreInstanceState() only if there is a saved state to restore, so you do not need to check whether the Bundle is null.

从.java中和从.xml中load resource

// Get a string resource from your app’s Resources

1
String hello =getResources().getString(R.string.hello_world);
// Or supply a string resource to a method that requires a string

1
2
3
TextView textView =newTextView(this);

textView.setText(R.string.hello_world);
1
2
3
4
5
6
7