Desktop shortcuts for Android Desktop component development (1)

Home is the first application to interact with users after the Android device is enabled. Home will always run on the background when other applications are running on the foreground.

On an Android device with a screen resolution of 320*480 pixels, the desktop consists of 3 Fast 320 * PX areas when the screen is portrait, each area is divided into 16 80*100 pixel cells. The horizontal screen consists of three 424 * 296px cells, each screen is divided into 16 cells, but each cell is 106 * 74px. (The android2.2 system has now reached five screens ).

See the figure for specific dimensions:

Three types of components can be added to the launcher desktop: shortcuts, real-time folders, and desktop components. The Desktop shortcuts and real-time folders occupy the size of one cell in the desktop area, the desktop widget occupies one or more cells according to the functional requirements.

There are two ways to create shortcuts: 1. Build an intent in the application, and then notify launcher to create a shortcut in the form of broadcast; 2. register an intentfilter that meets specific conditions for the application's components, and then add a shortcut to start the component on the launcher's desktop.

Let's look at the code for adding shortcuts (first ):

Mainactivity Code: (layout Code omitted)

Code:

1. Package com. myshortcut;
3. Import Android. App. activity;
4. Import Android. content. intent;
5. Import android.net. Uri;
6. Import Android. OS. Bundle;
7. Import Android. OS. parcelable;
8. Import Android. View. view;
9. Import Android. View. View. onclicklistener;
10. Import Android. widget. Button;
11. /*
12. * Desktop components-> shortcuts-> Add shortcuts to applications
13. */
14. Public class hellosponcut extends activity implements onclicklistener
15. {
16. Private button bt_fire = NULL;
17. Private button bt_police = NULL;
18. Private intent directCall = NULL;
19. Private final string action_add_shortcut = "com. Android. launcher. Action. install_shortcut ";
22. /** Called when the activity is first created .*/
23. @ Override
24. Public void oncreate (bundle savedinstancestate)
25. {
26. Super. oncreate (savedinstancestate );
27. Setcontentview (R. layout. Main );
29. Bt_fire = (button) findviewbyid (R. Id. bt_fire );
30. Bt_police = (button) findviewbyid (R. Id. bt_police );
32. Bt_fire.setonclicklistener (this );
33. Bt_effece.setonclicklistener (this );
35. DirectCall = new intent (intent. action_call );
36. }
39. @ Override
40. Public void onclick (view V)
41. {
42. // Todo auto-generated method stub
43. Intent addshortcut = new intent (action_add_shortcut );
44. String nametodial = NULL;
45. Parcelable icon = NULL;
47. Switch (V. GETID ())
48. {
49. Case R. Id. bt_fire:
50. Nametodial = "119 ";
51. Icon = intent. Reset cuticonresource. fromcontext (this,
52. R. drawable. Fire );
53. Break;
54. Case R. Id. bt_police:
55. Nametodial = "110 ";
56. /*
57. * When cuticonresource is intent
58. * An internal class is used to construct shortcuts, while intent implements the parcelable interface, so intent objects and
59. * All cuticonresource objects can use putextra (string, parcelable) to input information
60. * Add intent information to broadcast.
61. */
62. Icon = intent. Reset cuticonresource. fromcontext (this,
63. R. drawable. Police );
64. Break;
65. Default:
66. Break;
67. }
69. Addshortcut. putextra (intent. extra_shortcut_name, nametodial );
70. Addshortcut. putextra (intent. extra_shortcut_icon_resource, icon );
71. DirectCall. setdata (URI. parse ("Tel:" + nametodial ));
72. Addshortcut. putextra (intent. extra_shortcut_intent, directCall );
74. This. sendbroadcast (addshortcut );
75. }
76. }

Running result:

1,

2. (toast is provided by the system)

3. (After successful addition)

4. (To delete the shortcut icon, please press the icon long and drag it to the "drawer" area below to change the "drawer" to the "bin" icon)

Reference books: go deep into googleandroid