Add new SWT FAQ pages and some cleanup

* Cleanup fenced code blocks
* Some small markdown cleanup

Author: tivervac

docs/FAQ/FAQ_Can_I_use_SWT_outside_Eclipse_for_my_own_project.md

@@ -1,23 +1,21 @@
 
-
 FAQ Can I use SWT outside Eclipse for my own project?
 =====================================================
 
 This can be interpreted as either a legal question or a technical question. You can find an official answer to the legal question on the SWT FAQ hosted on the SWT development team home page at eclipse.org. The answer to the technical question is an unqualified yes! However, because SWT has a native component, the technical details are a bit more involved than they are for simple Java libraries.
 
-Each platform you want your project to run on will need its own native libraries. Luckily, this is easier than it used to be because the download section of eclipse.org now includes SWT drops. Download the appropriate SWT drop for the platform you are interested in running on, and set up the VM's classpath and library path accordingly. Here is a command line that was used to launch the BrowserSnippet stand-alone program:
+Each platform you want your project to run on will need its own native libraries. Luckily, this is easier than it used to be because the download section of eclipse.org now includes SWT drops. Download the appropriate SWT drop for the platform you are interested in running on, and set up the VM's classpath and library path accordingly. Here is a command line that was used to launch the `BrowserSnippet` stand-alone program:
 
-      java -cp swt.jar;. -Djava.library.path=. BrowserSnippet
+```sh
+java -cp swt.jar;. -Djava.library.path=. BrowserSnippet
+```
 
 This command line assumes that java is on your execution path and that both swt.jar and the SWT dynamic link library are located in the current working directory.
 
-  
-
 See Also:
 ---------
 
 *   [FAQ How do I configure an Eclipse Java project to use SWT?](./FAQ_How_do_I_configure_an_Eclipse_Java_project_to_use_SWT.md "FAQ How do I configure an Eclipse Java project to use SWT?")
 *   [FAQ How do I create an executable JAR file for a stand-alone SWT program?](./FAQ_How_do_I_create_an_executable_JAR_file_for_a_stand-alone_SWT_program.md "FAQ How do I create an executable JAR file for a stand-alone SWT program?")
 *   [FAQ\_How\_is\_Eclipse\_licensed?](./FAQ_How_is_Eclipse_licensed.md "FAQ How is Eclipse licensed?")
 *   [FAQ\_How\_do\_I\_display\_a\_Web\_page\_in_SWT?](./FAQ_How_do_I_display_a_Web_page_in_SWT.md "FAQ How do I display a Web page in SWT?")
-

docs/FAQ/FAQ_How_do_I_display_a_Web_page_in_SWT.md

@@ -3,44 +3,45 @@ FAQ How do I display a Web page in SWT?
 
 In Eclipse 3.0, SWT introduced a browser widget for displaying a native HTML renderer inside an SWT control. Prior to the introduction of this browser, it was necessary to invoke an external Web browser program for displaying rendered HTML. The browser can be instructed to render either a URL or a supplied string containing HTML content. The browser widget does not include the usual controls for navigation, bookmarks, and all the usual bells and whistles associated with a Web browser. As such, it can be used for highly controlled applications, such as displaying help text or even for showing decorated and interactive text inside a view or an editor.
 
-The browser has API for programmatically manipulating the content, such as browsing forward or back in the navigation history, refreshing the content, or halting a rendering in process. You can install listeners on the browser to be notified when the location is changing or when the title changes or to receive progress notification as a page loads. It is fairly straightforward to implement basic Web browser functionality around this browser widget. For more details, take a look at BrowserAction in the org.eclipse.faq.examples plug-in. This action implements a fully functional Web browser in fewer than 60 lines of code!
+The browser has API for programmatically manipulating the content, such as browsing forward or back in the navigation history, refreshing the content, or halting a rendering in process. You can install listeners on the browser to be notified when the location is changing or when the title changes or to receive progress notification as a page loads. It is fairly straightforward to implement basic Web browser functionality around this browser widget. For more details, take a look at `BrowserAction` in the `org.eclipse.faq.examples` plug-in. This action implements a fully functional Web browser in fewer than 60 lines of code!
 
