Inline details of build and overview websites as popup dialogs

Instead, show details as popup dialog opened when clicking the info-icon
next the corresponding headline.

Author: HannesWell

sites/eclipse/README.md

@@ -32,5 +32,5 @@ Unzip the archives to a location of your choise and launch the RelEng Java progr
 ## Launching a web-server
 
 Launch `jwebserver` from this or the parent folder (requires a JDK-18 or later on `PATH`)
-and open the localhost URL displayed on the console (by default `http://127.0.0.1:8000/`).
+and open the localhost URL displayed on the console (by default `http://localhost:8000/`).
 Run `jwebserver --help` for help and further options.

sites/eclipse/build/details.html

@@ -125,12 +125,17 @@ <h4>Verify artifact integrity</h4>
 			</div>
 		</details>
 
-		<h3 id="repository">Eclipse p2 Repository
-			<a href="details.html#Repository"><i class="fa fa-xs fa-info-circle"></i></a>
-		</h3>
+		<h3 id="repository">Eclipse p2 Repository</h3>
+		<dialog class="details-popup">
+			<h3>Eclipse p2 Repository</h3>
+			The Eclipse p2 Repository includes all artifacts produced by the Eclipse Project, including the Eclipse Platform, the Equinox OSGi runtime,
+			Java development tools, Plug-in Development Environment and even some extra items from other projects
+			required by Eclipse (such as a few bundles from EMF and Orbit).<br>
+			Please be aware that repositories have different retention policies, and restrictions on what types can be updated with what other types.
+			See the information on the different build types at the <a href="https://download.eclipse.org/eclipse/downloads/">Eclipse Downloads</a> page for details.
+		</dialog>
 		<p>
-			To update your Eclipse installation to this development stream, you can use the software repository at
-			<br>
+			To update your Eclipse installation to this development stream, you can use the software repository at<br>
 			<code><a class="data-ref" href="${updatesP2RepositoryComposite}">${updatesP2RepositoryComposite}</a></code>
 		</p>
 		<p>
@@ -140,29 +145,72 @@ <h3 id="repository">Eclipse p2 Repository
 		</p>
 		<table class="files-table" data-path="p2Repository"></table>
 
-		<h3 id="eclipse-sdk">Eclipse SDK
-			<a href="details.html#EclipseSDK"><i class="fa fa-xs fa-info-circle"></i></a>
-		</h3>
+		<h3 id="eclipse-sdk">Eclipse SDK</h3>
+		<dialog class="details-popup">
+			<h3>Eclipse SDK</h3>
+			The Eclipse SDK includes the Eclipse Platform, Java development tools, and Plug-in Development Environment,
+			including source and both user and programmer documentation.
+			If you aren't sure which download you want... then you probably want this one.
+			You will need a <em>Java</em> installation, ideally a JDK, to run Eclipse (Java-21 or greater is required).
+		</dialog>
 		<table class="files-table" data-path="sdkProducts"></table>
 
-		<h3 id="testing-framework">Tests and Testing Framework
-			<a href="details.html#JUnitPlugin"><i class="fa fa-xs fa-info-circle"></i></a>
-		</h3>
+		<h3 id="testing-framework">Tests and Testing Framework</h3>
+		<dialog class="details-popup">
+			<h3>Tests and Testing Framework</h3>
+			These packages contain the Test Framework and JUnit Test Plug-ins used to run JUnit plug-in tests from the command line.
+			See the Platform's <a href="https://wiki.eclipse.org/Platform-releng/Automated_Testing">Automated Testing</a> wiki page for more information and setup instructions.
+			Includes both source code and binary.
+		</dialog>
 		<table class="files-table" data-path="eclipseTests"></table>
 
-		<h3 id="platform-runtime">Platform Runtime Binary
-			<a href="details.html#PlatformRuntime"><i class="fa fa-xs fa-info-circle"></i></a>
-		</h3>
+		<h3 id="platform-runtime">Platform Runtime Binary</h3>
+		<dialog class="details-popup">
+			<h3>Platform Runtime Binary</h3>
+			These products contains only the Eclipse Platform with user documentation and no source and no programmer documentation.
+			The Java development tools and Plug-in Development Environment are <em>not</em> included.
+			You can use these products as base to package your tool plug-ins for redistribution when you don't want to ship the entire SDK.
+		</dialog>
 		<table class="files-table" data-path="platformProducts"></table>
 
