[richfaces-svn-commits] JBoss Rich Faces SVN: r2482 - in trunk/samples/richfaces-demo/src/main/webapp/richfaces: effect and 5 other directories.
richfaces-svn-commits at lists.jboss.org
richfaces-svn-commits at lists.jboss.org
Fri Aug 24 10:59:02 EDT 2007
Author: smukhina
Date: 2007-08-24 10:59:02 -0400 (Fri, 24 Aug 2007)
New Revision: 2482
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/calendar/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/effect/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/include/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/mediaOutput/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/modalPanel/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/togglePanel/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml
Log:
http://jira.jboss.com/jira/browse/RF-524
the language is checked
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/calendar/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/calendar/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/calendar/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -10,9 +10,9 @@
<p>
rich:calendar allows to select the date using monthly calendar elements on pages.
- It is possoble to use the component in popup and inline code. Calendar at popup mode
- initially renders as input for date and button on the right side to call popup.
- In case of inline mode, the monthly calendar is located on the page initially.
+ It is possible to use the component in a popup and inline code. At a popup mode Calendar
+ is initially rendered as input for date and button on the right side to call a popup.
+ In case of an inline mode, the monthly calendar is located on a page initially.
</p>
<div class="sample-container" >
@@ -24,22 +24,22 @@
</div>
<p>
- <b>locale</b> attribute define a Locale. The default value is set to the Locale of current page.
- The name of the month and week days names are depends of the Locale.
+ <b>locale</b> attribute is defined as a Locale. The default value is set to the Locale of the current page.
+ The name of the month and week days names depend of the Locale.
</p>
<p>
- <b>popup</b> attribute is a flag that direct the calendar mode. If true, the popup mode is used.
- Otherwize, the inline mode is set.
+ <b>popup</b> attribute is a flag that directs to the calendar mode. If true, the popup mode is used.
+ Otherwise, the inline mode is set.
</p>
<p>
- <b>showInput</b> attribute defines should the input field be rendered in popup mode. If
+ <b>showInput</b> attribute defines whether the input field should be rendered in a popup mode. If
set to false, only the button (calendar icon) appears on the page.
</p>
<p>
- <b>enableManualInput</b> attribute allows to input the date in the text field manually.
+ <b>enableManualInput</b> attribute allows to input the date in a text field manually.
The default value is false. It means a user can only select the date from the calendar element.
</p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/effect/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/effect/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/effect/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -10,7 +10,7 @@
<p>rich:effect utilizes the set of effects provided by scriptaculous javascript library. It
allows to attach effects to JSF components and html tags. For the reference of the available
- effects and thier parameters see the scriptaculous documentation and wiki. Those are
+ effects and their parameters see the scriptaculous documentation and wiki. There are
some of many possible effects available out-of-the-box:
</p>
<div class="sample-container">
@@ -22,13 +22,13 @@
<p>
It is possible to use rich:effect in two modes:
<ul>
- <li>attached to the JSF components or html tags and triggered by particular event. Wiring
- effect with JSF components might be occurs on the server or client. Wiring with html tag is
+ <li>attached to the JSF components or html tags and triggered by a particular event. Wiring
+ effect with JSF components might occur on the server or the client. Wiring with html tag is
possible only on the client side</li>
- <li>invoking from the javascript code by effect name. During the rendering, rich:effect generates the javascript
- function with defined name. When the function is called, the effect is applied</li>
+ <li>invoking from the javascript code by an effect name. During the rendering, rich:effect generates the javascript
+ function with a defined name. When the function is called, the effect is applied</li>
</ul>
- Those a the typical variants of using:
+ Here are the typical variants of usage:
</p>
<div class="sample-container">
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/include/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/include/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/include/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -9,13 +9,13 @@
<ui:define name="sample">
- <p>a4j:include functionality is equal to the facelets' ui:include functionality, plus, enables the
- partial page navigation in Ajax mode. The standard JSF navigation rules are used to define the
+ <p>a4j:include functionality is equal to the facelets ui:include functionality, plus, it enables the
+ partial page navigation in an Ajax mode. The standard JSF navigation rules are used to define the
navigation between the view.
</p>
<p>
- <b>viewId</b> attribute specify the view id of the page that will be included. It should be
- the full context-relative path of the resource in order to use as from-view and to-view in the
+ <b>viewId</b> attribute specifies the view id of a page that will be included. It should be
+ a full context-relative path of the resource in order to use as from-view and to-view in the
JSF navigation cases.
</p>
@@ -46,12 +46,12 @@
<p>
The Ajax command component (button, link, jsFunction, etc) should be located inside the
- a4j:include in order to having a partial navigation. When the navigation
- performs, the part of the component tree content is replaced with the content of view given
- by navigation rule.
+ a4j:include in order to have a partial navigation. When the navigation is
+ performed, a part of the component tree content is replaced with the content of a view given
+ by a navigation rule.
</p>
<p> The content of the a4j:include is not isolated from the whole view. You can point to the other
- parts of of the view with reRender if you want to update them while you navigate inside the
+ parts of the view with reRender if you want to update them while you navigate inside the
a4j:include.
</p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/mediaOutput/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/mediaOutput/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/mediaOutput/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -11,24 +11,24 @@
<p>a4j:mediaOutput allows to generate images, video, sounds and other binary
resources defined by a user on-the-fly.
</p>
- <p><b>createContent</b> attribute reference to the method that will be used
- for content creating. The method accept two parameters. The first parameter
- has an OutputStream type. It is a reference to the steam should be used for output.
- The second parameter is a reference to 'value' attribute of the component.
+ <p><b>createContent</b> attribute references to the method that will be used
+ for content creating. The method accepts two parameters. The first parameter
+ has an OutputStream type. It is a reference to the steam that should be used for output.
+ The second parameter is a reference to a 'value' attribute of the component.
</p>
<p>
- <b>value</b> attribute references to data can be used as a input data for content
+ <b>value</b> attribute references to data that can be used as a input data for a content
creator method. The data should be serializable because it is encoded to the URL
to the resource.
</p>
<p>
<b>mimeType</b> attribute defines the type of output content. It is used to define
- the corresponded type in the header of HTTP response.
+ the corresponded type in the header of an HTTP response.
</p>
<p>
<b>cacheable</b> attribute is a flag that defines the caching strategy. If 'cachable'
is set to false, the request will be cached. If it is set to true, it will be cached
- and the serialized value of 'value' attribute plays the role of cache key.
+ and the serialized value of 'value' attribute plays the role of a cache key.
</p>
<div class="sample-container" >
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/modalPanel/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/modalPanel/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/modalPanel/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -9,10 +9,10 @@
<ui:define name="sample">
- <p>RichFaces Modal Panel is a container that blocks the operation on the base page when the modal
+ <p>RichFaces Modal Panel is a container that blocks an operation on the base page when the modal
panel is shown.</p>
- <p>You can show the modal panel using the folowing javascript function: Richfaces.hideModalPanel(id, params).
- For example, this line code invoke the modal panel:
+ <p>You can show the modal panel using the following javascript function: Richfaces.hideModalPanel(id, params).
+ For example, this line code invokes the modal panel:
<a href="javascript:Richfaces.showModalPanel('mp',{width:450, top:200})">
Richfaces.showModalPanel('mp',{width:450, top:200})</a></p>
<div class="sample-container">
@@ -24,12 +24,12 @@
</ui:include>
</div>
- <p>The modal panel has absolute layout. Absolutly, no reason to put in on the page
- where it is called. If modal panel has a form element, it should have it own form.
- In this case, it must be declired outside of the other form on the same page.
- I.e. nested form are not allowed.<br/>
- Those requirements apply because due to the bug of earlier Interner Expolrer versions,
- the dialog are moved to the top of the browser DOM tree just after it is rendered.</p>
+ <p>The modal panel has an absolute layout.There is no reason to put in on the page
+ where it is called.If you want to perform submits from this modal panel, you should have a separate form inside it.
+ In this case, the panel must be declared outside of the other form on the same page.
+ I.e. nested forms are not allowed.<br/>
+ Those requirements are applied because of the bug in earlier Internet Explorer versions, as
+ the dialog is moved to the top of the browser DOM tree just after it is rendered.</p>
</ui:define>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/togglePanel/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/togglePanel/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/togglePanel/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -8,23 +8,23 @@
<ui:composition template="/templates/component-sample.xhtml">
<ui:define name="sample">
<p>
- Toggle Panel renders sequence of states, tha can be switched (toggled) by
+ Toggle Panel renders sequence of states that can be switched (toggled) by a
component called Toggle Control. rich:togglePanel has no default appearance.
You can define it using the set of facets with any given content inside.
</p>
<p>
- <b>switchType</b> attribute define the strategy of switching. The possible values for this attributes
+ <b>switchType</b> attribute defines the strategy of switching. The possible values for this attributes
are:
<ul>
<li>client - switching happens on the client without any request to the server.
The jsf form is not required in this mode</li>
- <li>ajax - when state are switched, the content of new states comes from the server in Ajax way.</li>
+ <li>ajax - when states are switched, the content of new states comes from the server in Ajax way.</li>
<li>server - the whole page is reloaded when states are switched</li>
</ul>
</p>
<p>
- <b>stateOrder</b> attribute defines the order of the states if "switchToState" attribute of
- rich:toggleControl. The following example shows tips panel having one closed state and
+ <b>stateOrder</b> attribute defines the order of the states, if "switchToState" isn't explicitly defined on the
+ rich:toggleControl. The following example shows tips panel that has one closed state and
three states for tips.
</p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml 2007-08-24 14:53:16 UTC (rev 2481)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/toolTip/usage.xhtml 2007-08-24 14:59:02 UTC (rev 2482)
@@ -9,14 +9,14 @@
<ui:define name="sample">
<p>
- ToolTip is a little non-modal pop-up that may be used to display additional information, that normally hidden.<br/>
+ ToolTip is a little non-modal pop-up that could be used to display additional information, that is usually hidden.<br/>
Major toolTip features:
</p>
<ul>
- <li>Tool-tip content may be <b>pre-rendered</b> on page (client mode) or <b>loaded in separate Ajax request</b> (ajax mode)</li>
- <li>In "ajax" mode <b>default content</b> may be shown while request is executed</li>
- <li>Parameters can be passed to server during ajax reques</li>
+ <li>Tool-tip content may be <b>pre-rendered</b> on a page (client mode) or <b>loaded on separate Ajax request</b> (ajax mode)</li>
+ <li>In "ajax" mode <b>default content</b> could be shown while request is executed</li>
+ <li>Parameters can be passed to the server during an ajax request</li>
<li>Tooltip <b>look is fully customizable</b> using both - Richfaces skins and CSS style classes</li>
</ul>
More information about the richfaces-svn-commits
mailing list