Skip to content

Commit

Permalink
Bug 578309: Tidy doc HTML files in /gettingStarted
Browse files Browse the repository at this point in the history
All these have been cleanup up with HTML tidy with:
  tidy -miq --wrap 120 --tidy-mark no

Change-Id: Ie60e36f996058b3b643763e451930a384ffe8f62
Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.common/+/190113
Tested-by: Alexander Kurtakov <akurtako@redhat.com>
Reviewed-by: Alexander Kurtakov <akurtako@redhat.com>
  • Loading branch information
BeckerWdf authored and akurtakov committed Feb 4, 2022
1 parent 7609697 commit 3eea3a3
Show file tree
Hide file tree
Showing 81 changed files with 3,253 additions and 3,999 deletions.
@@ -1,56 +1,40 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2012. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Eclipse platform overview</title>

<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
<meta name="copyright" content=
"Copyright (c) IBM Corporation and others 2000, 2012. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
<title>Eclipse platform overview</title>
<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"></script>
</head>

<BODY BGCOLOR="#ffffff">
<h1>Eclipse platform overview</h1>

<p>The Eclipse platform itself is structured as subsystems which are implemented
in one or more plug-ins. The subsystems are built on top of a small runtime
engine. The figure below depicts a simplified view. </p>
<p align="center">
<img alt="Platform runtime base with groups of plug-ins adding function" src="../../images/arch-npi.svg" border="0">
</p>
<h2>Workbench</h2>
<P>The term <i>Workbench</i> refers to the desktop development environment.
The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources.</P>


<P>
Each Workbench window contains one or more
perspectives. Perspectives contain views and editors and control
what appears in certain menus and tool bars. More than one Workbench window can exist
on the desktop at any given time.</P>

<h3 class="related">Related concepts</h3>
<a href="../../concepts/concepts-25.htm">Features</a><br>
<a href="../../concepts/concepts-12.htm">Resources</a><br>
<a href="../../concepts/concepts-4.htm">Perspectives</a><br>
<a href="../../concepts/concepts-5.htm">Views</a><br>
<a href="../../concepts/concepts-6.htm">Editors</a><br>
<a href="../../concepts/concepts-27c.htm">CVS Repositories</a>

<h3 class="related">Related tasks</h3>
<a href="../../tasks/tasks-124.htm">Installing new software</a><br>
<a href="../../tasks/tasks-9f.htm">Opening perspectives</a><br>
<a href="../../tasks/tasks-3.htm">Opening views</a><br>
<a href="../../tasks/tasks-28.htm">Switching between perspectives</a><br>
<a href="../../tasks/tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
<a href="../../tasks/tasks-9m.htm">Configuring perspective command groups</a><br>
<a href="../../tasks/tasks-9k.htm">Configuring perspective shortcuts</a>

<h3 class="related">Related reference</h3>
<a href="../../reference/ref-68.htm">Toolbar buttons</a>

</BODY>
</HTML>
<body bgcolor="#FFFFFF">
<h1>Eclipse platform overview</h1>
<p>The Eclipse platform itself is structured as subsystems which are implemented in one or more plug-ins. The
subsystems are built on top of a small runtime engine. The figure below depicts a simplified view.</p>
<p align="center"><img alt="Platform runtime base with groups of plug-ins adding function" src=
"../../images/arch-npi.svg" border="0"></p>
<h2>Workbench</h2>
<p>The term <i>Workbench</i> refers to the desktop development environment. The Workbench aims to achieve seamless
tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation
of workspace resources.</p>
<p>Each Workbench window contains one or more perspectives. Perspectives contain views and editors and control what
appears in certain menus and tool bars. More than one Workbench window can exist on the desktop at any given
time.</p>
<h3 class="related">Related concepts</h3><a href="../../concepts/concepts-25.htm">Features</a><br>
<a href="../../concepts/concepts-12.htm">Resources</a><br>
<a href="../../concepts/concepts-4.htm">Perspectives</a><br>
<a href="../../concepts/concepts-5.htm">Views</a><br>
<a href="../../concepts/concepts-6.htm">Editors</a><br>
<a href="../../concepts/concepts-27c.htm">CVS Repositories</a>
<h3 class="related">Related tasks</h3><a href="../../tasks/tasks-124.htm">Installing new software</a><br>
<a href="../../tasks/tasks-9f.htm">Opening perspectives</a><br>
<a href="../../tasks/tasks-3.htm">Opening views</a><br>
<a href="../../tasks/tasks-28.htm">Switching between perspectives</a><br>
<a href="../../tasks/tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
<a href="../../tasks/tasks-9m.htm">Configuring perspective command groups</a><br>
<a href="../../tasks/tasks-9k.htm">Configuring perspective shortcuts</a>
<h3 class="related">Related reference</h3><a href="../../reference/ref-68.htm">Toolbar buttons</a>
</body>
</html>
35 changes: 15 additions & 20 deletions bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
@@ -1,20 +1,15 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>

