Android - Android ADT (Android Development Tools) in detail

The Android SDK includes several tools and utilities to help you to create, test, and debug your projects. ADT plug-in conveniently incorporates most of those tools into the eclipse IDE, where you can access them from the DDMS (Dalvik Debug Monitoring Service) perspective, including:

  • The Android SDK and Virtual Device Manager : Used to create and manage Android Virtual Devices
    (AVD) and SDK packages. The AVD hosts an emulator running a particular build of Android, letting you specify the supported SDK version, screen resolution, amount of SD card storage available hardware capabilities.
  • The Android Emulator : An implementation of the Android Virtual machine designed to run within a virtual device on your development computer. Use the emulator to test and debug your android applications.
  • Dalvik Debug Monitoring service (DDMS) : Use the DDMS perspective to monitor and control the Dalvik virtual machines on which you are debugging your applications.
  • Android Asset Packaging Tool : Constructs the distributable Android package files  
  • Android Debug Bridge (ADB) : A client - server application that provides a link to a running emulator. It lets you copy files, install compiled application packages (.apk), and run shell commands.
The following additional tools are also available : 

  • SQLite3 : A database tool that you can use to access the SQLite database files created and used by android.
  • Traceview : A graphical analysis tool for viewing the trace logs from your Android application.
  • MkSDCard : Creates an SD card disk image that can be used by the emulator to simulate an external storage card.
  • Dx : Converts java .class bytecode into Android .dex bytecode.
  • activityCreator : A script that builds Ant build files that you can use to compile your Android applications without ADT plug - in.
  • layoutOpt : A tool that analyses your layout resources and suggests improvements and optimization.

Comments

Post a Comment

Popular posts from this blog

EJB - Stateful vs Stateless

For  stateless session beans  the server can maintain a variable amount of instances in a pool. Each time a client requests such a stateless bean (e.g. through a method) a random instance is chosen to serve that request. That means if the client does two subsequent requests it is possible that two different instances of the stateless bean serve the requests. In fact there is no conversational state between the two requests. Also if the client disappears, the stateless bean does not get destroyed and can serve the next request from another client. On the other hand a  stateful session bean  is closely connected to the client. Each instance is created and bounded to a single client and serves only requests from that particular client. So happens that if you do two subsequent requests on a stateful bean, your request will be served always from the same instance of the bean. That means you can maintain a conversational state between the requests. At the end of the li...
Read more

Mirror binay tree - Java

public class TreeNode {     private TreeNode left;     private TreeNode right;     private Object value;     public TreeNode getLeft() {         return left;     }     public TreeNode setLeft(TreeNode left) {         this.left = left;         return this;     }     public TreeNode getRight() {         return right;     }     public TreeNode setRight(TreeNode right) {         this.right = right;         return this;     }     public Object getValue() {         return value;     }     public TreeNode setValue(Object value) {         this.value = value;         return this;     } } public class Mirror {     public stat...
Read more