-As a quick example, here is a stand-alone SWT snippet that opens a browser shell on this book's Web site.
+As a quick example, here is a stand-alone SWT snippet that opens a browser shell on this book's Website.
 
 A title listener is added to the browser in order to update the shell title with the name of the Web page being displayed:
 
-      Display display = new Display();
-      final Shell shell = new Shell(display, SWT.SHELL_TRIM);
-      shell.setLayout(new FillLayout());
-      Browser browser = new Browser(shell, SWT.NONE);
-      browser.addTitleListener(new TitleListener() {
-         public void changed(TitleEvent event) {
-            shell.setText(event.title);
-         }
-      });
-      browser.setBounds(0,0,600,400);
-      shell.pack();
-      shell.open();
-      browser.setUrl("https://eclipse.org");
-      while (!shell.isDisposed())
-         if (!display.readAndDispatch())
-            display.sleep();
-
+```java
+Display display = new Display();
+final Shell shell = new Shell(display, SWT.SHELL_TRIM);
+shell.setLayout(new FillLayout());
+Browser browser = new Browser(shell, SWT.NONE);
+browser.addTitleListener(new TitleListener() {
+   public void changed(TitleEvent event) {
+      shell.setText(event.title);
+   }
+});
+browser.setBounds(0,0,600,400);
+shell.pack();
+shell.open();
+browser.setUrl("https://eclipse.org");
+while (!shell.isDisposed())
+   if (!display.readAndDispatch())
+      display.sleep();
+```
 
-Figure 7.1 shows the resulting browser inside a simple shell. The browser widget is not yet available on all platforms as not all platforms that SWT supports have an appropriate native control that can be exploited. For Eclipse 3.0, the browser will at least be available on Windows, Linux, QNX, and MacOS. For platforms that do not have a browser widget available, the Browser constructor will throw an SWT error, allowing you to catch the condition and fall back to an alternative, such as a user-specified external browser.
+Figure 7.1 shows the resulting browser inside a simple shell. The browser widget is not yet available on all platforms as not all platforms that SWT supports have an appropriate native control that can be exploited. For Eclipse 3.0, the browser will at least be available on Windows, Linux, QNX, and macOS. For platforms that do not have a browser widget available, the Browser constructor will throw an SWT error, allowing you to catch the condition and fall back to an alternative, such as a user-specified external browser.
 
-How can I invoke the eclipse default web browser in my own plugin?
+How can I invoke the Eclipse default web browser in my own plugin?
 ------------------------------------------------------------------
 
       > > I want to invoke the eclipse default web browser which is specified in 
       > > "Preferences" -> "General" -> "Web Browser" in my own plugin, giving it 
       > > a URL and make it visit that URL. How can I do this? Thanks.
 
-I think you want something like...
+I think you want something like below.
 
-      IWorkbenchBrowserSupport support =
+```java
+   IWorkbenchBrowserSupport support =
       PlatformUI.getWorkbench().getBrowserSupport();
-      IWebBrowser browser = support.createBrowser("someId");
-      browser.openURL(new URL("https://www.eclipse.org"));
-
-
+   IWebBrowser browser = support.createBrowser("someId");
+   browser.openURL(new URL("https://www.eclipse.org"));
+```

docs/FAQ/FAQ_How_do_I_embed_AWT_and_Swing_inside_SWT.md

@@ -1,9 +1,8 @@
 
-
 FAQ How do I embed AWT and Swing inside SWT?
 ============================================
 
-In Eclipse 3.0, APIs have been introduced for integrating AWT and Swing with SWT. This support is product-quality on Windows and has only early access support on Linux under JDK 1.5. The main entry point for AWT integration is the class SWT_AWT. It provides a factory method, new_Frame, that creates an AWT Frame that is parented within an SWT Composite. From there, you can create whatever AWT components you want within that frame. The bridging layer created by SWT_AWT handles forwarding of SWT events to the corresponding AWT events within the frame.
+In Eclipse 3.0, APIs have been introduced for integrating AWT and Swing with SWT. This support is product-quality on Windows and has only early access support on Linux under JDK 1.5. The main entry point for AWT integration is the class `SWT_AWT`. It provides a factory method, `new_Frame`, that creates an AWT Frame that is parented within an SWT Composite. From there, you can create whatever AWT components you want within that frame. The bridging layer created by `SWT_AWT` handles forwarding of SWT events to the corresponding AWT events within the frame.
 
 Articles
 --------
