Skip to content

Commit a89f764

Browse files
HannesWellHannesWell
committed
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.
1 parent a19b619 commit a89f764

File tree

7 files changed

+185
-169
lines changed

7 files changed

+185
-169
lines changed

‎sites/eclipse/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,5 +32,5 @@ Unzip the archives to a location of your choise and launch the RelEng Java progr
3232
## Launching a web-server
3333

3434
Launch `jwebserver` from this or the parent folder (requires a JDK-18 or later on `PATH`)
35-
and open the localhost URL displayed on the console (by default `http://127.0.0.1:8000/`).
35+
and open the localhost URL displayed on the console (by default `http://localhost:8000/`).
3636
Run `jwebserver --help` for help and further options.

‎sites/eclipse/build/details.html‎

Lines changed: 0 additions & 130 deletions
This file was deleted.

‎sites/eclipse/build/index.html‎

Lines changed: 59 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -125,9 +125,15 @@ <h4>Verify artifact integrity</h4>
125125
</div>
126126
</details>
127127

128-
<h3 id="repository">Eclipse p2 Repository
129-
<a href="details.html#Repository"><i class="fa fa-xs fa-info-circle"></i></a>
130-
</h3>
128+
<h3 id="repository">Eclipse p2 Repository</h3>
129+
<dialog class="details-popup">
130+
<h3>Eclipse p2 Repository</h3>
131+
The Eclipse Repository includes all that is produced by the Eclipse Project, including the Eclipse Platform,
132+
Java development tools, and Plug-in Development Environment, Unit Tests, and even some extra items from other projects
133+
required by Eclipse (such as Equinox and a few bundles from EMF and Orbit).
134+
Please be aware that repositories have different retention policies, and restrictions on what types can be updated with what other types.
135+
See the wiki's <a href="https://wiki.eclipse.org/Eclipse_Project_Update_Sites">Update Sites</a> document for details.
136+
</dialog>
131137
<p>
132138
To update your Eclipse installation to this development stream, you can use the software repository at
133139
<br>
@@ -140,29 +146,64 @@ <h3 id="repository">Eclipse p2 Repository
140146
</p>
141147
<table class="files-table" data-path="p2Repository"></table>
142148

143-
<h3 id="eclipse-sdk">Eclipse SDK
144-
<a href="details.html#EclipseSDK"><i class="fa fa-xs fa-info-circle"></i></a>
145-
</h3>
149+
<h3 id="eclipse-sdk">Eclipse SDK</h3>
150+
<dialog class="details-popup">
151+
<h3>Eclipse SDK</h3>
152+
The Eclipse SDK includes the Eclipse Platform, Java development tools, and Plug-in Development Environment,
153+
including source and both user and programmer documentation.
154+
If you aren't sure which download you want... then you probably want this one.
155+
You will need a <a href="https://wiki.eclipse.org/Eclipse/Installation#Install_a_JVM">Java runtime environment (JRE)</a> to use Eclipse (Java-21 or greater is recommended).
156+
</dialog>
146157
<table class="files-table" data-path="sdkProducts"></table>
147158

148-
<h3 id="testing-framework">Tests and Testing Framework
149-
<a href="details.html#JUnitPlugin"><i class="fa fa-xs fa-info-circle"></i></a>
150-
</h3>
159+
<h3 id="testing-framework">Tests and Testing Framework</h3>
160+
<dialog class="details-popup">
161+
<h3>Tests and Testing Framework</h3>
162+
These packages contain the Test Framework and JUnit test plugins used to run JUnit plug-in tests from the command line.
163+
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.
164+
Includes both source code and binary.
165+
</dialog>
151166
<table class="files-table" data-path="eclipseTests"></table>
152167

153-
<h3 id="platform-runtime">Platform Runtime Binary
154-
<a href="details.html#PlatformRuntime"><i class="fa fa-xs fa-info-circle"></i></a>
155-
</h3>
168+
<h3 id="platform-runtime">Platform Runtime Binary</h3>
169+
<dialog class="details-popup">
170+
<h3>Platform Runtime Binary</h3>
171+
These drops contain only the Eclipse Platform with user documentation and no source and no programmer documentation.
172+
The Java development tools and Plug-in Development Environment are NOT included.
173+
You can use these drops to help you package your tool plug-ins for redistribution when you don't want to ship the entire SDK.
174+
</dialog>
156175
<table class="files-table" data-path="platformProducts"></table>
157176

