JBoss Rich Faces SVN: r9613 - trunk/ui/beanValidator/src/main/java/org/richfaces/component.
by richfaces-svn-commits＠lists.jboss.org
Author: dsvyatobatsko
Date: 2008-07-15 10:36:37 -0400 (Tue, 15 Jul 2008)
New Revision: 9613
Modified:
trunk/ui/beanValidator/src/main/java/org/richfaces/component/UIBeanValidator.java
Log:
UIMessages search is narrowed down to the current form if any
Modified: trunk/ui/beanValidator/src/main/java/org/richfaces/component/UIBeanValidator.java
===================================================================
--- trunk/ui/beanValidator/src/main/java/org/richfaces/component/UIBeanValidator.java 2008-07-15 14:21:35 UTC (rev 9612)
+++ trunk/ui/beanValidator/src/main/java/org/richfaces/component/UIBeanValidator.java 2008-07-15 14:36:37 UTC (rev 9613)
@@ -17,12 +17,10 @@
import javax.faces.component.UIComponentBase;
import javax.faces.component.UIInput;
import javax.faces.component.UIMessage;
-import javax.faces.component.UIViewRoot;
import javax.faces.context.FacesContext;
import javax.faces.event.AbortProcessingException;
import javax.faces.event.FacesEvent;
import javax.faces.event.PhaseId;
-import javax.faces.validator.Validator;
import org.ajax4jsf.component.AjaxComponent;
import org.ajax4jsf.component.AjaxContainer;
@@ -31,10 +29,8 @@
import org.ajax4jsf.context.AjaxContext;
import org.ajax4jsf.event.AjaxEvent;
import org.ajax4jsf.event.AjaxListener;
-import org.ajax4jsf.renderkit.AjaxContainerRenderer;
import org.ajax4jsf.renderkit.AjaxRendererUtils;
import org.richfaces.event.ValidationEvent;
-import org.richfaces.validator.FacesBeanValidator;
import com.sun.facelets.FaceletException;
@@ -42,12 +38,12 @@
* JSF component class
*
*/
-public abstract class UIBeanValidator extends UIComponentBase implements AjaxComponent, AjaxSupport,AjaxContainer {
+public abstract class UIBeanValidator extends UIComponentBase implements AjaxComponent, AjaxSupport, AjaxContainer {
public static final String COMPONENT_TYPE = "org.richfaces.BeanValidator";
public static final String COMPONENT_FAMILY = "org.richfaces.BeanValidator";
-
+
public static final String BEAN_VALIDATOR_FACET = "org.richfaces.validator.";
@Override
@@ -82,12 +78,12 @@
FacesContext context = getFacesContext();
if (event instanceof ValidationEvent) {
// ByPass UpdateModelValue
- context.renderResponse();
+ context.renderResponse();
} else if (event instanceof AjaxEvent) {
// TODO - find all UIMessages components for a parent UIInput.
// for an ajaxSingle component, re-render only target message.
- AjaxContext ajaxContext = AjaxContext.getCurrentInstance(context);
- ajaxContext.setSubmittedRegionClientId(this.getClientId(context));
+ AjaxContext ajaxContext = AjaxContext.getCurrentInstance(context);
+ ajaxContext.setSubmittedRegionClientId(this.getClientId(context));
}
}
}
@@ -124,72 +120,80 @@
return getParent();
}
- public void encodeAjax(FacesContext context) throws IOException {
- AjaxContext ajaxContext = AjaxContext.getCurrentInstance(context);
- Set<String> renderedAreas = ajaxContext.getAjaxRenderedAreas();
- List<UIMessage> messages = getMessages(context);
- for (UIMessage message : messages) {
- if (message.isRendered()) {
- message.encodeAll(context);
- renderedAreas.add(message.getClientId(context));
- }
- }
- // Write information about encoded areas after submission.
- AjaxRendererUtils.encodeAreas(context, this);
+ public void encodeAjax(FacesContext context) throws IOException {
+ AjaxContext ajaxContext = AjaxContext.getCurrentInstance(context);
+ Set<String> renderedAreas = ajaxContext.getAjaxRenderedAreas();
+ List<UIMessage> messages = getMessages(context);
+ for (UIMessage message : messages) {
+ if (message.isRendered()) {
+ message.encodeAll(context);
+ renderedAreas.add(message.getClientId(context));
+ }
+ }
+ // Write information about encoded areas after submission.
+ AjaxRendererUtils.encodeAreas(context, this);
+ }
- }
-
- public List<UIMessage> getMessages(FacesContext context){
- ArrayList<UIMessage> messages = new ArrayList<UIMessage>();
- findMessages(context.getViewRoot(),messages);
- return messages;
- }
+ public List<UIMessage> getMessages(FacesContext context) {
+ ArrayList<UIMessage> messages = new ArrayList<UIMessage>();
+ UIComponent form = AjaxRendererUtils.getNestingForm(this);
+ if (null == form) {
+ form = context.getViewRoot();
+ }
+ findMessages(form, messages);
+ return messages;
+ }
- /**
- * Recursive search messages for the parent component.
- * @param component
- * @param messages
- */
- protected void findMessages(UIComponent component, ArrayList<UIMessage> messages) {
- // TODO create more intellectual search, symmenric for an UIMessage algoritm.
- Iterator<UIComponent> facetsAndChildren = component.getFacetsAndChildren();
- while (facetsAndChildren.hasNext()) {
- UIComponent child = (UIComponent) facetsAndChildren.next();
- if (child instanceof UIMessage) {
- UIMessage message = (UIMessage) child;
- String messageFor = message.getFor();
- if(null != messageFor && messageFor.equals(getParent().getId())){
- messages.add(message);
- }
- } else {
- findMessages(child, messages);
- }
- }
- }
+ /**
+ * Recursive search messages for the parent component.
+ *
+ * @param component
+ * @param messages
+ */
+ protected void findMessages(UIComponent component, ArrayList<UIMessage> messages) {
+ // TODO create more intellectual search, symmenric for an UIMessage
+ // algoritm.
+ Iterator<UIComponent> facetsAndChildren = component.getFacetsAndChildren();
+ while (facetsAndChildren.hasNext()) {
+ UIComponent child = (UIComponent) facetsAndChildren.next();
+ if (child instanceof UIMessage) {
+ UIMessage message = (UIMessage) child;
+ String messageFor = message.getFor();
+ if (null != messageFor && messageFor.equals(getParent().getId())) {
+ messages.add(message);
+ }
+ } else {
+ findMessages(child, messages);
+ }
+ }
+ }
- /* (non-Javadoc)
- * @see org.ajax4jsf.event.AjaxSource#addAjaxListener(org.ajax4jsf.event.AjaxListener)
- */
- public void addAjaxListener(AjaxListener listener) {
- // TODO Auto-generated method stub
-
- }
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.ajax4jsf.event.AjaxSource#addAjaxListener(org.ajax4jsf.event.AjaxListener)
+ */
+ public void addAjaxListener(AjaxListener listener) {
+ // TODO Auto-generated method stub
- /* (non-Javadoc)
- * @see org.ajax4jsf.event.AjaxSource#getAjaxListeners()
- */
- public AjaxListener[] getAjaxListeners() {
- // TODO Auto-generated method stub
- return null;
- }
+ }
- /* (non-Javadoc)
- * @see org.ajax4jsf.event.AjaxSource#removeAjaxListener(org.ajax4jsf.event.AjaxListener)
- */
- public void removeAjaxListener(AjaxListener listener) {
- // TODO Auto-generated method stub
-
- }
-
-
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.ajax4jsf.event.AjaxSource#getAjaxListeners()
+ */
+ public AjaxListener[] getAjaxListeners() {
+ // TODO Auto-generated method stub
+ return null;
+ }
+
+ /* (non-Javadoc)
+ * @see org.ajax4jsf.event.AjaxSource#removeAjaxListener(org.ajax4jsf.event.AjaxListener)
+ */
+ public void removeAjaxListener(AjaxListener listener) {
+ // TODO Auto-generated method stub
+
+ }
+
}
16 years, 2 months
JBoss Rich Faces SVN: r9612 - trunk/samples/functions-demo/src/main/webapp/pages.
by richfaces-svn-commits＠lists.jboss.org
Author: nbelaevski
Date: 2008-07-15 10:21:35 -0400 (Tue, 15 Jul 2008)
New Revision: 9612
Modified:
trunk/samples/functions-demo/src/main/webapp/pages/index.jsp
trunk/samples/functions-demo/src/main/webapp/pages/index.xhtml
Log:
findComponent function added to demo
Modified: trunk/samples/functions-demo/src/main/webapp/pages/index.jsp
===================================================================
--- trunk/samples/functions-demo/src/main/webapp/pages/index.jsp 2008-07-15 14:17:11 UTC (rev 9611)
+++ trunk/samples/functions-demo/src/main/webapp/pages/index.jsp 2008-07-15 14:21:35 UTC (rev 9612)
@@ -9,7 +9,7 @@
<f:view>
<f:subview id="view">
<h:form id="myForm">
- <h:inputText id="input" />
+ <h:inputText id="input" value="abc" />
</h:form>
</f:subview>
@@ -19,6 +19,8 @@
<br />
<h:outputText value="#{fn:component('input')}" />
<br />
+ <h:outputText value="#{fn:findComponent('input').value}" />
+ <br />
</f:view>
</body>
</html>
Modified: trunk/samples/functions-demo/src/main/webapp/pages/index.xhtml
===================================================================
--- trunk/samples/functions-demo/src/main/webapp/pages/index.xhtml 2008-07-15 14:17:11 UTC (rev 9611)
+++ trunk/samples/functions-demo/src/main/webapp/pages/index.xhtml 2008-07-15 14:21:35 UTC (rev 9612)
@@ -8,7 +8,7 @@
<f:view>
<f:subview id="view">
<h:form id="myForm">
- <h:inputText id="input" />
+ <h:inputText id="input" value="abc"/>
</h:form>
</f:subview>
@@ -18,5 +18,7 @@
<br />
<h:outputText value="#{fn:component('input')}" />
<br />
+ <h:outputText value="#{fn:findComponent('input').value}" />
+ <br />
</f:view>
</html>
\ No newline at end of file
16 years, 2 months
JBoss Rich Faces SVN: r9611 - in trunk: ui/calendar/src/main/resources/org/richfaces/renderkit/html/scripts and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: pyaschenko
Date: 2008-07-15 10:17:11 -0400 (Tue, 15 Jul 2008)
New Revision: 9611
Modified:
trunk/framework/impl/src/main/javascript/ajaxjsf/JSFAJAX.js
trunk/ui/calendar/src/main/resources/org/richfaces/renderkit/html/scripts/calendar.js
Log:
http://jira.jboss.com/jira/browse/RF-3628
Modified: trunk/framework/impl/src/main/javascript/ajaxjsf/JSFAJAX.js
===================================================================
--- trunk/framework/impl/src/main/javascript/ajaxjsf/JSFAJAX.js 2008-07-15 13:32:06 UTC (rev 9610)
+++ trunk/framework/impl/src/main/javascript/ajaxjsf/JSFAJAX.js 2008-07-15 14:17:11 UTC (rev 9611)
@@ -394,18 +394,43 @@
}
},
- appendNewHeadElements : function(){
+ appendNewHeadElements : function(callback){
// Append scripts and styles to head, if not presented in page before.
- this._appendNewElements("script","src",null,null,["type","language","charset"]);
+ var includes = this._appendNewElements("script","src",null,null,["type","language","charset"]);
var _this = this;
- this._appendNewElements("link","href","class",["component","user"],["type","rev","media"],{"class": "className"},
+ includes.concat( this._appendNewElements("link","href","class",["component","user"],["type","rev","media"],{"class": "className"},
function (element, script) {
//IE requires to re-set rel or href after insertion to initialize correctly
//see http://jira.jboss.com/jira/browse/RF-1627#action_12394642
_this._copyAttribute(element,script,"rel");
}
- );
+ ));
+
+ if ( includes.length == 0) {
+ callback();
+ return;
+ }
+
+ A4J.AJAX.headElementsCounter = includes.length;
+
+ var onReadyStateChange = function () {
+ if (this.readyState == 'loaded' || this.readyState == 'complete') {
+ this.onreadystatechange = null;
+ this.onload = null;
+ callback();
+ }
+ };
+ var onLoad = function () {
+ this.onreadystatechange = null;
+ this.onload = null;
+ callback();
+ };
+ for (var i = 0; i<includes.length; i++)
+ {
+ includes[i].onreadystatechange = onReadyStateChange;
+ includes[i].onload = onLoad;
+ }
},
_appendNewElements : function(tag,href,role,roles,attributes,mappings,callback){
@@ -413,6 +438,7 @@
var newscripts = this.getElementsByTagName(tag);
var oldscripts = document.getElementsByTagName(tag);
var mappedRole = (mappings && mappings[role]) || role;
+ var elements = [];
var roleAnchors = {};
if (roles) {
@@ -483,10 +509,11 @@
if (callback) {
callback(element,script);
}
+ if (tag!="link" || script.type.toLowerCase()=="text/javascript") elements.push(script);
}
}
}
-
+ return elements;
},
_noSessionHref : function(href){
@@ -777,7 +804,16 @@
return false;
};
+A4J.AJAX.processResponseAfterUpdateHeadElements = function (req, ids)
+{
+ for ( var k =0; k < ids.length ; k++ ) {
+ var id = ids[k];
+ LOG.debug("Update page part from call parameter for ID " + id);
+ req.updatePagePart(id, k==ids.length-1);
+ };
+}
+A4J.AJAX.headElementsCounter = 0;
A4J.AJAX.processResponse = function(req) {
var options = req.options;
@@ -816,14 +852,23 @@
}
var idsFromResponse = req.getResponseHeader("Ajax-Update-Ids");
+ var ids;
+
+ var callback = function () {
+ if (A4J.AJAX.headElementsCounter!=0) {
+ LOG.debug("Script "+A4J.AJAX.headElementsCounter+" was loaded");
+ --A4J.AJAX.headElementsCounter;
+ }
+ if (A4J.AJAX.headElementsCounter==0) {
+ A4J.AJAX.processResponseAfterUpdateHeadElements(req, ids);
+ }
+ };
+
// 3 strategy for replace :
// if setted affected parameters - replace its
if( options.affected ) {
- req.appendNewHeadElements();
- for ( var k =0; k < options.affected.length ; k++ ) {
- LOG.debug("Update page part from call parameter for ID " + options.affected[k]);
- req.updatePagePart(options.affected[k], k==options.affected.length-1);
- };
+ ids = options.affected;
+ req.appendNewHeadElements(callback);
// if resopnce contains element with ID "ajax:update" get id's from
// child text element . like :
// <div id="ajax:update" style="display none" >
@@ -834,13 +879,8 @@
} else if( idsFromResponse && idsFromResponse != "" ) {
LOG.debug("Update page by list of rendered areas from response " + idsFromResponse );
// Append scripts and styles to head, if not presented in page before.
- req.appendNewHeadElements();
- var childs = idsFromResponse.split(",");
- for ( var k=0 ; k < childs.length ; k++ ) {
- var id = childs[k];
- LOG.debug("Attempt to update part of page for Id: "+id);
- req.updatePagePart(id, k==childs.length-1);
- };
+ ids = idsFromResponse.split(",");
+ req.appendNewHeadElements(callback);
} else {
// if none of above - error ?
// A4J.AJAX.replace(form.id,A4J.AJAX.findElement(form.id,xmlDoc));
Modified: trunk/ui/calendar/src/main/resources/org/richfaces/renderkit/html/scripts/calendar.js
===================================================================
--- trunk/ui/calendar/src/main/resources/org/richfaces/renderkit/html/scripts/calendar.js 2008-07-15 13:32:06 UTC (rev 9610)
+++ trunk/ui/calendar/src/main/resources/org/richfaces/renderkit/html/scripts/calendar.js 2008-07-15 14:17:11 UTC (rev 9611)
@@ -2,9 +2,6 @@
window.LOG = {warn:function(){}};
}
-if(typeof Effect == 'undefined')
- throw("calendar.js requires including script.aculo.us' effects.js library");
-
if (!window.Richfaces) window.Richfaces={};
Richfaces.Calendar={};
16 years, 2 months
JBoss Rich Faces SVN: r9610 - trunk.
by richfaces-svn-commits＠lists.jboss.org
Author: nbelaevski
Date: 2008-07-15 09:32:06 -0400 (Tue, 15 Jul 2008)
New Revision: 9610
Modified:
trunk/pom.xml
Log:
jboss.org repository added
Modified: trunk/pom.xml
===================================================================
--- trunk/pom.xml 2008-07-15 13:17:28 UTC (rev 9609)
+++ trunk/pom.xml 2008-07-15 13:32:06 UTC (rev 9610)
@@ -104,7 +104,6 @@
</snapshots>
<id>repository.jboss.org</id>
<url>http://repository.jboss.org/maven2</url>
- <layout>legacy</layout>
</repository>
</repositories>
<pluginRepositories>
16 years, 2 months
JBoss Rich Faces SVN: r9609 - trunk.
by richfaces-svn-commits＠lists.jboss.org
Author: nbelaevski
Date: 2008-07-15 09:17:28 -0400 (Tue, 15 Jul 2008)
New Revision: 9609
Modified:
trunk/pom.xml
Log:
jboss.org repository added
Modified: trunk/pom.xml
===================================================================
--- trunk/pom.xml 2008-07-15 12:54:08 UTC (rev 9608)
+++ trunk/pom.xml 2008-07-15 13:17:28 UTC (rev 9609)
@@ -96,6 +96,16 @@
<layout>legacy</layout>
</repository>
+ <repository>
+ <releases />
+ <snapshots>
+ <enabled>false</enabled>
+ <updatePolicy>never</updatePolicy>
+ </snapshots>
+ <id>repository.jboss.org</id>
+ <url>http://repository.jboss.org/maven2</url>
+ <layout>legacy</layout>
+ </repository>
</repositories>
<pluginRepositories>
<pluginRepository>
@@ -215,9 +225,9 @@
.settings/org.eclipse.jdt.ui.prefs
</name>
<content>
- <![CDATA[
- eclipse.preferences.version=1
- org.eclipse.jdt.ui.text.custom_code_templates=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?><templates><template autoinsert\="false" context\="typecomment_context" deleted\="false" description\="Comment for created types" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.typecomment" name\="typecomment">/**\r\n * $${tags}\r\n * <br /><br />\r\n * \r\n * Created $${date}\r\n * @author $${user}\r\n * @since ${project.artifact.selectedVersion.majorVersion}.${project.artifact.selectedVersion.minorVersion}\r\n */\r\n</template><template autoinsert\="false" context\="filecomment_context" deleted\="false" description\="Comment for created Java files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.filecomment" name\="filecomment">/**\r\n * License Agreement.\r\n *\r\n * JBoss RichFaces - Ajax4jsf Component Library\r\n *\r\n * Copyright (C) 2007 Exadel, Inc.\r\n *\r\n * This library is free software; you can redistribute it and/o!
r\r\n * modify it under the terms of the GNU Lesser General Public\r\n * License version 2.1 as published by the Free Software Foundation.\r\n *\r\n * This library is distributed in the hope that it will be useful,\r\n * but WITHOUT ANY WARRANTY; without even the implied warranty of\r\n * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\r\n * Lesser General Public License for more details.\r\n *\r\n * You should have received a copy of the GNU Lesser General Public\r\n * License along with this library; if not, write to the Free Software\r\n * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA\r\n */\r\n</template></templates>
+ <![CDATA[
+ eclipse.preferences.version=1
+ org.eclipse.jdt.ui.text.custom_code_templates=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?><templates><template autoinsert\="false" context\="typecomment_context" deleted\="false" description\="Comment for created types" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.typecomment" name\="typecomment">/**\r\n * $${tags}\r\n * <br /><br />\r\n * \r\n * Created $${date}\r\n * @author $${user}\r\n * @since ${project.artifact.selectedVersion.majorVersion}.${project.artifact.selectedVersion.minorVersion}\r\n */\r\n</template><template autoinsert\="false" context\="filecomment_context" deleted\="false" description\="Comment for created Java files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.filecomment" name\="filecomment">/**\r\n * License Agreement.\r\n *\r\n * JBoss RichFaces - Ajax4jsf Component Library\r\n *\r\n * Copyright (C) 2007 Exadel, Inc.\r\n *\r\n * This library is free software; you can redistribute it and/o!
r\r\n * modify it under the terms of the GNU Lesser General Public\r\n * License version 2.1 as published by the Free Software Foundation.\r\n *\r\n * This library is distributed in the hope that it will be useful,\r\n * but WITHOUT ANY WARRANTY; without even the implied warranty of\r\n * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\r\n * Lesser General Public License for more details.\r\n *\r\n * You should have received a copy of the GNU Lesser General Public\r\n * License along with this library; if not, write to the Free Software\r\n * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA\r\n */\r\n</template></templates>
]]>
</content>
</file>
@@ -385,4 +395,4 @@
</distributionManagement>
</profile>
</profiles>
-</project>
\ No newline at end of file
+</project>
16 years, 2 months
JBoss Rich Faces SVN: r9608 - Plan and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: tkuprevich
Date: 2008-07-15 08:54:08 -0400 (Tue, 15 Jul 2008)
New Revision: 9608
Modified:
trunk/test-applications/qa/Test Plan/ComponentsAssignment.xls
Log:
Modified: trunk/test-applications/qa/Test Plan/ComponentsAssignment.xls
===================================================================
(Binary files differ)
16 years, 2 months
JBoss Rich Faces SVN: r9607 - trunk/docs/userguide/en/src/main/docbook/modules.
by richfaces-svn-commits＠lists.jboss.org
Author: smukhina
Date: 2008-07-15 08:52:28 -0400 (Tue, 15 Jul 2008)
New Revision: 9607
Modified:
trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml
Log:
http://jira.jboss.com/jira/browse/RF-3875
RF guide review
Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2008-07-15 12:51:09 UTC (rev 9606)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2008-07-15 12:52:28 UTC (rev 9607)
@@ -476,7 +476,7 @@
<emphasis>
<property>"eventsQueue"</property>
</emphasis>
- attribute is defined. In addition, Richfaces starts to
+ attribute is defined. In addition, RichFaces starts to
remove from the queue "similar" requests.
"Similar'"requests are the requests produced
by the same event. For example, according to the
@@ -841,7 +841,7 @@
</emphasis>
attribute allows to invoke the JavaScript code right
after the Ajax Response is returned back and the DOM
- tree of the browser is updated. Richfaces registers the
+ tree of the browser is updated. RichFaces registers the
code for further invocation of XMLHTTP request object
before an Ajax request is sent. This means the code will
not be changed during processing of the request on the
@@ -880,7 +880,7 @@
]]></programlisting>
<para>
- Richfaces allows to serialize not only primitive types
+ RichFaces allows to serialize not only primitive types
into JSON format, but also complex types including
arrays and collections. The beans should be serializable
to be refered with
@@ -2303,7 +2303,7 @@
<para>
Skin "plain" was added from 3.0.2 version. It doesn't
- have any parameters. It's necessary for embedding
+ have any parameters. It's necessary for embedding
RichFaces components into existing projecst which have
its own styles.
</para>
@@ -3969,7 +3969,7 @@
<title>XCSS file format</title>
<para>
- XCSS files are the core of Richfaces components
+ XCSS files are the core of RichFaces components
skinnability.
</para>
<para>
@@ -4459,7 +4459,7 @@
<title>Details of Usage</title>
<para>This section will cover some practical aspects of Plug-n-Skin implementation.
- It's assumed that you have read the section of the guide that tells how the new skin using Plug-n-Skin prototype can be created. </para>
+ It's assumed that you have read the section of the guide that tells how the new skin using Plug-n-Skin prototype can be created. </para>
<para>Above all, we need to create a new skin, in order to do that we just have to follow
the steps described in the previous section.</para>
@@ -4506,7 +4506,7 @@
</para>
<para>Thus, it will be demonstrated how to: </para>
<itemizedlist>
- <listitem><para>Recolor the current day's cell background of the <emphasis role="bold">
+ <listitem><para>Recolor the current day's cell background of the <emphasis role="bold">
<property><rich:calendar></property></emphasis> to see how the new skin created with the help of Plug-n-Skin feature affects the style of the component;</para></listitem>
<listitem><para>Recolor a standard HTML submit button;</para></listitem>
16 years, 2 months
JBoss Rich Faces SVN: r9606 - in trunk/docs/userguide/en/src/main/docbook: modules and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: smukhina
Date: 2008-07-15 08:51:09 -0400 (Tue, 15 Jul 2008)
New Revision: 9606
Modified:
trunk/docs/userguide/en/src/main/docbook/included/actionparam.xml
trunk/docs/userguide/en/src/main/docbook/included/comboBox.xml
trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml
trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml
trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml
trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml
trunk/docs/userguide/en/src/main/docbook/included/effect.xml
trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml
trunk/docs/userguide/en/src/main/docbook/included/form.xml
trunk/docs/userguide/en/src/main/docbook/included/include.xml
trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml
trunk/docs/userguide/en/src/main/docbook/included/jQuery.xml
trunk/docs/userguide/en/src/main/docbook/included/mediaOutput.xml
trunk/docs/userguide/en/src/main/docbook/included/menuGroup.desc.xml
trunk/docs/userguide/en/src/main/docbook/included/message.xml
trunk/docs/userguide/en/src/main/docbook/included/orderingList.xml
trunk/docs/userguide/en/src/main/docbook/included/recursiveTreeNodesAdaptor.xml
trunk/docs/userguide/en/src/main/docbook/included/scrollableDataTable.xml
trunk/docs/userguide/en/src/main/docbook/included/toolTip.xml
trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml
trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml
trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml
Log:
http://jira.jboss.com/jira/browse/RF-3875
RF guide review
Modified: trunk/docs/userguide/en/src/main/docbook/included/actionparam.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/actionparam.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/actionparam.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -57,7 +57,7 @@
</emphasis> and <emphasis role="bold">
<property><f:actionListener></property>
</emphasis>.</para>
- <para>At the render phase, it's decoded by parent component (<emphasis role="bold">
+ <para>At the render phase, it's decoded by parent component (<emphasis role="bold">
<property><h:commandLink></property>
</emphasis> or like) as usual. At the process request phase, if the parent component
performs an action event, update the <emphasis><property>"value"</property></emphasis> specified in the <emphasis><property>"assignTo"</property></emphasis>
Modified: trunk/docs/userguide/en/src/main/docbook/included/comboBox.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/comboBox.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/comboBox.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -253,7 +253,7 @@
</para></listitem>
</itemizedlist>
</para>
- <!-- <para>It's possible to handle events for comboBox from JavaScript code. A simplest example of usage JavaScript API is placed below:</para>
+ <!-- <para>It's possible to handle events for comboBox from JavaScript code. A simplest example of usage JavaScript API is placed below:</para>
<para>
<emphasis role="bold">Example:</emphasis>
</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -321,13 +321,13 @@
</emphasis> out from
<emphasis role="bold">
<property><h:outputText></property>
- </emphasis>to provide component's correct work.
+ </emphasis>to provide component's correct work.
</para>
</note>
- <!-- <para>It's possible to handle events for contextMenu from JavaScript code. A simplest example of usage JavaScript API is placed below:</para>
+ <!-- <para>It's possible to handle events for contextMenu from JavaScript code. A simplest example of usage JavaScript API is placed below:</para>
<para>
<emphasis role="bold">Example:</emphasis>
</para>
@@ -428,14 +428,14 @@
<property>"action"</property>
</emphasis> and <emphasis>
<property>"actionListener"</property>
- </emphasis> item's attributes are ignored. Menu items don't fire any submits
+ </emphasis> item's attributes are ignored. Menu items don't fire any submits
themselves. The behavior is fully defined by the components nested inside items.</para>
<template
<para>emphasis role="bold">
<property><contextMenu></property>
</emphasis> could not be generated for every component where it's defined. Templating could
be used instead. So only representation data could be loaded from server. And markup
- could be evaluated on client side. So it's should accept macrosubstitutions like
+ could be evaluated on client side. So it's should accept macrosubstitutions like
{value} </para>
</para-->
Modified: trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -133,7 +133,7 @@
<property><rich:dataFilterSlider></property>
</emphasis> component has no skin parameters and special <emphasis>
<property>style classes</property></emphasis>, as it consists of one element generated with a your method on the server. To
- define some style properties such as an indent or a border, it's possible to use <emphasis>
+ define some style properties such as an indent or a border, it's possible to use <emphasis>
<property>"style"</property>
</emphasis> and <emphasis>
<property>"styleClass"</property>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -267,7 +267,7 @@
<para>The <emphasis role="bold"><property><rich:dragIndicator></property></emphasis> component has no skin parameters and special <emphasis>
<property>style classes</property></emphasis>, as it consists of one element
generated with a your method on the server. To define some style properties such as an indent
- or a border, it's possible to use <emphasis>
+ or a border, it's possible to use <emphasis>
<property>"style"</property></emphasis> and <emphasis>
<property>"styleClass"</property></emphasis> attributes on the component.</para>
</section>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -98,7 +98,7 @@
The
<property>dragSupport</property>
tag inside a component completely specifies the events and
- JavaScript required to use the component and it's children
+ JavaScript required to use the component and it's children
for dragging as part of a drag-and-drop operation. In order
to work, though,
<property>dragSupport</property>
Modified: trunk/docs/userguide/en/src/main/docbook/included/effect.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/effect.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/effect.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -145,10 +145,10 @@
<emphasis>
<property>"for"</property>
</emphasis> attribute defines the id of the component or html tag, the effect is attached
- to. Richfaces converts the <emphasis>
+ to. RichFaces converts the <emphasis>
<property>"for"</property>
</emphasis> attribute value to the client id of the component if such component is found. If
- not, the value is left as is for possible wiring with on the DOM element's id on the client
+ not, the value is left as is for possible wiring with on the DOM element's id on the client
side. By default, the target of the effect is the same element that effect pointed to.
However, the target element is might be overridden with <emphasis>
<property>"targetId"</property>
Modified: trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -357,7 +357,7 @@
</imageobject>
</mediaobject>
</figure>
- <para>It's possible to handle events for fileUpload using JavaScript code. A simplest example of usage JavaScript API is placed below:</para>
+ <para>It's possible to handle events for fileUpload using JavaScript code. A simplest example of usage JavaScript API is placed below:</para>
<para>
<emphasis role="bold">Example:</emphasis>
</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/form.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/form.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/form.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -87,7 +87,7 @@
]]></programlisting>
<para>This example shows that in order to make <emphasis role="bold">
<property><t:datascroller></property>
- </emphasis> submissions to be Ajax ones it's required only to place this <emphasis role="bold">
+ </emphasis> submissions to be Ajax ones it's required only to place this <emphasis role="bold">
<property><t:datascroller></property>
</emphasis> into <emphasis role="bold">
<property><a4j:form></property>
Modified: trunk/docs/userguide/en/src/main/docbook/included/include.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/include.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/include.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -56,7 +56,7 @@
<a4j:commandButton action="next" reRender="wizard"/>
...
]]></programlisting>
-<para>And in faces-config it's defined:</para>
+<para>And in faces-config it's defined:</para>
<para>
<emphasis role="bold">Example:</emphasis>
Modified: trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -137,7 +137,7 @@
if the attribute is
"true"
after the current value reaches the border value
- it's be reversed to another border value after next
+ it's be reversed to another border value after next
increasing/decreasing. In other case possibilities
of next increasing/decreasing are locked
</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/jQuery.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/jQuery.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/jQuery.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -240,7 +240,7 @@
<para>In addition, RichFaces allows using either a component id or client id if you apply the
query to a JSF component. When you define a selector, RichFaces examines its content and
- tries to replace the defined in the selector id with a component id if it's found.</para>
+ tries to replace the defined in the selector id with a component id if it's found.</para>
<para>For example, you have the following code:</para>
<programlisting role="XML"><![CDATA[...
Modified: trunk/docs/userguide/en/src/main/docbook/included/mediaOutput.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/mediaOutput.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/mediaOutput.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -100,7 +100,7 @@
<note><title>Note:</title><para>A bean class transmitted into value should <code>implement Serializable</code> interface.
</para>
</note>
- <para>Hence, when using the component it's possible to output your data of any type on a page with Ajax requests.</para>
+ <para>Hence, when using the component it's possible to output your data of any type on a page with Ajax requests.</para>
</section>
<section>
Modified: trunk/docs/userguide/en/src/main/docbook/included/menuGroup.desc.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/menuGroup.desc.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/menuGroup.desc.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -21,7 +21,7 @@
<title>Key Features</title>
<itemizedlist>
<listitem><para>Highly customizable look-and-feel</para></listitem>
- <listitem><para>Grouping of any menu's items</para></listitem>
+ <listitem><para>Grouping of any menu's items</para></listitem>
<listitem><para>Pop-up appearance event customization</para></listitem>
<listitem><para>Support for disabling</para></listitem>
<listitem><para>Smart user-defined positioning</para></listitem>
Modified: trunk/docs/userguide/en/src/main/docbook/included/message.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/message.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/message.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -74,7 +74,7 @@
<para> The component has the same behavior as standard <emphasis role="bold">
<property><h:message></property>
</emphasis>component except next two features: <itemizedlist>
- <listitem><para>It's ajaxRendered. It means that the component is reRendered after Ajax request
+ <listitem><para>It's ajaxRendered. It means that the component is reRendered after Ajax request
automatically without outputPanel usage</para></listitem>
<listitem><para>The component optionally provides "passed" state which will be shown if no message is displayed</para></listitem>
<listitem><para>Provides possibility to add some marker to message. By default a marker element
Modified: trunk/docs/userguide/en/src/main/docbook/included/orderingList.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/orderingList.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/orderingList.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -107,7 +107,7 @@
<para> The <emphasis>
<property>"selection" </property>
</emphasis> attribute stores the collection of items selected by you. In the example
- below after submitting the form the current collection is placed in the object's
+ below after submitting the form the current collection is placed in the object's
property and then <emphasis role="bold">
<property><rich:dataTable></property>
</emphasis> with selected items is shown. </para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/recursiveTreeNodesAdaptor.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/recursiveTreeNodesAdaptor.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/recursiveTreeNodesAdaptor.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -199,7 +199,7 @@
<para>
<emphasis><property>"for"</property></emphasis> attribute defines the id of the component or html tag, the effect will be attached to.
Richfaces converts the <emphasis><property>"for"</property></emphasis> attribute value to the client id of the component if such component is found. If not, the value is left as is for possible
-wiring with on the DOM element's id on the client side.
+wiring with on the DOM element's id on the client side.
By default, the target of the effect is the same element that effect pointed to. However, the target element
is might be overridden with <emphasis><property>"effectId"</property></emphasis> option passed with <emphasis><property>"params"</property></emphasis>
attribute of with function paramenter.
Modified: trunk/docs/userguide/en/src/main/docbook/included/scrollableDataTable.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/scrollableDataTable.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/scrollableDataTable.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -81,7 +81,7 @@
<property>"hideWhenScrolling"</property>
</emphasis>. If attribute value is "true" data is hidden during scrolling. </para>
- <para> It's possible to select the whole row with onclick on the row or some set of rows.
+ <para> It's possible to select the whole row with onclick on the row or some set of rows.
Selection is optional and availability of such feature is defined on the component. There are
two ways to select a few rows: <itemizedlist>
<listitem><para>Just clicking the columns one by one.</para></listitem>
@@ -94,7 +94,7 @@
the next JS API: <itemizedlist>
<listitem><para><code>collapse(columnId)</code> - Performs the collapse action for the column with the
corresponding id</para></listitem>
- </itemizedlist> It's possible to sort the table content after clicks on the header. The
+ </itemizedlist> It's possible to sort the table content after clicks on the header. The
feature is optional. Every column should be pointed to the comparator method that is used
for sorting the table. In case the
<emphasis role="bold"><property><rich:scrollableDataTable></property></emphasis> is already sorted by some column
@@ -132,7 +132,7 @@
<code>org.richfaces.model.selection.Selection</code> interface, containing current
collection of objects selected by you.</para>
<para>In the following example when you submit the form, current collection of the selected objects
- is placed in the object's property. Then on complete action the <emphasis role="bold">
+ is placed in the object's property. Then on complete action the <emphasis role="bold">
<property><rich:modalPanel></property>
</emphasis> with selected data is shown.</para>
<para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/toolTip.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/toolTip.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/included/toolTip.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -74,7 +74,7 @@
<para>
To specify text information, labeled on a <emphasis role="bold"><property><rich:toolTip></property></emphasis>, use <emphasis><property>"value"</property></emphasis> attribute.
Images, links, buttons and other RichFaces components also may be put and composed inside <emphasis role="bold"><property><rich:toolTip></property></emphasis>.
- Text, specified between <property>tooltip's</property> start and end tags will be rendered in browser as simple text.
+ Text, specified between <property>tooltip's</property> start and end tags will be rendered in browser as simple text.
<emphasis role="bold"><property><rich:toolTip></property></emphasis> borders stretch to enclose it contents.
</para>
<para>
@@ -85,7 +85,7 @@
<note>
<title>Note:</title>
<para>
- It is recommended to specify <emphasis><property>"id"</property></emphasis> for parent page element to ensure <property>tooltip's</property> correct work.
+ It is recommended to specify <emphasis><property>"id"</property></emphasis> for parent page element to ensure <property>tooltip's</property> correct work.
</para>
</note>
<note>
@@ -131,7 +131,7 @@
<emphasis role="bold"><property><rich:toolTip></property></emphasis> may also be invoked by JS API function.
List of JS API functions available for <emphasis role="bold"><property><rich:toolTip></property></emphasis> is listed <link linkend="tab_jsapi">below</link>.
JS API functions are defined for a page element, the <emphasis role="bold"><property><rich:toolTip></property></emphasis> is applied to. Thus, <emphasis role="bold"><property><rich:toolTip></property></emphasis> can be defined separately from that page element.
- It is necessary to specify <emphasis><property>"ids"</property></emphasis> for both and set <emphasis role="bold"><property><rich:toolTip></property></emphasis> <emphasis><property>"attached"</property></emphasis> attribute's value to "false" (see the example below).
+ It is necessary to specify <emphasis><property>"ids"</property></emphasis> for both and set <emphasis role="bold"><property><rich:toolTip></property></emphasis> <emphasis><property>"attached"</property></emphasis> attribute's value to "false" (see the example below).
</para>
<programlisting role="XML"><![CDATA[...
<rich:panel id="paneld" onclick="#{rich:component("tooltipId")}.show();">
@@ -205,7 +205,7 @@
<para>
By default, <emphasis role="bold"><property><rich:toolTip></property></emphasis> appears smart positioned. But as you can see from the previous example, you
can define an appearance direction via the corresponding attribute <emphasis><property>"direction"</property></emphasis>.
- And also it's possible to define vertical and horizontal offsets relatively to a mouse position.
+ And also it's possible to define vertical and horizontal offsets relatively to a mouse position.
</para>
<para>
Disabled <emphasis role="bold"><property><rich:toolTip></property></emphasis> is rendered to a page as usual but JS that responds for its activation is disabled until <code>enable()</code> is called.
Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -114,7 +114,7 @@
RichFaces installs its ViewHandler in any case, so in case
of two frameworks, for example RichFaces + Facelets, no
changes in settings are required. Although, when more then
- one framework (except RichFaces) is used, it's possible to
+ one framework (except RichFaces) is used, it's possible to
use the
<code>VIEW_HANDLERS</code>
parameter defining these frameworks view handlers according
@@ -320,7 +320,7 @@
<para>
<property>JBoss Portlets</property>
have support since version Ajax4jsf 1.1.1. This support is
- improved in Richfaces 3.2.1. Provide your feedback on
+ improved in RichFaces 3.2.1. Provide your feedback on
compatible with RichFaces if you face some problems.
</para>
</section>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -920,9 +920,9 @@
<section id="DisableSkins">
<?dbhtml filename="DisableSkins.html"?>
- <title>How to disable skinability?</title>
+ <title>How to disable skinnability?</title>
<para>There is possibility to use special skin with name "plain". It doesn't have
- any parameters. It's necessary for embedding RichFaces components into
+ any parameters. It's necessary for embedding RichFaces components into
existing projecst which have its own styles.</para>
<para>For information you can see discussion about this problem on the <ulink
url="http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066340#..."
Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml 2008-07-15 12:35:17 UTC (rev 9605)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml 2008-07-15 12:51:09 UTC (rev 9606)
@@ -62,7 +62,7 @@
<listitem><para>Browser (on client side)</para></listitem>
- <listitem><para>Richfaces framework</para></listitem>
+ <listitem><para>RichFaces framework</para></listitem>
</itemizedlist>
<section id="SupportedJavaVersions">
16 years, 2 months
JBoss Rich Faces SVN: r9605 - in trunk/samples/richfaces-demo/src/main/webapp/richfaces: plugnskin and 1 other directories.
by richfaces-svn-commits＠lists.jboss.org
Author: smukhina
Date: 2008-07-15 08:35:17 -0400 (Tue, 15 Jul 2008)
New Revision: 9605
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml
trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml
Log:
http://jira.jboss.com/jira/browse/RF-398
language is corrected in livedemo
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml 2008-07-15 12:28:53 UTC (rev 9604)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml 2008-07-15 12:35:17 UTC (rev 9605)
@@ -11,7 +11,7 @@
<p>a4j:jsFunction component is very similar to a4j:commandButton, but allows to perform
an Ajax request from a Javascript code directly. The component sends a request using
a standard JSF approach, so the JSF form is required. The following example
- shows how the part of the page is re-rendered when a user hovers over the names.
+ shows how the part of a page is re-rendered when a user hovers over the names.
</p>
<fieldset class="demo_fieldset">
@@ -37,7 +37,7 @@
</a>.
</p>
<p>
- As for any other Ajax components, you can use <b>reRender</b> attribute to update the area(s) of the page
+ As for any other Ajax components, you can use <b>reRender</b> attribute to update the area(s) of a page
after an Ajax Response comes back. Also, you can use <b>data</b> attribute and <b>oncomplete</b> attribute to
take the data from the server and use them for Javascript to call them. For additional information about
Javascript oriented and other important attributes of a4j:jsFunction read
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml 2008-07-15 12:28:53 UTC (rev 9604)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml 2008-07-15 12:35:17 UTC (rev 9605)
@@ -27,7 +27,7 @@
by taking the base skin as basis and plugging-in custom styles.
</p>
<p>
- You may freely create your own pluggable skin in a next way:
+ You may freely create your own pluggable skin in the next way:
</p>
<ul>
<li>
@@ -39,17 +39,17 @@
root folder of richfaces.
</li>
<li>
- <b>Create new pluggable skin inside project</b> using
+ <b>Create new pluggable skin inside the project</b> using
<i>mvn cdk:add-skin -Dname=*SKIN-NAME* -Dpackage=*SKIN-PACKAGE*</i>
from the folder created on the previous step.
</li>
</ul>
<p>
- In the result you'll get new skin project.
+ In the result you'll get a new skin project.
</p>
<p class="note">
In order to check some other optional parameters for CDK commands and
- more info about the feature in general - visit corresponding
+ more info about the feature in general - visit the corresponding
developer guide section
and explore <b>Laguna</b> skin project in richfaces/samples svn.
</p>
@@ -74,8 +74,8 @@
</li>
</ul>
<p>
- All classes for all the components and standard skinning classes already
- listed in corresponding imported xcss files. So you'll only need to fill them
+ All classes for all the components and standard skinning classes are already
+ listed in corresponding imported xcss files. Thus you'll only need to fill them
with the properties you need.
</p>
<p>
Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml
===================================================================
--- trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml 2008-07-15 12:28:53 UTC (rev 9604)
+++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml 2008-07-15 12:35:17 UTC (rev 9605)
@@ -30,21 +30,21 @@
</p>
<p>
This feature provides styling for standard HTML form elements
- in order to be highly compilant to RichFaces common look'n'feel. There
+ in order to be highly compilant with RichFaces common look'n'feel. There
should be two ways of applying skins to elements:
</p>
<ul>
<li>
Skinning style classes are applied to elements by element
name and type attribute (where applicable). No additional steps
- required from an application developer. Application initialization
+ are required from an application developer. Application initialization
parameter serves for enabling/disabling the feature.
</li>
<li>
Several style classes are provided for different types of
elements. That style classes have predefined names. Application
developer should manually assign classes to controls that need
- skinning or assign class to an element that contains controls.
+ skinning or assign a class to an element that contains controls.
</li>
</ul>
<p>
@@ -89,7 +89,7 @@
will be skinned. It could be also turned off using <b>disable</b> value.
</li>
<li>
- Rich faces also provides predefined classes which can be applied by end developer
+ RichFaces also provides predefined classes which can be applied by an end developer
to elements need to be skinned separately. This classes added to the page also
according to <b>org.richfaces.CONTROL_SKINNING_CLASSES</b> context-param.
</li>
@@ -113,7 +113,7 @@
</rich:panel>
</fieldset>
<p>
- And the last one way means that classes with names corresponding to elements names
+ And the last one means that classes with names corresponding to elements names
will be added to the application pages and possible to set manually:
</p>
<fieldset class="demo_fieldset">
16 years, 2 months
JBoss Rich Faces SVN: r9604 - trunk/docs/userguide/en/src/main/docbook/included.
by richfaces-svn-commits＠lists.jboss.org
Author: cluts
Date: 2008-07-15 08:28:53 -0400 (Tue, 15 Jul 2008)
New Revision: 9604
Modified:
trunk/docs/userguide/en/src/main/docbook/included/calendar.xml
Log:
RF-3882 - described "currentDate" attribute and corrected code example (because "selectedDate" attribute is absent for <rich:calendar> component).
Modified: trunk/docs/userguide/en/src/main/docbook/included/calendar.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/calendar.xml 2008-07-15 12:25:53 UTC (rev 9603)
+++ trunk/docs/userguide/en/src/main/docbook/included/calendar.xml 2008-07-15 12:28:53 UTC (rev 9604)
@@ -101,6 +101,8 @@
<para>Usage <emphasis>
<property>"currentDate"</property>
</emphasis> attribute isn't available in the popup mode.</para>
+ <para>With help of the <emphasis><property>"currentDate"</property></emphasis> attribute
+ you can define month and year which will be displayed currently.</para>
<para>The <emphasis role="bold">
<property><rich:calendar></property>
</emphasis> component can render pages of days in two modes. A mode could be
@@ -325,7 +327,7 @@
<programlisting role="XML"><![CDATA[...
<rich:calendar id="myCalendar" popup="true" locale="#{calendarBean.locale}" value="#{bean.date}"
- preloadRangeBegin="#{bean.date}" preloadRangeEnd="#{bean.date}" selectedDate="#{bean.date}" cellWidth="40px" cellHeight="40px">
+ preloadRangeBegin="#{bean.date}" preloadRangeEnd="#{bean.date}" cellWidth="40px" cellHeight="40px">
<!-- Customization with usage of facets and accessible elements -->
<f:facet name="header">
16 years, 2 months