-		<h3 id="ecj">JDT Core Batch Compiler
-			<a href="details.html#JDTCORE"><i class="fa fa-xs fa-info-circle"></i></a>
-		</h3>
+		<h3 id="ecj">JDT Core Batch Compiler</h3>
+		<dialog class="details-popup">
+			<h3>JDT Core Batch Compiler</h3>
+			These archives contain the standalone batch java compiler, Ant compiler adapter and associated source.
+			The batch compiler and Ant adapter (ecj.jar) are extracted from the <code>org.eclipse.jdt.core</code> plug-in as a lean download.
+			For examples of usage, please refer to the help section:<br>
+			<a href="https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Fguide%2Fjdt_api_compile.htm">JDT Plug-in Developer Guide &gt; Programmer's Guide &gt; JDT Core &gt; Compiling Java code</a>
+		</dialog>
 		<table class="files-table" data-path="jdtCompiler"></table>
 
-		<h3 id="swt">SWT Binary and Source
-			<a href="details.html#SWT"><i class="fa fa-xs fa-info-circle"></i></a>
-		</h3>
+		<h3 id="swt">SWT Binary and Source</h3>
+		<dialog class="details-popup">
+			<h3>SWT Binary and Source</h3>
+			<p>
+				These archives contain the SWT libraries and source for standalone SWT application development.
+				For examples of standalone SWT applications refer to the <a href="https://eclipse.dev/eclipse/swt/snippets/">snippets</a> section of the SWT Component page.
+			</p>
+			<p>
+				To run a standalone SWT application, add the swt jar(s) to the classpath.
+				For example, if you extract the download below to <code>C:\SWT</code> you would launch the <code>HelloWorld</code> application with the following command:<br>
+				<code>java -classpath C:\SWT\swt.jar;C:\MyApp\helloworld.jar HelloWorld</code>
+			</p>
+			<p>
+				To run the standalone SWT examples that are shipped with Eclipse, download them from
+				<code><a href="https://download.eclipse.org/eclipse/updates/">eclipse/updates</a>/$VERSION/plugins/org.eclipse.swt.examples_*.jar</code>.
+				Then copy the file to <code>C:\SWT</code>.
+				Now you can run the examples as described in <a href="https://eclipse.dev/eclipse/swt/examples.html">SWT Examples</a>.
+				For example:<br>
+				<code>
+					cd C:\SWT<br>
+					java -classpath swt.jar;swtexamples.jar org.eclipse.swt.examples.controlexample.ControlExample
+				</code>
+			</p>
+			<p>
+				On Linux systems, note that the classpath separator character is a colon, so the equivalent command becomes:<br>
+				<code>java -classpath swt.jar:swtexamples.jar org.eclipse.swt.examples.controlexample.ControlExample</code>
+			</p>
+		</dialog>
 		<table class="files-table" data-path="swtBinaries"></table>
 
 	</main>

sites/eclipse/build/index.html

@@ -18,27 +18,69 @@ <h1>The Eclipse Project Downloads</h1>
 		<!--TODO: check all the links and migrate them if necessary-->
 		<p>
 			On this page you can find the latest builds produced by the <a href="https://www.eclipse.org/eclipse/">Eclipse Project</a>.
-			To get started, run the program and go through the user and developer documentation provided in the help system or see the <a href="http://help.eclipse.org/">web-based help system</a>.
+			To get started, run the program and go through the user and developer documentation provided in the help system or see the <a href="https://help.eclipse.org/">web-based help system</a>.
 			If you have problems installing or getting the workbench to run, <a href="https://wiki.eclipse.org/The_Official_Eclipse_FAQs">check out the Eclipse Project FAQ</a>, or try posting a question to the <a href="https://www.eclipse.org/forums/">forum</a>.
 		</p>
 		<p>
 			See the <a href="https://www.eclipse.org/downloads/">main Eclipse Foundation download site</a> for convenient all-in-one packages.