158-
<h3 id="ecj">JDT Core Batch Compiler
159-
<a href="details.html#JDTCORE"><i class="fa fa-xs fa-info-circle"></i></a>
160-
</h3>
177+
<h3 id="ecj">JDT Core Batch Compiler</h3>
178+
<dialog class="details-popup">
179+
<h3>JDT Core Batch Compiler</h3>
180+
These drops contain the standalone batch java compiler, Ant compiler adapter and associated source.
181+
The batch compiler and Ant adapter (ecj.jar) are extracted from the <code>org.eclipse.jdt.core</code> plug-in as a lean download.
182+
For examples of usage, please refer to this help section: JDT Plug-in Developer Guide&gt;Programmer's Guide&gt;JDT Core&gt;Compiling Java code.
183+
</dialog>
161184
<table class="files-table" data-path="jdtCompiler"></table>
162185

163-
<h3 id="swt">SWT Binary and Source
164-
<a href="details.html#SWT"><i class="fa fa-xs fa-info-circle"></i></a>
165-
</h3>
186+
<h3 id="swt">SWT Binary and Source</h3>
187+
<dialog class="details-popup">
188+
<h3>SWT Binary and Source</h3>
189+
<p>
190+
These drops contain the SWT libraries and source for standalone SWT application development.
191+
For examples of standalone SWT applications refer to the <a href=" https://www.eclipse.org/swt/snippets/">snippets</a> section of the SWT Component page.
192+
</p>
193+
<p>To run a standalone SWT application, add the swt jar(s) to the classpath.
194+
For example, if you extract the download below to <code>C:\SWT</code> you would launch the HelloWorld application with the following command:
195+
</p>
196+
<code>java -classpath C:\SWT\swt.jar;C:\MyApp\helloworld.jar HelloWorld</code>
197+
<p>
198+
To run the standalone SWT examples that are shipped with Eclipse, download them from <a href="https://download.eclipse.org/eclipse/updates/">here</a>/$VERSION/plugins/org.eclipse.swt.examples_*.jar.
199+
Then copy the file to C:\SWT.
200+
Now you can run the examples that are described <a href="https://www.eclipse.org/swt/examples.php">here</a>.
201+
For example:
202+
</p>
203+
<code>cd C:\SWT<br> java -classpath swt.jar;swtexamples.jar org.eclipse.swt.examples.controlexample.ControlExample</code>
204+
<p>On Linux systems, note that the classpath separator character is a colon, so the equivalent command becomes:</p>
205+
<code>java -classpath swt.jar:swtexamples.jar org.eclipse.swt.examples.controlexample.ControlExample</code>
206+
</dialog>
166207
<table class="files-table" data-path="swtBinaries"></table>
167208

168209
</main>

‎sites/eclipse/overview/index.html‎

Lines changed: 47 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,27 +18,70 @@ <h1>The Eclipse Project Downloads</h1>
1818
<!--TODO: check all the links and migrate them if necessary-->
1919
<p>
2020
On this page you can find the latest builds produced by the <a href="https://www.eclipse.org/eclipse/">Eclipse Project</a>.
21-
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>.
21+
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>.
2222
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>.
2323
</p>
2424
<p>
2525
See the <a href="https://www.eclipse.org/downloads/">main Eclipse Foundation download site</a> for convenient all-in-one packages.
26-
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>).
27-
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>.
26+
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>).
27+
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>.
2828
</p>
2929
<h3 id="latest-downloads">Latest Downloads</h3>
3030
<table class="builds-table" data-path="latest"></table>
3131

32-
<h3 id="latest-release">Latest Release</h3>
32+
<h3 id="latest-release">Latest Releases</h3>
33+
<!-- TODO: explain the retention policy from https://wiki.eclipse.org/Eclipse_Project_Update_Sites and mention that older releases are continued in the archives. -->
34+
<dialog class="details-popup">
35+
<h3>Latest Releases</h3>
36+
<em>Releases</em> are builds that have been declared major releases by the development team - for example <code>R4.38</code>.
37+
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.
38+
Release builds always have an "R" at the beginning of the name i.e. <code>R4.0</code>, <code>R4.37</code> etc.
39+
<h4>Retention policy</h4>
40+
Releases are retained indefinitivly.
41+
However, only the build websites of the last three releases are provided at this main download area.
42+
Older releases are available in the <a href="https://archive.eclipse.org/eclipse/downloads/">Eclipse Archive</a>.
43+
Existing links to artifacts, that were moved to the archive, are transparently redirected and continue to work.
44+
Similarly only the P2-repositories of the last ten releases are provided at this download area and older repositories are moved to the archive.
45+
Again, links pointing to P2-repositories at this download area continue to work, even after a repository was moved to the archive.
46+
</dialog>
3347
<table class="builds-table" data-path="releases"></table>
3448

