Hackathon Azerbaijan Android API Overview and Repository

  • 854 views
Uploaded on

First training for Hackathon Azerbaijan Android Age participants.

First training for Hackathon Azerbaijan Android Age participants.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
854
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Android API Overview and Repository Ramin Orujov 08.01.2012
  • 2. Agenda• Android API overview• Android resources• Code repository• VCS and DVCS• Git intro• BitBucket account
  • 3. Android API Overview• Based on Core Java APIs.• Additional Android specific APIshttp://developer.android.com/reference/packag es.html
  • 4. Android Main Packages• Widget – UI components• Telephony – cell network, call, GSM, CDMA• Media – audio, video• Location – LBS, GPS• Content – content providers• Database – SQLLite• XML – SAX, pull parser
  • 5. Android Main Packages• Hardware – camera, sensor, usb• OS – system services, IPC, messaging• Net – internet, HTTP, RTP, SIP, WiFi• Bluetooth• Speech – text to speech, SIRI • NFC – Near Field Communication• Test – Android testing
  • 6. Android resources• Android Developers Guidehttp://developer.android.com/guide/index.html• Official referencehttp://developer.android.com/reference/packag es.html• Android training from Google• https://developer.android.com/training/index. html
  • 7. Android Books• Pro Android 2/3• Amazon.com Android search =~ 3000 book
  • 8. Code Repository• Each user will have BitBucket account and private repository.• Repository is based on GIT DVCS.• GIT training will be provided on 1st training.• Jury team will monitor code commits.
  • 9. VCS• VCS – Version Control System• http://en.wikipedia.org/wiki/Revision_control• Centralized – CVS, Subversion(SVN), MS Visual SourceSave, Perforce, etc.• Distributed – Git – Mercurial – Bazaar
  • 10. DVCS• Peer-to-peer approach, as opposed to the client- server approach of centralized systems. Each peers working copy of the codebase is a bona- fide repository.• Distributed revision control conducts synchronization by exchanging patches (change-sets) from peer to peer.• No canonical, reference copy of the codebase exists by default; only working copies.
  • 11. DVCS• Common operations (such as commits, viewing history, and reverting changes) are fast, because there is no need to communicate with a central server.• Communication is only necessary when pushing or pulling changes to or from other peers.• Each working copy effectively functions as a remote backup of the codebase and of its change-history, providing natural protection against data loss
  • 12. Git• Git (/ɡɪt/) is a distributed revision control system with an emphasis on speed.• Git was initially designed and developed by Linus Torvalds for Linux kernel development.• Every Git working directory is a full- fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server.• Git is free software distributed under the terms GPL version 2.
  • 13. Git• http://git-scm.com/documentation• http://schacon.github.com/git/gittutorial.html• http://progit.org/book/• http://code.google.com/p/msysgit
  • 14. BitBucketBitBucket 101• http://confluence.atlassian.com/display/BITB UCKET/bitbucket+101• Git installation• Configuration• BitBucket account• BitBucket Dashboard
  • 15. Questions?
  • 16. Contact mehttp://raminorucov.wordpress.comhttp://www.facebook.com/ramin.orucovhttp://www.linkedin.com/in/raminorujovhttp://twitter.com/RaminOrujov