-			The <a href="http://archive.eclipse.org/eclipse/downloads/">archive site</a> contains older releases (including the last 3.x version, <a href="http://archive.eclipse.org/eclipse/downloads/drops/R-3.8.2-201301310800/">3.8.2</a>).
-			For reference, see also the <a href="https://wiki.eclipse.org/Eclipse_Project_Update_Sites">p2 repositories provided</a>, meaning of <a href="https://download.eclipse.org/eclipse/downloads/build_types.html">kinds of builds (P,M,I,S, and R)</a>, and the <a href="https://www.eclipse.org/eclipse/platform-releng/buildSchedule.html">build schedule</a>.
+			The <a href="https://archive.eclipse.org/eclipse/downloads/">archive site</a> contains older releases (including the last 3.x version, <a href="https://archive.eclipse.org/eclipse/downloads/drops/R-3.8.2-201301310800/">3.8.2</a>).
+			For reference, see also the <a href="https://wiki.eclipse.org/Eclipse_Project_Update_Sites">p2 repositories provided</a>, and the <a href="https://www.eclipse.org/eclipse/platform-releng/buildSchedule.html">build schedule</a>.
 		</p>
 		<h3 id="latest-downloads">Latest Downloads</h3>
 		<table class="builds-table" data-path="latest"></table>
 
-		<h3 id="latest-release">Latest Release</h3>
+		<h3 id="latest-release">Latest Releases</h3>
+		<dialog class="details-popup">
+			<h3>Latest Releases</h3>
+			<em>Releases</em> are builds that have been declared as release for the general public - for example <code>R4.38</code>.
+			Releases are the right builds for people who want to be on a stable, tested release, and don't need the latest greatest features and improvements.
+			Release builds always have an "R" at the beginning of the name i.e. <code>R4.0</code>, <code>R4.37</code> etc.
+			<h4>Retention policy</h4>
+			Releases are retained indefinitely.<br>
+			However, only the build websites of the last three releases are provided at this main download area.
+			Older releases are available in the <a href="https://archive.eclipse.org/eclipse/downloads/">Eclipse Archive</a>.
+			Links to artifacts, that were later moved to the archive, are transparently redirected and continue to work.
+			Similarly the P2-repositories of only the last ten releases are provided in this download area and older repositories are moved to the archive.
+			Again, links pointing to P2-repositories at this main download area continue to work, even after a repository was moved to the archive.
+		</dialog>
 		<table class="builds-table" data-path="releases"></table>
 
 		<h3 id="stable-builds">Stable Builds</h3>
+		<dialog class="details-popup">
+			<h3>Stable Builds</h3>
+			<em>Stable builds</em> are <em>integration builds</em> that have been found to be stable enough for most people to use.
+			They are promoted from <em>integration</em> to <em>stable build</em> on a regular schedule, as <em>milestones</em> or <em>release-candidates</em> and after they have been used for a few days and deemed reasonably stable.
+			The latest stable build is the right build for people who want to stay up to date with what is going on in the latest development stream, and don't mind putting up with a few problems in order to get the latest greatest features and bug fixes.
+			The latest stable build is the one the development team likes people to be using, because of the valuable and timely feedback.
+			<h4>Retention policy</h4>
+			Stable builds and their P2-repositories are retained until the targeted release is published.
+		</dialog>
 		<table class="builds-table" data-path="stableBuilds"></table>
 
 		<h3 id="integration-builds">Integration Builds</h3>
+		<dialog class="details-popup">
+			<h3>Integration Builds</h3>
+			An <em>Integration build</em> (short <em>I-Build</em>) is usually produced once a day and reflects the latest development state of the main branches of all contributing Git repositories.
+			Even though changes are developed with great diligence, I-Builds are more likely to contain bugs and functionality degradations may occur temporarily.
+			In case of a severe problem the corresponding I-Build is marked as <em>unstable</em>.
+			I-Builds are recommended for developers of Eclipse itself and for those interested in testing the very latest features, bug-fixes and state.
+			<h4>Retention policy</h4>
+			The build website of an I-Build is retained for at least five days.
+			From older I-Builds only the first (not unstable) build of a week is retained until the targeted release is published.
+			The p2-repository of each I-Build is retained until the targeted release is published.
+		</dialog>
 		<table class="builds-table" data-path="iBuilds"></table>
 
 		<h3 id="beta-java-builds">Beta Java Builds</h3>
+		<dialog class="details-popup">
+			<h3>Beta Java Builds</h3>
+			<em>Beta Java Builds</em> provide the latest development state of the support for the upcoming, not yet released <em>Java</em> version
+			in Eclipse JDT's Java Compiler ECJ, UI and debug support.
+			These builds are produced regularly from dedicated <em>beta</em> branches in the JDT Git repositories.
+			<h4>Retention policy</h4>
+			For <em>Beta Java Builds</em> the websites of last nine builds are retained.
+			The corresponding P2-repositories are retained until the next development cycle respectively the targeted java version is released.
+		</dialog>
 		<table class="builds-table" data-path="yBuilds"></table>
 
 	</main>