Lines Matching full:link
44 as well as {@link android.util.Log} messages you've written from your application. To run
47 <p>{@link android.util.Log} is a logging
50 {@link android.util.Log#v(String,String)} (verbose), {@link
51 android.util.Log#d(String,String)} (debug), {@link android.util.Log#i(String,String)}
52 (information), {@link android.util.Log#w(String,String)} (warning) and {@link
124 {@link android.os.Debug#waitForDebugger()} to your code.</dd>
131 reclaim memory). This is very useful for testing the {@link android.app.Activity#onSaveInstanceState}
132 / {@link android.app.Activity#onCreate(android.os.Bundle)} code path, which would
154 with the Console APIs. The Android Browser (and the {@link android.webkit.WebChromeClient}) supports
176 <p>The Android Browser (and {@link android.webkit.WebChromeClient}) does not implement all of the
188 <p>If you've implemented a custom {@link android.webkit.WebView} in your application, then in order
189 to receive messages that are sent through the Console APIs, you must provide a {@link
190 android.webkit.WebChromeClient} that implements the {@link
192 method. For example, assuming that the {@code myWebView} field references the {@link
201 <p>The {@link android.webkit.WebChromeClient#onConsoleMessage(String,int,String)
203 within your {@link android.webkit.WebView}.</p>
204 <p>When the "Hello World" log is executed through your {@link android.webkit.WebView}, it will
210 <p class="note"><strong>Note:</strong> The {@link
212 method was added with API Level 7. If you are using a custom {@link
252 {@link android.os.Debug#startMethodTracing(String) startMethodTracing()}. See <a
271 <dd>Android provides debug helper classes such as {@link android.util.Log
272 util.Log} and {@link android.os.Debug} for your convenience. </dd>
