| /external/webkit/WebCore/manual-tests/inspector/ |
| debugger-scopes-inspection.html | 32 <p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=34161"> Bug 34161 - Local scope is shown as With scope in scope chain pane </a>.</p>
33 <p>To test, open the Inspector and start a debugging session. In a second debugger will pause. While paused look at scope chain pane. There should be three scopes: 'With scope' containing objField variable, 'Local scope' with this and self variables and 'Global scope'. All scopes but 'Global' should be expanced. 'Global' scope should be collapsed(it takes too long to expand DOMWindow so we prefer to do it on demand). </p>
|
| debugger-watch-expressions.html | 16 Scripts panel sidebar pane: "<code>this</code>", "<code>a</code>",
|
| /external/junit/src/junit/swingui/ |
| TestRunView.java | 30 public void addTab(JTabbedPane pane);
|
| TestHierarchyRunView.java | 36 public void addTab(JTabbedPane pane) {
38 pane.addTab("Test Hierarchy", treeIcon, fTreeBrowser, "The test hierarchy");
|
| FailureRunView.java | 103 public void addTab(JTabbedPane pane) {
106 pane.addTab("Failures", errorIcon, scrollPane, "The list of failed tests");
|
| TestRunner.java | 95 private Vector fTestRunViews= new Vector(); // view associated with tab in tabbed pane
391 JTabbedPane pane= new JTabbedPane(SwingConstants.BOTTOM); local
395 lv.addTab(pane);
399 tv.addTab(pane);
401 pane.addChangeListener(
408 return pane;
|
| /external/webkit/WebCore/inspector/front-end/ |
| audits.css | 70 #audit-result-view > .pane img.score {
79 #audit-result-view > .pane img.score.red {
83 #audit-result-view > .pane img.score.green {
87 #audit-result-view > .pane.expanded:nth-last-of-type(1) {
91 #audit-result-view .pane.expanded:nth-last-of-type(1) {
95 #audit-result-view > .pane > .body > .pane > .title {
101 #audit-result-view > .pane > .body > .pane > .body {
105 #audit-result-view > .pane > .body > .pane .section
[all...] |
| ScopeChainSidebarPane.js | 82 section.pane = this;
104 if (this.hasChildren && this.propertyIdentifier in this.treeOutline.section.pane._expandedProperties)
110 this.treeOutline.section.pane._expandedProperties[this.propertyIdentifier] = true;
115 delete this.treeOutline.section.pane._expandedProperties[this.propertyIdentifier];
|
| StylesSidebarPane.js | 303 section.pane = this;
355 blankSection.pane = this;
693 self.pane.update();
700 InjectedScriptAccess.get(this.rule.injectedScriptId).applyStyleRuleText(this.rule.id, newContent, this.pane.node.id, callback);
754 InjectedScriptAccess.get(this.pane.node.injectedScriptId).addStyleSelector(newContent, this.pane.node.id, callback);
759 this.pane.removeSection(this);
[all...] |
| SidebarPane.js | 32 this.element.className = "pane";
|
| inspector.css | [all...] |
| EventListenersSidebarPane.js | 33 this.bodyElement.addStyleClass("events-pane");
|
| /frameworks/base/docs/html/guide/developing/testing/ |
| testing_eclipse.jd | 187 Your new class appears in a new Java editor pane.
281 In the left-hand pane, find the Android JUnit Test entry. In the right-hand pane, click the
301 In the Emulator Launch Parameters pane, set the Android emulator flags you want to
309 Click the Common tab. In the Save As pane, click Local to save this run configuration
314 menu: in the Display in Favorites pane click the checkbox next to Run.
471 The test results appear in the JUnit view. This is divided into an upper summary pane,
472 and a lower stack trace pane.
475 The upper pane contains test information. In the pane's header, you see the followin
[all...] |
| /frameworks/base/docs/html/guide/developing/tools/ |
| draw9patch.jd | 24 <p>The left pane is your drawing area, in which you can edit the lines for the
26 pane is the preview area, where you can preview your graphic when stretched.</p>
|
| ddms.jd | 48 <h2 id="left-pane">Left Pane</h2>
73 <h2 id="right-pane">Right pane</h2>
126 With a VM selected in the left pane, click <strong>Start Tracking</strong>, then
|
| traceview.jd | 126 <p>The image below shows the profile pane. The profile pane shows a
|
| /frameworks/base/docs/html/sdk/ |
| win-usb.jd | 224 <li>Select <strong>Devices</strong> in the left pane.</li>
225 <li>Locate and expand <em>Other device</em> in the right pane.</li>
243 <li>Select <strong>Device Manager</strong> in the left pane of the Computer Management
245 <li>Locate and expand <em>Android Phone</em> in the right pane.</li>
288 <li>Select <strong>Device Manager</strong> in the left pane.</li>
289 <li>Locate and expand <em>Android Phone</em> in the right pane.</li>
334 <li>Select <strong>Device Manager</strong> in the left pane.</li>
335 <li>Locate and expand <em>ADB Interface</em> in the right pane.</li>
|
| android-3.0-highlights.jd | 136 <p>The Contacts app uses a new two-pane UI and Fast Scroll to let users easily organize and locate contacts. The application offers improved formatting of international phone numbers as user types, based on home country and an international number parsing library. Contact information is presented in a card-like UI, making it easier for users to read and edit contacts.</p>
140 <p>The Email application uses a new two-pane UI to make viewing and organizing messages more efficient. The app lets users select one or more messages, then select an action from the Action Bar, such as moving them to a folder. Users can sync attachments for later viewing and keep track of email using a home screen Widget.</p>
166 <p>Starting with Android 3.0, developers can break the Activities of their applications into subcomponents called Fragments, then combine them in a variety of ways to create a richer, more interactive experience. For example, an application can use a set of Fragments to create a true multipane UI, with the user being able to interact with each pane independently. Fragments can be added, removed, replaced, and animated inside an Activity dynamically, and they are modular and reusable across multiple Activities. Because they are modular, Fragments also offer an efficient way for developers to write applications that can run properly on both larger screen as well as smaller screen devices.</p>
|
| adding-components.jd | 203 left pane. </li>
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/src/com/android/ide/eclipse/ddms/preferences/ |
| LogCatPreferencePage.java | 34 * Preference Pane for LogCat.
|
| /frameworks/base/docs/html/resources/tutorials/testing/ |
| helloandroid_test.jd | 406 an upper pane summarizes the tests that were run and a lower pane reports the failure traces
415 The upper pane summarizes the test:
450 The lower pane contains the failure trace. If all the tests are successful,
451 this pane is empty. If some tests fail, then if you select a failed test in the
452 upper pane, the lower view contains a stack trace for the test.
|
| activity_test.jd | 343 If you see errors listed in the <strong>Problems</strong> pane at the bottom of the Eclipse window, or if a red error marker appears next to
362 Open it, then at the bottom of the center pane click <strong>AndroidManifest.xml</strong>
[all...] |
| /external/proguard/src/proguard/gui/ |
| TabbedPane.java | 66 * Adds a component with a given title to the tabbed pane.
|
| /external/webkit/WebKit/chromium/src/js/ |
| DevTools.js | 376 glassPane.id = "glass-pane-for-drag";
388 var glassPane = document.getElementById("glass-pane-for-drag");
|
| /external/webkit/WebKit/wx/ |
| WebBrowserShell.cpp | 163 // create a status bar just for fun (by default with 1 pane only)
|
