1. The project document so-called list androidmanifest.xml documents. The file, but with great leverage, for example: app name. icons, app-supported version apps, and more. I'll show you the role of each of the parameters in this list file below.
<manifest xmlns:android= "http://schemas.android.com/apk/res/android" namespace package= "Com.example.hello" Package name uniquely identifies an app android:versioncode= "1" version number android:versionname= "1.0" version number name android:icon= "@drawable/ic_ Launcher "app icon.To access the Drawable constants of the R.java file, use the icon's ic_launcher under this constant as the app icons android:label= "@string/app_name" app name < Activity has multiple activity in an application.
An activity represents a form android:name= "com.example.hello.MainActivity" This package Com.example.hello under the Mainactivity Android:label= the title <intent-filter> Intent filter of the "@string/app_name" >activity form specifically matches the intent. Filtering data <action android:name= "Android.intent.action.MAIN"/> Action name <category android:name= " Android.intent.category.LAUNCHER "/> </intent-filter> </activity> android: Minsdkversion= "8" specifies the lowest version number supported by the app android:targetsdkversion= "/>" the highest version number
Display units in 2.android
1..PX (pixels) The general HVGA represents 320*480 pixels. It's a lot more than that.
2..dip or DP (device independent pixels), this is related to device hardware. Generally in order to support WVGA,QVGA and HVGA recommend this, do not rely on pixels
3..SP (scale of pixels) primarily handles font size, based on adaptive system fonts.
In addition to the above 3. There are also several infrequently used. In (feet), mm (mm), pt (point) 1/72 inch
In order to adapt to different resolutions and different pixel densities, it is recommended to use dip. Use the text SP,
Android Learning Path (iv) File Project learning list, Android display unit often used