summaryrefslogtreecommitdiffstats
path: root/docs/html/sdk/installing
diff options
context:
space:
mode:
authorRich Slogar <rslogar@google.com>2015-03-18 15:58:42 -0700
committerRich Slogar <rslogar@google.com>2015-04-29 19:47:25 -0700
commit2a3aa2d343820be9e05101a25b955d525e9bfa54 (patch)
treef020479c9acb88b9327f6f54884d12338692dfbe /docs/html/sdk/installing
parent999b08b74c29937b49c4106a784117eed6168045 (diff)
downloadframeworks_base-2a3aa2d343820be9e05101a25b955d525e9bfa54.zip
frameworks_base-2a3aa2d343820be9e05101a25b955d525e9bfa54.tar.gz
frameworks_base-2a3aa2d343820be9e05101a25b955d525e9bfa54.tar.bz2
docs: studio 1.2 updates
Change-Id: I893af7af0f686d0eeab11f881256c0cf26eb4605
Diffstat (limited to 'docs/html/sdk/installing')
-rw-r--r--docs/html/sdk/installing/studio-tips.jd60
1 files changed, 49 insertions, 11 deletions
diff --git a/docs/html/sdk/installing/studio-tips.jd b/docs/html/sdk/installing/studio-tips.jd
index 69c188c..a40050f 100644
--- a/docs/html/sdk/installing/studio-tips.jd
+++ b/docs/html/sdk/installing/studio-tips.jd
@@ -36,8 +36,8 @@ This section notes a few of the key features to help you work quickly and effici
<h3>Smart Rendering</h3>
<p>With smart rendering, Android Studio displays links for quick fixes to rendering errors.
For example, if you add a button to the layout without specifying the <em>width</em> and
-<em>height</em> atttributes, Android Studio displays the rendering message <em>Automatically
-add all missing attributs</em>. Clicking the message adds the missing attributes to the layout.</p>
+<em>height</em> attributes, Android Studio displays the rendering message <em>Automatically
+add all missing attributes</em>. Clicking the message adds the missing attributes to the layout.</p>
<h3> Bitmap rendering in the debugger</h3>
@@ -82,7 +82,50 @@ window. Clicking <strong>Designer</strong> on the right side of the window revea
with a layout hierarchy and a list of properties for each view in the layout.</p>
-<h2 id="intellij">Working with IntelliJ</h3>
+<h3>Annotations</h3>
+<p>Android Studio provides coding assistance for using annotations from the
+{@link android.support.annotation Support-Annotations} library, part of the
+Support Repository.
+
+Adding a dependency for this library enables you to decorate your code with annotations to help
+catch bugs, such as null pointer exceptions and resource type conflicts. You can also create
+enumerated annotations to, for example, check that a passed parameter value matches a value from
+a defined set of constants. For more information, see
+<a href="{@docRoot}tools/debugging/annotations.html#annotations">Improving Code Inspection with
+Annotations</a>.
+</p>
+
+
+<h3>Java class decompiling</h3>
+<p>Android Studio allows you to look at what’s inside Java libraries when you don’t have access
+to the source code. </p>
+
+<p>The decompiler is built into Android Studio for easy access. To use this feature, right-click
+a class, method, or field from a library for which you do not have source file access and select
+<strong>decompile</strong>.</p> The decompiled source code appears. </p>
+
+<p>To adjust the Java decompiler settings, select
+<strong>File > Settings > Other Settings > Java Decompiler</strong>. </p>
+
+
+<h3>Debugging and performance enhancements</h3>
+<p>Android Studio offers debugging and performance enhancements such as:</p>
+<ul>
+ <li>Auto detect an expanded set of code styles. To modify the current code style, choose
+ <strong>File &gt; Settings &gt; Code Styles</strong>. </li>
+ <li>Support for high density (Retina) displays on Windows and Linux. </li>
+ <li>Scratch files for quick prototyping without creating any project files.
+ <p>Choose <strong>Tools &gt; New Scratch File</strong> to open a scratch file to quickly
+ build and run code prototypes. Together with Android Studio coding assistance, scratch
+ files allow you to quickly run and debug code updates with the support of all file operations.
+ By embedding code created with scripting languages, you can run your code from within the
+ scratch file.</p>
+ </li>
+</ul>
+
+
+
+<h2 id="intellij">Working with IntelliJ-based Coding Practices</h3>
<p>This section list just a few of the code editing
practices you should consider using when creating Android Studio apps. </p>
@@ -114,23 +157,17 @@ individual classes. </p>
you can set a scope to identify all code related to a specific action bar. </p>
-<h3>External annotations</h3>
-<p>Specify annotations within the code or from an external annotation file. The Android Studio
-IDE keeps track of the restrictions and validates compliance, for example setting the data type
-of a string as not null.</p>
-
-
<h3>Injecting languages</h3>
<p>With language injection, the Android Studio IDE allows you to work with islands of different
languages embedded in the source code. This extends the syntax, error highlighting and coding
assistance to the embedded language. This can be especially useful for checking regular expression
-values inline, and validating XML and SQL statments.</p>
+values inline, and validating XML and SQL statements.</p>
<h3>Code folding</h3>
<p>This allows you to selectively hide and display sections of the code for readability. For
example, resource expressions or code for a nested class can be folded or hidden in to one line
-to make the outer class structure easier to read. The inner clas can be later expanded for
+to make the outer class structure easier to read. The inner class can be later expanded for
updates. </p>
@@ -140,6 +177,7 @@ updates. </p>
reference. Pressing {@code F1} with the preview image or icon selected displays resource asset
details, such as the <em>dp</em> settings. </p>
+
<h3>Quick F1 documentation</h3>
<p>You can now inspect theme attributes using <strong>View > Quick Documentation</strong>
(<strong>F1</strong>),