http://goo.gl/UDei
Activities
1. Setting Up the Development Environment
1.1 Download/Install the SDK
1.2 Download/Install the Eclipse Plugin
1.3 Download/Install the SDK Platform Components
2. Create "Hello World" Application
2.1 Create a new Android Project
3. Take a Tour of the Application
3. Take a Tour of the Application
4. Run "Hello World" on the Emulator
4.1 On the Emulator
4.2 On a Physical Device
4.2 On a Physical Device
- Project Modifications
- From the Package Explorer double-click the file AndroidManifest.xml.
- Select the tab labeled AndroidManifest.xml along the bottom.
- Add android:debuggable="true" to the inside of the opening <application> tag.
- Save the file and close it.
- Phone Modifications
- Turn the phone on.
- Navigate to the Home screen.
- Press MENU (the physical button on the device).
- Select Settings -> Applications -> Development.
- Enable the USB debugging"option.
5. Simple Activity Classes
There are four major types of component classes in any Android application:
- Activities: Much like a Form for a web page, activities display a user interface for the purpose of performing a single task. An example of an Activity class would be one which displays a Login Screen to the user.
- Services: These differ from Activities in that they have no user interface. Services run in the background to perform some sort of task. An example of a Service class would be one which fetches your email from a web server.
- Broadcast Receivers: The sole purpose of components of this type is to receive and react to broadcast announcements which are either initiated by system code or other applications. If you've ever done any work with Java Swing, you can think of these like Event Handlers. For example, a broadcast announcement may be made to signal that a WiFi connection has been established. A Broadcast Receiver for an email application listening for that broadcast may then trigger a Service to fetch your email.
- Content Providers: Components of this type function to provide data from their application to other applications. Components of this type would allow an email application to use the phone's existing contact list application for looking up and retrieving email address.
Lectures
- Activities: Much like a Form for a web page, activities display a user interface for the purpose of performing a single task. An example of an Activity class would be one which displays a Login Screen to the user.
- Services: These differ from Activities in that they have no user interface. Services run in the background to perform some sort of task. An example of a Service class would be one which fetches your email from a web server.
- Broadcast Receivers: The sole purpose of components of this type is to receive and react to broadcast announcements which are either initiated by system code or other applications. If you've ever done any work with Java Swing, you can think of these like Event Handlers. For example, a broadcast announcement may be made to signal that a WiFi connection has been established. A Broadcast Receiver for an email application listening for that broadcast may then trigger a Service to fetch your email.
- Content Providers: Components of this type function to provide data from their application to other applications. Components of this type would allow an email application to use the phone's existing contact list application for looking up and retrieving email address.
Lectures
|
/* by 구글 Google Code University */
이 웹사이트는 CS 학생과 교사가 현재의 컴퓨팅 기술 및 패러다임에 대해 자세히 알아볼 수 있도록 자습서 및 과정 콘텐츠 샘플을 제공합니다. 특히 이 콘텐츠는 Creative Commons 라이센스가 있으므로 CS 교사들이 교육 현장에서 쉽게 사용할 수 있습니다.
과정 섹션에는 다음과 같은 다양한 주제 영역에 대한 자습서, 강의 슬라이드 및 문제 집합이 들어 있습니다.
- AJAX 프로그래밍
- 알고리즘
- 분산 시스템
- 웹 보안
- 언어
도구 101 섹션에서는 버전 제어 시스템 및 데이터베이스와 같이 컴퓨터 공학에서 사용되는 몇 가지 일반적인 도구에 대한 소개를 볼 수 있습니다.
CS 커리큘럼 검색은 전 세계 CS 학과의 교직원들이 웹에 게시한 교육 자료를 찾는 데 도움이 됩니다. 과정에 대해 강의, 과제물 또는 참고 자료만을 표시하도록 검색 범위를 제한할 수 있습니다.
'0.일반개발' 카테고리의 다른 글
2010년 차세대 웹 세미나/컨퍼런스 이벤트 (0) | 2010.09.30 |
---|---|
JSConf.eu 2010 (0) | 2010.09.30 |
Using Modifiers -- Rokon Game Engine (1) | 2010.09.29 |
Using Touch Input -- Rokon Game Engine (0) | 2010.09.29 |
Using Sprites -- Rokon Game Engine (0) | 2010.09.29 |