<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Basic tutorial</title>

</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>Basic tutorial</H1>

<P>This tutorial provides a step by step walk-through of the
Workbench.<br>
</P>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content=
"Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>Basic tutorial</title>
</head>
<body bgcolor="#FFFFFF">
<h1>Basic tutorial</h1>
<p>This tutorial provides a step by step walk-through of the Workbench.<br></p>
</body>
</html>
79 changes: 35 additions & 44 deletions bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
@@ -1,44 +1,35 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>

<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>The Workbench</title>
<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
</HEAD>

<BODY BGCOLOR="#ffffff">
<h1>The Workbench</h1>

<P CLASS="Para"> When the Workbench is launched, the first thing you see is a
dialog that allows you to select where the workspace should be located. The
workspace is the directory where your work will be stored. For now, just
click OK to pick the default location.</p>
<p>After the workspace location is chosen, a single Workbench window is displayed.
A Workbench window offers one or more perspectives. A perspective contains
editors and views, such as the Project Explorer. Multiple Workbench windows can be
opened simultaneously. Initially, in the first Workbench window that is opened,
the Java perspective is displayed, with only the Welcome view visible.
Click the arrow labeled <b>Workbench</b> in the Welcome view to cause the other
views in the perspective to become visible. Note you can get the Welcome view back at any time by selecting
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.quickStartAction")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.svg" alt="command link">
<b>Help &gt; Welcome</b></a>.</p>
<p>A shortcut bar appears in the top right corner of the window. This allows you
to open new perspectives and switch between ones already open. The name of the
active perspective is shown in the title of the window and its item in the shortcut
bar is highlighted.</p>
<p>You should be seeing the Java perspective. We will switch to the simpler Resource perspective
to simplify this tutorial. Select
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.ui.resourcePerspective)")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.svg" alt="command link">
<b>Window &gt; Perspective &gt; Open Perspective &gt; Other... &gt; Resource</b></a>.
The Project Explorer, Outline, and Tasks views should now be visible. <br>
</p>
<P CLASS="Para"><img src="../images/Image1.png" alt="Workbench" border="0" width="800"></P>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content=
"Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>The Workbench</title>
<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"></script>
</head>
<body bgcolor="#FFFFFF">
<h1>The Workbench</h1>
<p class="Para">When the Workbench is launched, the first thing you see is a dialog that allows you to select where
the workspace should be located. The workspace is the directory where your work will be stored. For now, just click
OK to pick the default location.</p>
<p>After the workspace location is chosen, a single Workbench window is displayed. A Workbench window offers one or
more perspectives. A perspective contains editors and views, such as the Project Explorer. Multiple Workbench windows
can be opened simultaneously. Initially, in the first Workbench window that is opened, the Java perspective is
displayed, with only the Welcome view visible. Click the arrow labeled <b>Workbench</b> in the Welcome view to cause
the other views in the perspective to become visible. Note you can get the Welcome view back at any time by selecting
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.quickStartAction")'><img src=
"PLUGINS_ROOT/org.eclipse.help/command_link.svg" alt="command link"> <b>Help &gt; Welcome</b></a>.</p>
<p>A shortcut bar appears in the top right corner of the window. This allows you to open new perspectives and switch
between ones already open. The name of the active perspective is shown in the title of the window and its item in the
shortcut bar is highlighted.</p>
<p>You should be seeing the Java perspective. We will switch to the simpler Resource perspective to simplify this
tutorial. Select <a class="command-link" href=
'javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.ui.resourcePerspective)")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.svg" alt="command link"> <b>Window &gt; Perspective &gt; Open
Perspective &gt; Other... &gt; Resource</b></a>. The Project Explorer, Outline, and Tasks views should now be
visible.<br></p>
<p class="Para"><img src="../images/Image1.png" alt="Workbench" border="0" width="800"></p>
</body>
</html>
93 changes: 39 additions & 54 deletions bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
@@ -1,54 +1,39 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>

