[richfaces-svn-commits] JBoss Rich Faces SVN: r2247 - in trunk/samples/richfaces-demo/src/main/webapp/richfaces: keepAlive and 2 other directories.
richfaces-svn-commits at lists.jboss.org
richfaces-svn-commits at lists.jboss.org
Tue Aug 14 09:46:50 EDT 2007
Author: smukhina
Date: 2007-08-14 09:46:50 -0400 (Tue, 14 Aug 2007)
New Revision: 2247
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/bundle/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/script/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/style/usage.xhtml
Log:
http://jira.jboss.com/jira/browse/RF-524
Language correction in richfaces-demo for aj4 component
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/bundle/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/bundle/usage.xhtml 2007-08-14 13:31:39 UTC (rev 2246)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/bundle/usage.xhtml 2007-08-14 13:46:50 UTC (rev 2247)
@@ -9,16 +9,16 @@
<ui:define name="sample">
<p>a4j:loadBundle allows to use reference to bundle messages during the Ajax re-rendering.
- a4j:loadBundle is a substitute for the f:loadBundle in JSF 1.1 which is not a JSF component originally.
- f:loadBundle is a jsp tag that load the bundle messages into the request scope when page is
+ a4j:loadBundle is a substitution for the f:loadBundle in JSF 1.1 which is not originally a JSF component.
+ f:loadBundle is a jsp tag that loads the bundle messages into the request scope when page is
rendered. As soon as each Ajax request works in own request scope, the bundles loaded with
f:loadBundle are unavailable.
</p>
<p>Instead of f:loadBundle that might be located anywhere on the page, the a4j:loadBundle
- should be declared inside the f:view (this does not matter in case on using Facelets)
+ should be declared inside the f:view (this does not matter in case of using Facelets)
</p>
- <p>JSF 1.2 introduces the bundle registered in the faces-config.xml. This fixed the problem
+ <p>JSF 1.2 introduces the bundle registered in the faces-config.xml. This fixes the problem
with f:loadBundle. Therefore, you can use this JSF 1.2 way to declare your bundles.
</p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/usage.xhtml 2007-08-14 13:31:39 UTC (rev 2246)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/usage.xhtml 2007-08-14 13:46:50 UTC (rev 2247)
@@ -12,23 +12,22 @@
a4j:keepAlive extends the live cycle for request scope beans. In general, each Ajax
request works inside the own request scope. Therefore, the state of the component
tree rendered based on the variable from one request scope does not correspond to the
- state of the same tree processed during the next Ajax request. This causes on of
- the most popular problem when the form elements (buttons or fields) appear on
- the page after the previous Ajax response will not processed during after that if
- 'rendered' attribute reference to the request scope variable.
+ state of the same tree processed during the next Ajax request. This causes one of
+ the most widespread problem when the form elements (buttons or fields) can't be correctly proceeded with Ajax if the 'rendered' attribute is mapped to the request scoped variable
+
</p>
- <p>Using the session scope variables solved the problem mentioned above. However,
+ <p>Using the session scope variables solves the above mentioned problem. However,
using a session scope might be inappropriate from the architectural point of view.
- a4j:keepAlive allows to reuse the same value for request scope bean between
- the several Ajax requests.
+ a4j:keepAlive allows to reuse the same value for a request scope bean between
+ several Ajax requests.
</p>
<p>
- <b>beanName</b> attribute references to the requesr scope bean name you want
+ <b>beanName</b> attribute references to a request scope bean name you'd like
to re-use during the Ajax requests.
</p>
- <p><b>ajaxOnly</b> attribute is a flag that declare should the value of the bean
- still be available during the non-Ajax request. If ajaxOnly="true", the request
- scope bean will keep the same value during the Ajax requests from given page, but
+ <p><b>ajaxOnly</b> attribute is a flag that declares whether the value of the bean
+ should be available during a non-Ajax request. If ajaxOnly="true", a request
+ scope bean will keep the same value during Ajax requests from the given page, but
it will be re-created as a regular request scope bean when a non-Ajax request
will send from this page.
</p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/script/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/script/usage.xhtml 2007-08-14 13:31:39 UTC (rev 2246)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/script/usage.xhtml 2007-08-14 13:46:50 UTC (rev 2247)
@@ -8,17 +8,17 @@
<ui:composition template="/templates/component-sample.xhtml">
<ui:define name="sample">
- <p>a4j:loadScript is similar to the standard script tag with src attribute, but allows
- to load script from alternative sources like jar file.
+ <p>a4j:loadScript is similar to the standard script tag with src attribute, but it allows
+ to load script from alternative sources like a jar file.
</p>
<p>
<b>src</b> attribute defines the context relative path to the script. Instead of html
- script tag you do not have to have a prefix to your application. The leading slash in
+ script tag it's not required to have a prefix of your application. The leading slash in
the path means the root of the web context.
</p>
<p>
- You can use "resource://" prefix to access to the script file using
- RichFaces resource framework. For example, if you script file is located inside the
+ You can use "resource://" prefix to access the script file using
+ RichFaces resource framework. For example, if your script file is located inside the
jar file and has a full path there: /org/mycompany/assets/script/focus.js , you can
point to it with:
<pre style="margin:0px">
@@ -26,10 +26,10 @@
</pre>
</p>
<p>
- It is possible to register aliases to the static script files or dynamically
+ It is possible to register aliases in the static script files or dynamically
generated scripts and use those aliases then. For example, RichFaces has an
- alias to the prototype.js script. So, you can point to "resource://prototype.js" as
- a src for loading script and use prototype's features. The following example
+ alias for the prototype.js script. So, you can point to "resource://prototype.js" as
+ a src for loading script and use prototype features. The following example
shows how to use shipped with RichFaces prototype.js and script.aculo.us to create
a client-side effects.
</p>
@@ -46,12 +46,12 @@
<p>
- Note that if you have an Ajax functionality on the page, the prototype.js is already
- attached to this page and you do not have to include it explicitly once more.
+ Note that if you have an Ajax functionality on a page, the prototype.js is already
+ attached to this page and you do not have to include it explicitly once again.
</p>
<p>
- Since version 3.1.0, RichFaces introduced the rich:effect component. So, you do not have
- to program with javascript to have effects in your application.
+ Since version 3.1.0, RichFaces introduced the rich:effect component. Hence, you do not have
+ to write any javascript to make effects appear in your application.
</p>
</ui:define>
</ui:composition>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/style/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/style/usage.xhtml 2007-08-14 13:31:39 UTC (rev 2246)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/style/usage.xhtml 2007-08-14 13:46:50 UTC (rev 2247)
@@ -8,18 +8,18 @@
<ui:composition template="/templates/component-sample.xhtml">
<ui:define name="sample">
- <p>a4j:loadStyle is similar to the standard style tag with src attribute, but allows
- to load style sheet file from alternative sources like jar file.
+ <p>a4j:loadStyle is similar to the standard style tag with src attribute, but it allows
+ to load a style sheet file from alternative sources like a jar file.
</p>
<p>
<b>src</b> attribute defines the context relative path to the style sheet file. Instead of html
- style tag you do not have to have a prefix to your application. The leading slash in
+ style tag it's not required to have a prefix in your application. The leading slash in
the path means the root of the web context.
</p>
<p>
- You can use "resource://" prefix to access to the file using
- RichFaces resource framework. For example, if you css file is located inside the
- jar file and has a full path there: /org/mycompany/assets/css/common.css , you can
+ You can use "resource://" prefix to access the file using
+ RichFaces resource framework. For example, if your css file is located inside the
+ jar file and has a full path there: /org/mycompany/assets/css/common.css, you can
point to it with:
</p>
<pre style="margin:0px">
@@ -27,10 +27,10 @@
</pre>
<p>
Richfaces allows to have a dynamically generated css file based on RichFaces
- skinability feature. xcss is a XML formated css with some additional extentions.
+ skinability feature. xcss is an XML formated css with some additional extensions.
The following example shows how the look-n-feel of non-RichFaces components might
be changed based on the selected skin. The panel with the form elements consists
- of only non-Richfaces component, but it is sensitive to the current skin.
+ only of non-Richfaces component, but it is sensitive to the current skin.
</p>
More information about the richfaces-svn-commits
mailing list