mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
Bug 269416 [Accessibility] The ALT attribute should be defined for images
This commit is contained in:
parent
d631a9cfb5
commit
6c04054d66
4 changed files with 26 additions and 26 deletions
|
@ -74,7 +74,7 @@ table.MsoTableGrid
|
|||
in the new
|
||||
CDT build system in CDT 4.0</font></td>
|
||||
<td width="28%"><img src="http://dev.eclipse.org/images/Idea.jpg"
|
||||
alt="" height="86" width="120"></td>
|
||||
alt="" height="86" width="120" alt="idea"></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
@ -219,7 +219,7 @@ Model schema</a></p>
|
|||
of the schema elements. It is simplified by leaving out the fact that the
|
||||
configuration, toolChain, tool, targetPlatform, and builder definition elements
|
||||
can be defined at the top level in a manifest file.</p>
|
||||
<p class="MsoNormal" style="margin-top:6.0pt"><img border="0" src="whats_1.gif"></p>
|
||||
<p class="MsoNormal" style="margin-top:6.0pt"><img border="0" src="whats_1.gif" alt="UML model of schema elements"></p>
|
||||
<p> </p>
|
||||
<p class="subsection"><a name="_TocSectionUIModel_2">2.2 New New Project Wizard</a></p>
|
||||
<p>The CDT 4.0 presents a new New Project Wizard. This section primarily
|
||||
|
@ -229,7 +229,7 @@ Project Wizard" user description for more detail on the New Project Wizard
|
|||
<p>The first wizard page presents the wizard allows user to select a project
|
||||
type and tool-chain(s) to be used with the project type.</p>
|
||||
<p> </p>
|
||||
<p><img border="0" src="../../migration_guides/4.0/migrat1.gif"></p>
|
||||
<p><img border="0" src="../../migration_guides/4.0/migrat1.gif" alt="New project wizard dialog"></p>
|
||||
<p><b>Presenting project-types and tool-chains in the New Project Wizard</b></p>
|
||||
<p>A tool-integrator has two options of presenting his project-types in the
|
||||
wizard.</p>
|
||||
|
@ -280,7 +280,7 @@ wizard.</p>
|
|||
<p>In case a tool-integrator is willing his/her project type to be displayed as
|
||||
separate entries with custom names, his project-type definition must specify a
|
||||
"name" property for the project-type, e.g.</p>
|
||||
<p><img border="0" src="whats_3.gif"></p>
|
||||
<p><img border="0" src="whats_3.gif" alt="Project type definition and new project wizard"></p>
|
||||
<p>When the project type entry is selected in the wizard the "Toolchain:"
|
||||
pane will display the list of tool-chains defined/associated with the project type</p>
|
||||
<p><b>Using general project type entries</b></p>
|
||||
|
@ -316,7 +316,7 @@ the values of the buildArtefactType build property, e.g.</p>
|
|||
buildArtefactType="org.eclipse.cdt.build.core.buildArtefactType.exe"<br>
|
||||
id="cdt.managedbuild.target.gnu.exe"></p>
|
||||
<p> ...</p>
|
||||
<p><img border="0" src="whats_2.gif"></p>
|
||||
<p><img border="0" src="whats_2.gif" alt="Build property definition and New project wizard"></p>
|
||||
<p> </p>
|
||||
<p class="subsection"><a name="_TocSectionUIModel_3">2.3 Multi-configuration support for makefile
|
||||
projects</a></p>
|
||||
|
|
|
@ -935,7 +935,7 @@ style='mso-spacerun:yes'>
|
|||
</v:shape><w:wrap type="none"/>
|
||||
<w:anchorlock/>
|
||||
</v:group><![endif]--><![if !vml]><img width=582 height=186
|
||||
src="prebuiltIndexes_files/image001.gif" v:shapes="_x0000_s1046 _x0000_s1045 _x0000_s1047"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
src="prebuiltIndexes_files/image001.gif" alt="IExportProjectProvider interface" v:shapes="_x0000_s1046 _x0000_s1045 _x0000_s1047"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
id="_x0000_i1025" type="#_x0000_t75" style='width:6in;height:135pt'>
|
||||
<v:imagedata croptop="-65520f" cropbottom="65520f"/>
|
||||
</v:shape><span style='mso-element:field-end'></span><![endif]--></p>
|
||||
|
@ -1064,7 +1064,7 @@ style='mso-spacerun:yes'>
|
|||
</v:shape><w:wrap type="none"/>
|
||||
<w:anchorlock/>
|
||||
</v:group><![endif]--><![if !vml]><img width=582 height=342
|
||||
src="prebuiltIndexes_files/image002.gif" v:shapes="_x0000_s1052 _x0000_s1051 _x0000_s1053"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
src="prebuiltIndexes_files/image002.gif" alt="ExportProjectProvider extension point" v:shapes="_x0000_s1052 _x0000_s1051 _x0000_s1053"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
id="_x0000_i1026" type="#_x0000_t75" style='width:6in;height:252pt'>
|
||||
<v:imagedata croptop="-65520f" cropbottom="65520f"/>
|
||||
</v:shape><span style='mso-element:field-end'></span><![endif]--><br clear=all
|
||||
|
@ -1344,7 +1344,7 @@ the previous sections</p>
|
|||
type="#_x0000_t75" style='width:431.25pt;height:321pt'>
|
||||
<v:imagedata src="prebuiltIndexes_files/image003.png" o:title=""/>
|
||||
</v:shape><![endif]--><![if !vml]><img width=575 height=428
|
||||
src="prebuiltIndexes_files/image004.jpg" v:shapes="_x0000_i1027"><![endif]></p>
|
||||
src="prebuiltIndexes_files/image004.jpg" alt="Run configuration, Run an application" v:shapes="_x0000_i1027"><![endif]></p>
|
||||
|
||||
<p class=MsoNormal style='text-align:justify'><o:p> </o:p></p>
|
||||
|
||||
|
@ -1352,7 +1352,7 @@ src="prebuiltIndexes_files/image004.jpg" v:shapes="_x0000_i1027"><![endif]></p>
|
|||
type="#_x0000_t75" style='width:431.25pt;height:321pt'>
|
||||
<v:imagedata src="prebuiltIndexes_files/image005.png" o:title=""/>
|
||||
</v:shape><![endif]--><![if !vml]><img width=575 height=428
|
||||
src="prebuiltIndexes_files/image006.jpg" v:shapes="_x0000_i1028"><![endif]></p>
|
||||
src="prebuiltIndexes_files/image006.jpg" alt="Run configuration, Arguments tab" v:shapes="_x0000_i1028"><![endif]></p>
|
||||
|
||||
<p class=MsoNormal style='text-align:justify'><o:p> </o:p></p>
|
||||
|
||||
|
@ -1433,7 +1433,7 @@ style='mso-spacerun:yes'>
|
|||
</v:shape><w:wrap type="none"/>
|
||||
<w:anchorlock/>
|
||||
</v:group><![endif]--><![if !vml]><img width=582 height=277
|
||||
src="prebuiltIndexes_files/image007.gif" v:shapes="_x0000_s1043 _x0000_s1042 _x0000_s1044"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
src="prebuiltIndexes_files/image007.gif" alt="launching Eclipse as a console application" v:shapes="_x0000_s1043 _x0000_s1042 _x0000_s1044"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
id="_x0000_i1029" type="#_x0000_t75" style='width:6in;height:205.5pt'>
|
||||
<v:imagedata croptop="-65520f" cropbottom="65520f"/>
|
||||
</v:shape><span style='mso-element:field-end'></span><![endif]--></p>
|
||||
|
@ -1538,7 +1538,7 @@ style='mso-spacerun:yes'>
|
|||
</v:shape><w:wrap type="none"/>
|
||||
<w:anchorlock/>
|
||||
</v:group><![endif]--><![if !vml]><img width=582 height=470
|
||||
src="prebuiltIndexes_files/image008.gif" v:shapes="_x0000_s1040 _x0000_s1039 _x0000_s1041"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
src="prebuiltIndexes_files/image008.gif" alt="invoking via an Ant script" v:shapes="_x0000_s1040 _x0000_s1039 _x0000_s1041"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
id="_x0000_i1030" type="#_x0000_t75" style='width:6in;height:348pt'>
|
||||
<v:imagedata croptop="-65520f" cropbottom="65520f"/>
|
||||
</v:shape><span style='mso-element:field-end'></span><![endif]--></p>
|
||||
|
@ -1643,7 +1643,7 @@ style='mso-spacerun:yes'>
|
|||
</v:shape><w:wrap type="none"/>
|
||||
<w:anchorlock/>
|
||||
</v:group><![endif]--><![if !vml]><img width=618 height=174
|
||||
src="prebuiltIndexes_files/image009.gif" v:shapes="_x0000_s1037 _x0000_s1036 _x0000_s1038"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
src="prebuiltIndexes_files/image009.gif" alt="IReadOnlyPDOMProvider and IPDOMDescriptor interface " v:shapes="_x0000_s1037 _x0000_s1036 _x0000_s1038"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
id="_x0000_i1031" type="#_x0000_t75" style='width:459pt;height:126pt'>
|
||||
<v:imagedata croptop="-65520f" cropbottom="65520f"/>
|
||||
</v:shape><span style='mso-element:field-end'></span><![endif]--></p>
|
||||
|
@ -1736,7 +1736,7 @@ style='mso-spacerun:yes'>
|
|||
</v:shape><w:wrap type="none"/>
|
||||
<w:anchorlock/>
|
||||
</v:group><![endif]--><![if !vml]><img width=582 height=222
|
||||
src="prebuiltIndexes_files/image010.gif" v:shapes="_x0000_s1049 _x0000_s1048 _x0000_s1050"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
src="prebuiltIndexes_files/image010.gif" alt="ReadOnlyPDOMProvider extension point" v:shapes="_x0000_s1049 _x0000_s1048 _x0000_s1050"><![endif]><!--[if mso & !supportInlineShapes & supportFields]><v:shape
|
||||
id="_x0000_i1032" type="#_x0000_t75" style='width:6in;height:162pt'>
|
||||
<v:imagedata croptop="-65520f" cropbottom="65520f"/>
|
||||
</v:shape><span style='mso-element:field-end'></span><![endif]--><br clear=all
|
||||
|
|
|
@ -322,7 +322,7 @@ mso-bidi-language:AR-SA'><br clear=all style='page-break-before:always'>
|
|||
|
||||
<p class=MsoNormal align=center style='text-align:center'><img border=0
|
||||
width=421 height=653 id="_x0000_i1025"
|
||||
src="prebuiltVersioning_files/image001.jpg"></p>
|
||||
src="prebuiltVersioning_files/image001.jpg" alt="example scenario"></p>
|
||||
|
||||
<p class=MsoNormal align=center style='text-align:center'> </p>
|
||||
|
||||
|
|
|
@ -73,7 +73,7 @@ System Extensibility Document</font><br>
|
|||
<font class="indexsub">This document describes the design of the
|
||||
managed build system and how to extend it.</font></td>
|
||||
<td width="28%"><img src="http://dev.eclipse.org/images/Idea.jpg"
|
||||
alt="" height="86" width="120"></td>
|
||||
alt="idea" height="86" width="120"></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
@ -4573,7 +4573,7 @@ they are used. The makefile includes external makefiles that have a
|
|||
list of build directories, object files, makefile fragments, and
|
||||
dependency makefiles. </p>
|
||||
<p>
|
||||
<img border="0" src="./image036.gif"></p>
|
||||
<img border="0" src="./image036.gif" alt="generated makefile"></p>
|
||||
<p>This makefile is passed as an argument to <span
|
||||
style="font-style: italic;">make</span>, so it contains
|
||||
<span style="font-style: italic;">clean</span>
|
||||
|
@ -7063,7 +7063,7 @@ page methods).</P>
|
|||
<P class="MsoNormal">For convenience, here is a UML class diagram of the
|
||||
IWizardPage interface.<BR>
|
||||
<BR>
|
||||
<IMG border="0" src="IWizardPage.jpeg" width="176" height="196">
|
||||
<IMG border="0" src="IWizardPage.jpeg" width="176" height="196" alt="UML class diagram of the IWizardPage interface">
|
||||
<BR>
|
||||
<BR><A name="OLE_LINK10"></A><A name="OLE_LINK9"><SPAN
|
||||
style="mso-bookmark:OLE_LINK10">Wizard pages as GUI elements by
|
||||
|
@ -7468,7 +7468,7 @@ allowing the page manager to completely control the ordering of pages.</P>
|
|||
<P class="MsoNormal">The following class diagram shows how these
|
||||
new classes fit into the existing wizard system in MBS in terms of class
|
||||
hierarchies and associations.<BR><BR>
|
||||
<IMG border="0" src="classdiagram.jpeg" width="1454" height="1711">
|
||||
<IMG border="0" src="classdiagram.jpeg" width="1454" height="1711" alt="High level view of MBS wizard system">
|
||||
</P>
|
||||
<H5>Figure 12: High level view of MBS wizard system</H5>
|
||||
<P><BR>
|
||||
|
@ -7479,7 +7479,7 @@ wizards provided by the CDT's core UI. There are several wizard pages that alway
|
|||
</P>
|
||||
<P><BR>Drilling down into the custom wizard page system itself, we see the following:<BR>
|
||||
<BR>
|
||||
<IMG border="0" src="classdiagram2.jpeg" width="776" height="1052">
|
||||
<IMG border="0" src="classdiagram2.jpeg" width="776" height="1052" alt="High level view of custom wizard system">
|
||||
</P>
|
||||
<H5>Figure 12: High level view of custom wizard system</H5>
|
||||
<P><BR>The MBSCustomPageManager class is the main entry point to the system. It is responsible for loading all of the extensions which provide custom wizard pages, and storing that data for later use by the wizard. It keeps a list of records of these pages (MBSCustomPageData) which act as a repository for everything that needs to be known about the page, including what circumstances it should be shown under, and what actual IWizardPage should be shown when the page is displayed.<BR>
|
||||
|
@ -7524,7 +7524,7 @@ manager can only do so much as it fills the role of an advisor.<SPAN
|
|||
theoretically free to ignore its existence, although this is strongly
|
||||
discouraged.<BR>
|
||||
<BR>
|
||||
<IMG border="0" src="MBSCustomPageManager.jpeg" width="243" height="585">
|
||||
<IMG border="0" src="MBSCustomPageManager.jpeg" width="243" height="585" alt="UML diagram of MBSCustomPageManager">
|
||||
<BR>
|
||||
<BR>
|
||||
|
||||
|
@ -7540,7 +7540,7 @@ for the page manager to store information on a custom wizard page.<SPAN
|
|||
loads all contributions to the newWizardPages extension point, and
|
||||
stores the loaded data in these records for later use. There is a nested class, ToolchainData, which is used to maintain information on each individual toolchain that a given custom page supports. The MBSCustomPage manager calls various methods on this class (e.g. MBSCustomPageData.shouldBeVisibleForNature()) to determine when a given page should be visible in the wizard.<BR>
|
||||
<BR>
|
||||
<IMG border="0" src="MBSCustomPageData.jpeg" width="238" height="604">
|
||||
<IMG border="0" src="MBSCustomPageData.jpeg" width="238" height="604" alt="UML diagram of MBSCustomPageData">
|
||||
</P>
|
||||
<P><BR>
|
||||
<SPAN style="mso-bookmark:
|
||||
|
@ -7559,7 +7559,7 @@ custom pages do not subclass MBSCustomPage then their page
|
|||
implementation must be carefully coded to function properly while still
|
||||
respecting the rules laid out by the page manager.<BR>
|
||||
<BR>
|
||||
<IMG border="0" src="MBSCustomPage.jpeg" width="199" height="234">
|
||||
<IMG border="0" src="MBSCustomPage.jpeg" width="199" height="234" alt="UML diagram of MBSCustomPage">
|
||||
<BR>
|
||||
<BR>7.14.4 Limitations<BR>
|
||||
<BR>
|
||||
|
@ -7603,11 +7603,11 @@ and other ordering constraints.</SPAN></P>
|
|||
</blockquote>
|
||||
<p class="style1">} </p>
|
||||
</blockquote>
|
||||
<a name="_TocSectionTutorial_18">
|
||||
<a name="_TocSectionTutorial_18"></a>
|
||||
<p> </p>
|
||||
<p class="section"><a name="_TocSectionAdvanced"> Advanced Features</a></p>
|
||||
<p class="subsection"><a name="_TocSectionAdvanced_1">8.1 Converting CDT 2.0 Manifest Files</p>
|
||||
</a>
|
||||
<p class="subsection"><a name="_TocSectionAdvanced_1">8.1 Converting CDT 2.0 Manifest Files</a></p>
|
||||
|
||||
<p class="MsoNormal">The CDT 2.1 Managed Build System (MBS) defined a new object
|
||||
model for tool integrators to use when integrating their tool definitions.
|
||||
The CDT 3.0 model is upward compatible with the CDT 2.1 model with the exception
|
||||
|
@ -7618,7 +7618,7 @@ model.</p>
|
|||
object model. The CDT 3.0 object model is shown earlier in the document.</p>
|
||||
<p class="MsoNormal"> <img style="border: 0px solid ;"
|
||||
src="./image004.gif"
|
||||
title="Figure 2 Managed build model elements"
|
||||
title="Figure 12 CDT 2.0 Managed build model elements"
|
||||
alt="UML model of schema elements"></p>
|
||||
<h5>Figure 12 CDT 2.0 Managed build model elements</h5>
|
||||
<p class="MsoNormal">Below are the detailed instructions for converting a
|
||||
|
|
Loading…
Add table
Reference in a new issue