3549
<h3 id="stable-builds">Stable Builds</h3>
50+
<dialog class="details-popup">
51+
<h3>Stable Builds</h3>
52+
<em>Stable builds</em> are <em>integration builds</em> that have been found to be stable enough for most people to use.
53+
They are promoted from <em>integration</em> to <em>stable build</em> at a regular schedule as milestones or release-candidates and after they have been used for a few days and deemed reasonably stable.
54+
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.
55+
The latest stable build is the one the development team likes people to be using, because of the valuable and timely feedback.
56+
<h4>Retention policy</h4>
57+
Stable builds and their P2-repositories are retained until the targeted release is published.
58+
</dialog>
3659
<table class="builds-table" data-path="stableBuilds"></table>
3760

3861
<h3 id="integration-builds">Integration Builds</h3>
62+
<dialog class="details-popup">
63+
<h3>Integration Builds</h3>
64+
An <em>Integration build</em> (short <em>I-build</em>) is usually produced once a day and reflects the latest development state from the main branches of all contributing Git repositories.
65+
Altough great care is taken to submit changes only in best quality, I-builds are more likely to contain bugs and functionality degradations may occure temporarily.
66+
In case a severe problem is found the corresponding I-Build is marked as unstable.
67+
Using I-Builds is recommended for developers of Eclipse itself and for those interested in testing the latest features and state.
68+
<h4>Retention policy</h4>
69+
The build website of an integration build (short <em>I-build</em>) is retained for at least five days.
70+
From older I-builds only the first (not unstable) build of a week is retained until the targeted release is published.
71+
The p2-repository of each I-build is retained until the targeted release is published.
72+
</dialog>
3973
<table class="builds-table" data-path="iBuilds"></table>
4074

4175
<h3 id="beta-java-builds">Beta Java Builds</h3>
76+
<dialog class="details-popup">
77+
<h3>Beta Java Builds</h3>
78+
The <em>Beta Java Builds</em> provide the latest development state of JDT's support for the upcomming, not yet released <em>Java</em> version,
79+
including JDT's Java Compiler ECJ as well as UI and debug support.
80+
These builds are produced from dedicated <em>beta</em> branches in the JDT Git repositories.
81+
<h4>Retention policy</h4>
82+
For <em>Beta Java Builds</em> the last nine builds websites are retained
83+
and the corresponding P2-repositories are retained until the next development cycle respectivly until the targeted java version is released.
84+
</dialog>
4285
<table class="builds-table" data-path="yBuilds"></table>
4386

4487
</main>

‎sites/eclipse/page.css‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,44 @@ li.toc-item a {
7979
text-decoration: none;
8080
}
8181

82+
/* Pop-up dialog*/
83+
84+
.details-icon {
85+
/*darker steelblue*/
86+
color: rgb(48, 89, 122);
87+
border: none;
88+
background: none;
89+
}
90+
91+
dialog {
92+
border: none;
93+
border-radius: 2px;
94+
padding: 2rem;
95+
position: relative;
96+
/* Needed for absolute positioning of close btn */
97+
}
98+
99+
dialog::backdrop {
100+
background: rgba(0, 0, 0, 0.5);
101+
backdrop-filter: blur(3px);
102+
}
103+
104+
dialog button.close-btn {
105+
position: absolute;
106+
top: 0.25rem;
107+
right: 0.25rem;
108+
line-height: 1;
109+
font-size: 3.0rem;
110+
padding: 0;
111+
border: none;
112+
background: none;
113+
color: dimgray;
114+
}
115+
116+
dialog button.close-btn:hover {
117+
color: black;
118+
}
119+
82120
/* Details sections */
83121

84122
details {

0 commit comments

Comments
 (0)