4:31 p.m.
Author: smukhina
Date: 2008-08-27 10:31:10 -0400 (Wed, 27 Aug 2008)
New Revision: 10208
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/hotKey/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/stateAPI/usage.xhtml
Log:
https://jira.jboss.org/jira/browse/RF-398- text on demo site is corrected
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml
===================================================================
---
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml 2008-08-27
13:48:09 UTC (rev 10207)
+++
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml 2008-08-27
14:31:10 UTC (rev 10208)
@@ -152,10 +152,10 @@
</p>
<p>
<b>process</b> attribute allows you to define the components to be
processed
- additionally with the component which is marked as ajaxSingle or wrapped to region.
+ additionally with the component which is marked as ajaxSingle or wrapped to a
region.
Imagine you need to process only two fields in the different parts of view.
- If you wrap the first to region or make nested support component ajaxSingle -
- the second component will not be processed. And if you do not define the first
component
+ If you wrap the first to a region or make nested support component ajaxSingle -
+ the second component will not be processed and if you do not define the first
component
in this way - all the view will be processed. In this case the next simple
constructions
should be used:
</p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/hotKey/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/hotKey/usage.xhtml 2008-08-27
13:48:09 UTC (rev 10207)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/hotKey/usage.xhtml 2008-08-27
14:31:10 UTC (rev 10208)
@@ -15,17 +15,17 @@
<p>
Main component attributes are:
</p>
- <ul>
- <li><b>key</b> - hot key definition <i>("up",
"ctrl+a", etc...)</i></li>
+ <ul>
+ <li><b>key</b> - hot key definition <i>("up",
"ctrl+a", etc...)</i></li>
<li><b>handler</b> - defines callback function for this
hotKey</li>
<li>
<b>selector</b> - JQuerry selector, defines elements which will
process
defined hotKey(<i>html[0] by default</i>)
</li>
- </ul>
+ </ul>
<p>
First example shows you simple <b>hotKey </b>components usage. In order
to enlarge
- or reduce image size - press <i>CTRL + Up/Down</i> combinations. And in
order to
+ or reduce image size - press <i>CTRL + Up/Down</i> combinations. and in
order to
browse between images - use <i>CTRL + left/right</i> keys.
</p>
<fieldset class="demo_fieldset">
@@ -38,8 +38,8 @@
</div>
</fieldset>
<p>
- In next example we've used <b>selector</b> atribute. So the keys will
works
- only if listShuttle component focused.
+ In next example we've used <b>selector</b> attribute. Hence the keys
will work
+ only if listShuttle component is focused.
</p>
<p>
Press <i>right</i> or <i>left</i> keys in order to move some
selected items
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/stateAPI/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/stateAPI/usage.xhtml 2008-08-27
13:48:09 UTC (rev 10207)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/stateAPI/usage.xhtml 2008-08-27
14:31:10 UTC (rev 10208)
@@ -10,32 +10,32 @@
<style>
.rich-message-label{
color:red;
- }
+ }
</style>
<p>
- Rich Faces State API allows easily define some set of states for the pages and any
- properties sets for this states.
+ Rich Faces State API allows easily to define some set of states for the pages and any
+ properties sets for these states.
</p>
<p>
- Imagine one state as a set of named value bindings method bindings and some
- additional properties to be used after the state activated. So you could define
- inputs values, controls labels and actions, rendering conditions and etc
+ Imagine one state as a set of named value-bindings method-bindings and some
+ additional properties to be used after the state is activated. Hence you could
define
+ inputs values, controls labels and actions, rendering conditions and etc.
using the same state variables which will have different values for every state.
</p>
<p>
- Next small example panel
- has two states: <b>login</b> and <b>register</b>. Lets list
the changes between
+ The next small example panel
+ has two states: <b>login</b> and <b>register</b>.
Let's list the changes between
login and register.
</p>
<ul>
<li>
- Confirmation field for password should appears in register state.
+ Confirmation field for password should appear in a register state
</li>
<li>
- Method bindings should differs for the action button in every state.
+ Method bindings should differ for the action button in every state
</li>
<li>
- Value bindings for the fields could be different between states.
+ Value bindings for the fields could be different between states
</li>
<li>
Some labels should be changed between states
@@ -97,20 +97,20 @@
</div>
</fieldset>
<p>
- Actually states is a map where the entry key is name of the state and value
- is state map. Concrete state map has entries with some names as keys and
- any objects as values. So any value or method bindings or just simple state
+ Actually states are a map where the entry key is a name of the state and value
+ is a state map. Particular state map has entries with some names as keys and
+ any objects as values. Thus any value or method bindings or just simple state
constants could be saved in State map.
</p>
<p>
- Rich Faces state API implements states change as standard JSF navigation.
- Action component should just return outcome and our extension for JSF
- navigation handler will check if this outcome registered as state change
- outcome. If such state change outcome found - corresponding state will be
- activated and in other case - it will call standard navigation handling
+ Rich Faces state API implements states change as a standard JSF navigation.
+ Action component should just return outcome, and our extension for JSF
+ navigation handler will check whether this outcome is registered as state change
+ outcome. If such state change outcome is found, the corresponding state will be
+ activated and in other case, it will call standard navigation handling
</p>
<p>
- There is step by step instructions how configure Rich Faces states
+ There is step by step instructions telling how to configure Rich Faces states
manager for existing JSF application in details tab.
</p>
</ui:define>