You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by ma...@apache.org on 2008/07/02 07:16:51 UTC
svn commit: r673283 -
/myfaces/trinidad/trunk_1.2.x/src/site/xdoc/devguide/configuration.xml
Author: matzew
Date: Tue Jul 1 22:16:50 2008
New Revision: 673283
URL: http://svn.apache.org/viewvc?rev=673283&view=rev
Log:
corrected small typo from old ADF Faces days.
Modified:
myfaces/trinidad/trunk_1.2.x/src/site/xdoc/devguide/configuration.xml
Modified: myfaces/trinidad/trunk_1.2.x/src/site/xdoc/devguide/configuration.xml
URL: http://svn.apache.org/viewvc/myfaces/trinidad/trunk_1.2.x/src/site/xdoc/devguide/configuration.xml?rev=673283&r1=673282&r2=673283&view=diff
==============================================================================
--- myfaces/trinidad/trunk_1.2.x/src/site/xdoc/devguide/configuration.xml (original)
+++ myfaces/trinidad/trunk_1.2.x/src/site/xdoc/devguide/configuration.xml Tue Jul 1 22:16:50 2008
@@ -153,39 +153,39 @@
may affect other users negatively)</li>
</ul>
</p>
- </subsection>
- <subsection name="accessibility-profile">
-<p>
-The <code><accessibility-profile></code> element defines finer-grained
-accessibility preferences than is possible to support with the acccessibility
-mode. Accepted values are:
-</p>
-<p>
-<ul>
-<li>"high-contrast": Indicates that the end user prefers high contrast-friendly content.</li>
-<li>"large-fonts": Indicates that the end user prefers large fonts (larger fonts than the default font size provided by the skin).</li>
-</ul>
-</p>
-<p>
-Multiple values may be specified using whitespace to separate the values, eg:
-</p>
-<source><![CDATA[
- <!-- Enable both high-contrast and large-fonts content -->
- <accessibility-profile>high-contrast large-fonts</accessibility-profile>
-]]>
-</source>
-<p>
-Since accessibility preferences are user-specific, the accessibility-profile is typically bound, similar to the accessibility-mode. The preferences specified by the accessibility profile can be used at runtime to tune both styles/icons defined by the skin as well as the content produced by Renderers.
-</p>
-<p>
-The typical use case for the "high-contrast" preference is to work around issues relating to CSS background images when platform/browser high contrast features are enabled. For example, when Windows High Contrast mode is enabled (Control Panel->Accessibility Options->Display->High Contrast->Use High Contrast), all background images are hidden. In cases where background images are used to convey information, this information is lost to high contrast users. The high-contrast accessibility profile option allows skin implementations to replace such background images with <img> element-based icons, thus avoiding the loss of information.
-</p>
-<p>
-The typical use case for the "large-fonts" preference is to allow skins which specify small or non-scalable fonts (eg. px-based fonts on IE) to provide an alternate set of fonts for users who find the default fonts insufficient.
-</p>
-<p>
-Note that at the moment, the Trinidad core renderers/skins do not yet take advantage of the accessibility profile preferences. These properties are primarily provided for skin authors who wish to design skins which provide styles/icons optimized for high contrast/large font users.
-</p>
+ </subsection>
+ <subsection name="accessibility-profile">
+<p>
+The <code><accessibility-profile></code> element defines finer-grained
+accessibility preferences than is possible to support with the acccessibility
+mode. Accepted values are:
+</p>
+<p>
+<ul>
+<li>"high-contrast": Indicates that the end user prefers high contrast-friendly content.</li>
+<li>"large-fonts": Indicates that the end user prefers large fonts (larger fonts than the default font size provided by the skin).</li>
+</ul>
+</p>
+<p>
+Multiple values may be specified using whitespace to separate the values, eg:
+</p>
+<source><![CDATA[
+ <!-- Enable both high-contrast and large-fonts content -->
+ <accessibility-profile>high-contrast large-fonts</accessibility-profile>
+]]>
+</source>
+<p>
+Since accessibility preferences are user-specific, the accessibility-profile is typically bound, similar to the accessibility-mode. The preferences specified by the accessibility profile can be used at runtime to tune both styles/icons defined by the skin as well as the content produced by Renderers.
+</p>
+<p>
+The typical use case for the "high-contrast" preference is to work around issues relating to CSS background images when platform/browser high contrast features are enabled. For example, when Windows High Contrast mode is enabled (Control Panel->Accessibility Options->Display->High Contrast->Use High Contrast), all background images are hidden. In cases where background images are used to convey information, this information is lost to high contrast users. The high-contrast accessibility profile option allows skin implementations to replace such background images with <img> element-based icons, thus avoiding the loss of information.
+</p>
+<p>
+The typical use case for the "large-fonts" preference is to allow skins which specify small or non-scalable fonts (eg. px-based fonts on IE) to provide an alternate set of fonts for users who find the default fonts insufficient.
+</p>
+<p>
+Note that at the moment, the Trinidad core renderers/skins do not yet take advantage of the accessibility profile preferences. These properties are primarily provided for skin authors who wish to design skins which provide styles/icons optimized for high contrast/large font users.
+</p>
</subsection>
<subsection name="oracle-help-servlet-url">
<p>
@@ -476,7 +476,7 @@
result of evaluating an EL expression - it's the EL expression
itself. So, when you see:
<source><![CDATA[
- <af:outputText value="#{mybean.value}"/>
+ <tr:outputText value="#{mybean.value}"/>
]]>
</source>
... all that's being saved is "#{mybean.value}", and that state is
@@ -525,11 +525,11 @@
<h:outputText value="You're in an English locale"/>
</c:if>
- <af:selectOneListbox value="#{someValue}">
- <af:forEach var="item" items="#{model.listOfItems}">
- <af:selectItem value="#{item.value}" text="#{item.text}"/>
- </af:forEach>
- </af:selectOneListbox>
+ <tr:selectOneListbox value="#{someValue}">
+ <tr:forEach var="item" items="#{model.listOfItems}">
+ <tr:selectItem value="#{item.value}" text="#{item.text}"/>
+ </tr:forEach>
+ </tr:selectOneListbox>
]]>
</source>
The <c:if> will show "You're in an English locale" if the locale's
@@ -543,7 +543,7 @@
rendered="#{user.locale.language == 'en'}"/>
]]>
</source>
-The example using <af:forEach> is less clear-cut, and
+The example using <tr:forEach> is less clear-cut, and
less easily resolved. If "model.listOfItems" always has the
same <em>number</em> of items when a page gets shown at first,
then there are no issues with this particular code sample. But
@@ -551,9 +551,9 @@
then the page, as written, cannot support the Application View Cache.
In this particular case, there's also a simple workaround:
<source><![CDATA[
- <af:selectOneListbox value="#{someValue}">
+ <tr:selectOneListbox value="#{someValue}">
<f:selectItems value="#{model.listOfSelectItems}"/>
- </af:selectOneListbox>
+ </tr:selectOneListbox>
]]>
</source>
</p>