Android development basics 3-Development notes and references

ArticleDirectory

• Interface tools and Layout
• Code obfuscation
• Real machine debugging
• Software store
• Reference books

Interface tools and layout Interface Design Specifications

Http://developer.android.com/guide/practices/ui_guidelines/index.html

Some man-machine interface guides mentioned are just a few

One interface-based serialization 

Introduction http://azero.tsang.blog.163.com/blog/static/47005201072022410157/

Understanding Android mobile phone http://azero.tsang.blog.163.com/blog/static/47005201072372032555/

Interactive Mode http://azero.tsang.blog.163.com/blog/static/470052010730622032/

You can read the Post published by the blogger later.

Interface Design Tools

Eclipse plug-in

DroiddrawHttp://www.cnblogs.com/wanlipeng/archive/2010/08/18/1802715.html

This tool is better than the Eclipse plug-in, but the Eclipse plug-in version is more comprehensive after you are familiar with the interface.

Interface Layout

Android adaptive screen size and layout (landscape screen | landscape screen) 

Http://huangwuyi.javaeye.com/blog/842766

 

Code Obfuscation

Because Java compiledProgramIt is intermediate code, and tools can be easily decompiled. Therefore, obfuscation is required for programs to increase confidentiality. [actually, the core code with confidentiality can be packaged using ndk because it is a machine code, the difficulty of decompilation is greatly increased]

Proguard usage reference http://www.devdiv.com/thread-41467-1-1.html

Six common JavaSource codeProtection tools (obfuscation, encryption, underlying)

Http://www.cmd100.com/bbs/thread-4471-1-1.html

Real machine debugging

Http://www.cnblogs.com/wanlipeng/archive/2010/08/11/1797202.html

USB debugging settings for Android real machine (for new users)

Http://wenku.baidu.com/view/0e6d5eef5ef7ba0d4a733bfb.html

Http://blog.csdn.net/yihui8/archive/2010/05/26/5625350.aspx

Android simulator debugging and real machine debugging

1. simulator debugging and real machine debugging

1. simulator debugging

Run emulator in the source code or SDK and add Parameters

2. Real machine debugging

1) connect G1 hardware and PC with USB cable

2) if it is a Windows system, install the driver.

3) use the source code or the ADB command in the SDK to check whether the hardware connection is successful.

$ ADB devices normal debugging

4) Note:

A) use the root permission to connect to a real machine in Linux.

B) If you have connected to the simulator before, it is best to kill the ADB background process before connection.

$ Killalladb

3. debugging in eclipse

If the simulator is not enabled, connect to the real machine for debugging.

If the real machine is not connected and the simulator is enabled, debug it in the current simulator.

Enable simulator debugging if you have not connected to the real machine or enabled the simulator.

If multiple real machines or simulators are enabled and multiple connected devices are available at the same time, a list is displayed for users to choose from.

4. Use the ADB tool for debugging in the command line

When connecting multiple devices, use the command line parameter to indicate the device name or device type.

$ ADB-s device name shell device name listed by ADB Devices

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/yihui8/archive/2010/05/26/5625350.aspx

Software store

The reference for releasing completed software to the software store is as follows:

Http://hi.baidu.com/lphack/blog/item/1c8f6f2ae87435e9e7cd407b.html

Http://www.5y44.com/read.php? FID = 2 & tid = 761

Reference books

Android in action is a comprehensive book