From: Henri Sara Date: Wed, 14 Dec 2016 07:27:37 +0000 (+0200) Subject: Remove references to Firebug and the firebug chapter from the documentation (#7977) X-Git-Tag: 8.0.0.alpha10~33 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=731a4f42977e98f10ba76df05d33a1f2cda20e59;p=vaadin-framework.git Remove references to Firebug and the firebug chapter from the documentation (#7977) --- diff --git a/documentation/advanced/advanced-debug.asciidoc b/documentation/advanced/advanced-debug.asciidoc index 3bbd6eb931..3ff5a55ab4 100644 --- a/documentation/advanced/advanced-debug.asciidoc +++ b/documentation/advanced/advanced-debug.asciidoc @@ -69,7 +69,7 @@ corners. The [guibutton]#Minimize# button minimizes the debug window in the corner of the browser window, and the [guibutton]#Close# button closes it. If you use the Firebug plugin for Firefox or the Developer Tools console in -Chrome, the log messages will also be printed to the Firebug console. In such a +Chrome, the log messages will also be printed to the inspector console. In such a case, you may want to enable client-side debugging without showing the Debug Window with " ?debug=quiet" in the URL. In the quiet debug mode, log messages will only be printed to the console of the browser debugger. @@ -141,9 +141,8 @@ The [guibutton]#Select a component in the page to inspect it# button lets you select a component in the UI by clicking it and display its client-side properties. -To view the HTML structure and CSS styles in more detail, you can use Firebug in -Firefox, or the Developer Tools in Chrome, as described in -<>. Firefox also has a built-in feature for inspecting HTML and CSS. +To view the HTML structure and CSS styles in more detail, you can use Inspector in +Firefox or the Developer Tools in Chrome. [[advanced.debug.hierarchy.analyze]] diff --git a/documentation/installing/chapter-installing.asciidoc b/documentation/installing/chapter-installing.asciidoc index 7e987bcea8..c8f5e25a76 100644 --- a/documentation/installing/chapter-installing.asciidoc +++ b/documentation/installing/chapter-installing.asciidoc @@ -16,5 +16,3 @@ include::installing-eclipse.adoc[leveloffset=+2] include::installing-netbeans.asciidoc[leveloffset=+2] include::installing-idea.asciidoc[leveloffset=+2] - -include::installing-other.adoc[leveloffset=+2] diff --git a/documentation/installing/img/firebug.png b/documentation/installing/img/firebug.png deleted file mode 100644 index 81512b615d..0000000000 Binary files a/documentation/installing/img/firebug.png and /dev/null differ diff --git a/documentation/installing/installing-other.adoc b/documentation/installing/installing-other.adoc deleted file mode 100644 index d223841a30..0000000000 --- a/documentation/installing/installing-other.adoc +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Installing Other Tools -order: 200 -layout: page ---- - -= Installing Other Tools - -We recommend using a browser with either integrated or external development tools. - -At least Mozilla Firefox and Google Chrome have an integrated web inspector, which supports inspecting the DOM structure of a web page, as well as CSS styles and debug JavaScript execution. - -[[installing.other.firefox]] -== Firefox and Firebug - -While Firefox has an integrated web inspector, the Firebug inspector has some additional features. - -[[installing.other.firefox.firebug]] -=== Using Firebug with Vaadin - -After installing Firefox, use it to open -link:http://www.getfirebug.com/[http://www.getfirebug.com/]. Follow the -instructions on the site to install the latest stable version of Firebug -available for the browser. You may need to allow Firefox to install the plugin -by clicking the yellow warning bar at the top of the browser window. - -After Firebug is installed, it can be enabled at any time from the Firefox -toolbar. <> shows Firebug in action. - -[[figure.firebug.calc]] -.Firebug debugger for Firefox -image::img/firebug.png[width=100%, scaledwidth=100%] - -The most important feature in Firebug is inspecting HTML elements. Right-click -on an element and select [guilabel]#Inspect Element with Firebug# to inspect it. -In addition to HTML tree, it also shows the CSS rules matching the element, -which you can use for building themes. You can even edit the CSS styles live, to -experiment with styling. diff --git a/documentation/installing/installing-toolchain.adoc b/documentation/installing/installing-toolchain.adoc index fad7a57db2..802c15ad96 100644 --- a/documentation/installing/installing-toolchain.adoc +++ b/documentation/installing/installing-toolchain.adoc @@ -17,7 +17,6 @@ In this example, we use the following toolchain: * link:http://www.eclipse.org/downloads/[Eclipse IDE for Java EE Developers] * link:http://tomcat.apache.org/[Apache Tomcat 8.0 (Core)] * link:http://www.getfirefox.com/[Mozilla Firefox] browser -* link:http://www.getfirebug.com/[Firebug] debug tool (optional) * link:http://vaadin.com/download/[Vaadin Framework] The above reference toolchain is a good choice of tools, but you can use almost