<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Editors and views</title>

</HEAD>
<BODY BGCOLOR="#ffffff">
<h1>Editors and views</h1>

<P CLASS="Intro">Prior to commencing the Workbench tutorials found in this section,
it is important to first be familiar with the various elements of the Workbench.
A Workbench consists of:</p>
<ul>
<li>
perspectives</li>
<li>
views</li>
<li>
editors</li>
</ul>
<p CLASS="Intro">A perspective is a group of views and editors in
the Workbench window. One or more perspectives can exist in a single Workbench
window. Each perspective contains one or more views and editors. Within a
window, each perspective may have a different set of views but all perspectives
share the same set of editors.</p>
<p CLASS="Intro">A view is a visual component within the Workbench. It is typically
used to navigate a list or hierarchy of information (such as the resources in the Workbench),
or display properties for the active editor. Modifications made in a view are saved immediately.</p>
<p CLASS="Intro">An editor is also a visual component within the Workbench. It is typically used to edit or browse a
resource. The visual presentation might be text or a diagram.
Typically, editors are launched by clicking on a resource in a view.
Modifications made in an editor follow an open-save-close lifecycle model.
</p>
<p CLASS="Intro">Some features are common to both views and editors. We use the
term &quot;part&quot; to mean either a view or an editor. Parts can be active
or inactive, but only one part can be active at any one time. The active
part is the one whose title bar is highlighted. The active part is the target
for common operations like cut, copy and paste. The active part also determines
the contents of the status line. If an editor tab is not highlighted it indicates
the editor is not active, however views may show information based on the last
active editor.</p>
<p CLASS="Intro">In the image below, the Project Explorer view is active. </p>
<p CLASS="Intro"><img src="../images/Image1.png" alt="Workbench" border="0" width="800"></p>
<P CLASS="Intro">Clicking on the Outline view causes the Outline's title bar to
become highlighted and the Project Explorer's title bar to no longer be highlighted. The Outline view is now active. </p>
</p>
</BODY>
</HTML>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content=
"Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>Editors and views</title>
</head>
<body bgcolor="#FFFFFF">
<h1>Editors and views</h1>
<p class="Intro">Prior to commencing the Workbench tutorials found in this section, it is important to first be
familiar with the various elements of the Workbench. A Workbench consists of:</p>
<ul>
<li>perspectives</li>
<li>views</li>
<li>editors</li>
</ul>
<p class="Intro">A perspective is a group of views and editors in the Workbench window. One or more perspectives can
exist in a single Workbench window. Each perspective contains one or more views and editors. Within a window, each
perspective may have a different set of views but all perspectives share the same set of editors.</p>
<p class="Intro">A view is a visual component within the Workbench. It is typically used to navigate a list or
hierarchy of information (such as the resources in the Workbench), or display properties for the active editor.
Modifications made in a view are saved immediately.</p>
<p class="Intro">An editor is also a visual component within the Workbench. It is typically used to edit or browse a
resource. The visual presentation might be text or a diagram. Typically, editors are launched by clicking on a
resource in a view. Modifications made in an editor follow an open-save-close lifecycle model.</p>
<p class="Intro">Some features are common to both views and editors. We use the term "part" to mean either a view or
an editor. Parts can be active or inactive, but only one part can be active at any one time. The active part is the
one whose title bar is highlighted. The active part is the target for common operations like cut, copy and paste. The
active part also determines the contents of the status line. If an editor tab is not highlighted it indicates the
editor is not active, however views may show information based on the last active editor.</p>
<p class="Intro">In the image below, the Project Explorer view is active.</p>
<p class="Intro"><img src="../images/Image1.png" alt="Workbench" border="0" width="800"></p>
<p class="Intro">Clicking on the Outline view causes the Outline's title bar to become highlighted and the Project
Explorer's title bar to no longer be highlighted. The Outline view is now active.</p>
</body>
</html>

0 comments on commit 3eea3a3

Please sign in to comment.