Hackathon Azerbaijan Android API Overview and Repository

Hackathon Azerbaijan Android API Overview and Repository

• 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 APIs http://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 • AndroidDeveloper's Guide http://developer.android.com/guide/index.html • Official reference http://developer.android.com/reference/packag es.html • Android training from Google • https://developer.android.com/training/index. html
• 7.
  Android Books • ProAndroid 2/3 • Amazon.com Android search =~ 3000 book
• 8.
  Code Repository • Eachuser 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 peer's 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.
  BitBucket BitBucket 101 • http://confluence.atlassian.com/display/BITB UCKET/bitbucket+101 • Git installation • Configuration • BitBucket account • BitBucket Dashboard
• 15.
  Questions?
• 16.
  Contact me http://raminorucov.wordpress.com http://www.facebook.com/ramin.orucov http://www.linkedin.com/in/raminorujov http://twitter.com/RaminOrujov