View | Details | Raw Unified | Return to bug 236581 | Differences between
and this patch

Collapse All | Expand All

(-)guide/firstplugin_create.htm (-1 / +1 lines)
Lines 22-28 Link Here
22
  Eclipse SDK provides tooling specific for plug-in development.  We'll walk 
22
  Eclipse SDK provides tooling specific for plug-in development.  We'll walk 
23
  through the steps for building our plug-in with the Eclipse SDK, since this is the 
23
  through the steps for building our plug-in with the Eclipse SDK, since this is the 
24
  typical case. If you are not already familiar with the Eclipse workbench and the Java IDE, 
24
  typical case. If you are not already familiar with the Eclipse workbench and the Java IDE, 
25
  consult the Java Development User Guide or PDE Guide for further explanations of the steps 
25
  consult the Java development user guide or PDE guide for further explanations of the steps 
26
  we are taking. For now we are focusing on the code, not the tool; 
26
  we are taking. For now we are focusing on the code, not the tool; 
27
  however, there are some IDE logistics for getting started.</P>
27
  however, there are some IDE logistics for getting started.</P>
28
<h3>Creating your plug-in project</h3>
28
<h3>Creating your plug-in project</h3>
(-)guide/runtime_content_contributing.htm (-1 / +1 lines)
Lines 115-121 Link Here
115
  by using content type aliasing. A <em>content type alias</em> is a placeholder 
115
  by using content type aliasing. A <em>content type alias</em> is a placeholder 
116
  for another preferred content type whose availability is not guaranteed. For 
116
  for another preferred content type whose availability is not guaranteed. For 
117
  instance, the Runtime declares an alias (<code>org.eclipse.core.runtime.properties</code>) 
117
  instance, the Runtime declares an alias (<code>org.eclipse.core.runtime.properties</code>) 
118
  for the Java properties content type provided by the Java Development Tooling 
118
  for the Java properties content type provided by the Java development tooling 
119
  (<code>org.eclipse.jdt.core.javaProperties</code>):</p>
119
  (<code>org.eclipse.jdt.core.javaProperties</code>):</p>
120
<pre>&lt;!-- a placeholder for setups where JDT's official type is not available --&gt;			<br>&lt;content-type 
120
<pre>&lt;!-- a placeholder for setups where JDT's official type is not available --&gt;			<br>&lt;content-type 
121
	id=&quot;properties&quot; 
121
	id=&quot;properties&quot; 
(-)guide/arch_struct.htm (-1 / +1 lines)
Lines 109-115 Link Here
109
providing specialized features for editing, viewing, compiling, debugging, and
109
providing specialized features for editing, viewing, compiling, debugging, and
110
running Java code.</P>
110
running Java code.</P>
111
<P >The JDT is installed as a set of plug-ins that are included in the SDK.&nbsp;
111
<P >The JDT is installed as a set of plug-ins that are included in the SDK.&nbsp;
112
The Java Development User Guide describes how to use the Java tools.&nbsp; The JDT Plug-in
112
The Java development user guide describes how to use the Java tools.&nbsp; The JDT Plug-in
113
Developer Guide describes the structure and API of the JDT.</P>
113
Developer Guide describes the structure and API of the JDT.</P>
114
114
115
<H3>
115
<H3>
(-)reference/ref-capabilitiespref.htm (-1 / +1 lines)
Lines 25-31 Link Here
25
<P CLASS="Para"><strong>Note:</strong> Some capability selections have dependencies 
25
<P CLASS="Para"><strong>Note:</strong> Some capability selections have dependencies 
26
  on other capabilities, disabling a required capability while leaving dependant 
26
  on other capabilities, disabling a required capability while leaving dependant 
27
  capabilities enabled will only result in them becoming re-enabled. This is the 
27
  capabilities enabled will only result in them becoming re-enabled. This is the 
28
  case when deselecting Java Development and Core Team Support.</P>
28
  case when deselecting Java development and Core Team Support.</P>
29
<P CLASS="Para">Here is what the Capabilities preference page looks like: </P>
29
<P CLASS="Para">Here is what the Capabilities preference page looks like: </P>
30
30
31
<p><img src="../images/cap-pref.png" alt="Image of Capabilities Preference page" border="0" ></p>
31
<p><img src="../images/cap-pref.png" alt="Image of Capabilities Preference page" border="0" ></p>
(-)reference/ref-73.htm (-2 / +2 lines)
Lines 59-70 Link Here
59
<P CLASS="Para">This command allows you to change the view for your
59
<P CLASS="Para">This command allows you to change the view for your
60
specific needs. You may select filters to apply to the view so that you
60
specific needs. You may select filters to apply to the view so that you
61
can show or hide various artifacts as needed. The default filters
61
can show or hide various artifacts as needed. The default filters
62
available with the Java Development Tools (JDT) is shown below:</P>
62
available with the Java development tools (JDT) is shown below:</P>
63
<P CLASS="Para"><img src="../images/Image276_available_filters.png"
63
<P CLASS="Para"><img src="../images/Image276_available_filters.png"
64
	alt="Available Customizations &gt; Filters dialog" border="0"></P>
64
	alt="Available Customizations &gt; Filters dialog" border="0"></P>
65
<P CLASS="Para">You may also choose the types of content for the view
65
<P CLASS="Para">You may also choose the types of content for the view
66
to show as well. The default content extensions available with the
66
to show as well. The default content extensions available with the
67
Java Development Tools (JDT) is shown below, but your specific extensions
67
Java development tools (JDT) is shown below, but your specific extensions
68
will be determined by your workbench configuration:</P>
68
will be determined by your workbench configuration:</P>
69
<P CLASS="Para"><img src="../images/Image276_available_content.png"
69
<P CLASS="Para"><img src="../images/Image276_available_content.png"
70
	alt="Available Customizations &gt; Content dialog" border="0"></P>
70
	alt="Available Customizations &gt; Content dialog" border="0"></P>

Return to bug 236581