@@ -16,4 +15,3 @@ See Also:
 *   [FAQ Is SWT better than Swing?](./FAQ_Is_SWT_better_than_Swing.md "FAQ Is SWT better than Swing?")
 *   [Albireo](https://www.eclipse.org/albireo/) Albireo is an Eclipse Technology project (in incubation phase) that simplifies the task of combining user interface components from the Swing and SWT toolkits. It builds on SWT's standard SWT_AWT bridge, implementing much of the tricky code that is currently left to the developer.
 *   [DJ project](http://djproject.sourceforge.net/) The other way around. The DJ Project lets you embed SWT components in Swing.
-

docs/FAQ/FAQ_How_do_I_explicitly_use_Chromium_as_the_Browser's_underlying_renderer.md

@@ -0,0 +1,30 @@
+FAQ How do I explicitly use Chromium as the Browser's underlying renderer
+=========================================================================
+
+To specify that a Chromium renderer be used by a Browser instance, create it with style `SWT.CHROMIUM` (since 4.17) or set the Java property `org.eclipse.swt.browser.DefaultType=chromium`.
+
+You can get the SWT-Chromium libraries from the Eclipse SDK or from the standalone SWT Chromium support libraries section on the download page.
+
+To use the Chromium libraries from the Eclipse SDK:
+
+* Install the CEF binaries in Eclipse from the p2 repo - [CEF p2 repo from Make technology](https://dl.equo.dev/chromium-swt-ce/oss/p2)
+* Add the required jars to classpath of project:
+  * SWT-Chromium fragment (`org.eclipse.swt.browser.chromium.<ws>.<os>.<arch>.jar`)
+  * SWT fragment (`org.eclipse.swt.<ws>.<os>.<arch>.jar`)
+  * CEF binary (`com.make.chromium.cef.<ws>.<os>.<arch>.jar`)
+
+To use the Chromium libraries from the standalone SWT downloads:
+
+* Get CEF binaries for your platform from the p2 repo:
+  * [CEF GTK binaries](https://dl.equo.dev/chromium-swt-ce/oss/mvn/com/equo/com.equo.chromium.cef.gtk.linux.x86_64/128.0.0/com.equo.chromium.cef.gtk.linux.x86_64-128.0.0.jar)
+  * [CEF Mac binaries](https://dl.equo.dev/chromium-swt-ce/oss/mvn/com/equo/com.equo.chromium.cef.cocoa.macosx.x86_64/128.0.0/com.equo.chromium.cef.cocoa.macosx.x86_64-128.0.0.jar)
+  * [CEF Windows binaries](https://dl.equo.dev/chromium-swt-ce/oss/mvn/com/equo/com.equo.chromium.cef.win32.win32.x86_64/128.0.0/com.equo.chromium.cef.win32.win32.x86_64-128.0.0.jar)
+* Add the required jars to classpath of project:
+  * SWT-Chromium standalone jar (`swt-chromium.jar`)
+  * SWT standalone jar (`swt.jar`)
+  * CEF binary (`com.make.chromium.cef.<ws>.<os>.<arch>.jar`)
+
+To launch Eclipse with Chromium as the default browser type:
+
+* Install the CEF binaries in Eclipse from the p2 repo - [CEF p2 repo from Make technology](https://dl.equo.dev/chromium-swt-ce/oss/p2)
+* In `eclipse.ini`, add `-Dorg.eclipse.swt.browser.DefaultType=chromium` under `-vmargs`.

docs/FAQ/FAQ_How_do_I_explicitly_use_Edge_as_the_Browser's_underlying_renderer.md

@@ -0,0 +1,27 @@
+FAQ How do I explicitly use Edge as the Browser's underlying renderer
+=====================================================================
+
+To specify that an Edge renderer be used by a Browser instance, create it with style `SWT.EDGE` (since 4.19) or set the Java property `org.eclipse.swt.browser.DefaultType=edge`.
+
+Edge rendering back-end uses the WebView2 component, which is based on, but distinct from the Edge browser itself. WebView2 has to be installed separately from one of the following sources:
+
+* A stand-alone runtime installer, either web or offline ([Download the WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/#webview-title) from Microsoft).
+  This runtime will be shared between all applications on the machine and will auto-update itself independent of your application.
+* A fixed-version archive with all the necessary files (Same link as above).
+  This is a complete, fixed set of files to be included with your application. Unlike the first option, you have complete freedom in bundling, packaging and updating it.
+* Beta, Dev, or Canary version of the Edge browser (<https://www.microsoftedgeinsider.com/en-us/download>).
+  This option is convenient for testing, but production deployments should use the previous two options.
+
+_Note: Stable Edge browser installations don't provide a WebView2 component._
+
+See also [Distribution of apps using WebView2](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution) on MSDN.
+
+SWT will automatically locate installed browsers and runtimes. In case you want to use fixed-version binaries or override the automatically chosen version, set the `org.eclipse.swt.browser.EdgeDir` Java property to the directory containing `msedgewebview2.exe`. For example:
+
+```sh
+java "-Dorg.eclipse.swt.browser.EdgeDir=C:\Program Files (x86)\Microsoft\Edge Beta\Application\88.0.705.29" ...
+```
+
+WebView2 creates a user data directory to stores caches and persistent data like cookies and local storage. All WebView2 instances in an application and all instances of the same application share this directory.
+
+The default user-directory location is `%LOCALAPPDATA%\<AppName>\WebView2`, where `<AppName>` is defined with `Display.setAppName()`. This location can be overridden on a per-process basis by setting the `org.eclipse.swt.browser.EdgeDataDir` Java property.

docs/FAQ/FAQ_How_do_I_specify_the_default_type_of_native_renderer_that_is_used_by_the_Browser.md

@@ -0,0 +1,18 @@
+FAQ How do I specify the default type of native renderer that is used by the Browser
+====================================================================================
+
+The default native renderers that are used for `SWT.NONE`-style Browsers are listed in [Which platforms support the SWT Browser, and which native renderers do they use?](./FAQ_Which_platforms_support_the_SWT_Browser,_and_which_native_renderers_are_available.md). Default is chosen to not require additional software installation and to preserve backward-compatible behavior.
+
+A user can set a property to specify the type of native renderer to use for `SWT.NONE`-style Browsers. Setting this property does not affect Browsers that are created with explicit renderer styles such as `SWT.WEBKIT` or `SWT.CHROMIUM`. The property name is `org.eclipse.swt.browser.DefaultType` and valid values for it currently include `webkit`, `ie` (since 4.3), `chromium` (since 4.17) and `edge` (since 4.19). This property must be set before the first `Browser` instance is created.
+
+_Note: As of Eclipse/SWT 4.8, Mozilla (`XULRunner`) renderer is no longer supported, the value `mozilla` has no effect._
+
+A user can specify a comma-separated list of native renderers, in order of preference, for the `org.eclipse.swt.browser.DefaultType` value. Values not applicable to a particular platform are ignored. For example, the value of `edge,chromium` will change the default to Edge on Windows and Chromium on other platforms.
+
+The best opportunity for a user to set this property is by launching their application with a `-D` VM switch (e.g., add to the end of the `eclipse.ini` file: `-Dorg.eclipse.swt.browser.DefaultType=chromium`).
+
+An alternate approach that an Eclipse application may use is to provide a `BrowserInitializer` implementation that sets this property. This implementation will be invoked when the first Browser instance is about to be created. The steps to do so are:
+
+* Create a fragment with host plug-in `org.eclipse.swt`.
+* In this fragment, create class `org.eclipse.swt.browser.BrowserInitializer`.
+* Implement a static initializer in this class that sets the `org.eclipse.swt.browser.DefaultType` property.

docs/FAQ/FAQ_What_is_Ant.md

@@ -1,5 +1,4 @@
 
-
 FAQ What is Ant?
 ================
 
@@ -16,4 +15,3 @@ See Also:
 
 *   [Apache Ant](http://ant.apache.org)
 *   [FAQ What is the use of the build.xml file?](./FAQ_What_is_the_use_of_the_build_xml_file.md "FAQ What is the use of the build.xml file?")
-