richfaces-svn-commits
March 2011
richfaces-svn-commits@lists.jboss.org
- 1 participants
- 355 discussions
JBoss Rich Faces SVN: r22230 - in branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces: collapsiblePanel and 11 other directories.
by richfaces-svn-commits＠lists.jboss.org
Author: jbalunas(a)redhat.com
Date: 2011-03-15 17:41:44 -0400 (Tue, 15 Mar 2011)
New Revision: 22230
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/accordion/simple.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/samples/simple-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/simple.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/samples/lookCustomization-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/simple.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/login.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/modalPopup.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/modalPopup-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/simplePopup-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/simplePopup.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/ajaxProgressBar.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/clientProgressBar.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/ajaxProgressBar-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/clientProgressBar-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/simple.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/valueManagement.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/simple.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/wizard.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/samples/tooltip-sample.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/tooltip.xhtml
Log:
RFPL-1217 updates to showcase text
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/accordion/simple.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/accordion/simple.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/accordion/simple.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,14 +5,11 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>The <b>Accordion</b> (<i>panelBar from 3.3.x</i>) is a set of panels when one panel is expanded,
- but other ones are collapsed. </p>
- <p>
- <b>Main addition</b> to previous 3.3.x functionality - accordion in 4.x was finally added with
- different switching <b>switchType</b>'s. So as all the switchable panels it could be used with next modes -
- "<i>client</i>", "<i>ajax</i>" and "<i>server</i>".
- </p>
- <p>The following demo shows the simple example of usage for the Accordion in client mode:</p>
+ <p>The <b>rich:accordion</b> component is a set of panels where one panel is expanded,
+ while the other ones are collapsed. This is similar to, and inherits much of
+ the features from the rich:togglePanel, and rich:tabPanel. See the descriptions
+ of these components for details on switch-types, and shortcuts.</p>
+ <p>The following example shows the usage of the rich:accordion in client mode:</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/samples/simple-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/samples/simple-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/samples/simple-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -28,7 +28,7 @@
</ul>
</rich:collapsiblePanel>
- <p><b>And that panel switched by ajax and closed by default:</b></p>
+ <p><b>This panel is switched via Ajax and closed by default:</b></p>
<rich:collapsiblePanel header="JSF 2 and RichFaces 4" expanded="false"
switchType="ajax">
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/simple.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/simple.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/collapsiblePanel/simple.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,12 +5,13 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p><b>collapsiblePanel</b> representation is fully analogous to simple
- <b>rich:panel</b> component. Additionally that component could be toggled
- between two representations. In collapsed state only header shown and
- in expanded state there is complete panel.</p>
- <p>As most of switchable components it has three <b>switch types</b> for
- switching between states - <b>ajax</b>, <b>server</b> and <b>client</b>
+ <p>The <b>rich:collapsiblePanel</b> component is fully analogous to a simple
+ <b>rich:panel</b> component. Except that it can be collapsed, and expanded.
+ In the collapsed state only the header is shown and in expanded state the
+ complete panel.</p>
+ <p>As with most of switchable components it has three <b>switch types</b> for
+ switching between states - <b>ajax</b>, <b>server</b> and <b>client</b>.
+ See the rich:togglePanel for details.
</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
@@ -19,7 +20,7 @@
<ui:param name="openLabel" value="View Source" />
<ui:param name="hideLabel" value="Hide Source" />
</ui:include>
- <p>In ajax and server mode <b>PanelToggleEvent</b> queued and could be handled
- using <b>Listener</b> defined via <b>toggleListener</b> attribute</p>
+ <p><b>Note: </b>In ajax and server modes the <b>PanelToggleEvent</b> is queued and can be handled
+ using a <b>Listener</b> defined via the <b>toggleListener</b> attribute</p>
</ui:composition>
</html>
\ No newline at end of file
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/samples/lookCustomization-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/samples/lookCustomization-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/samples/lookCustomization-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -39,8 +39,8 @@
<f:facet name="header">
Panel #1. Changing Style Synchronously
</f:facet>
- Each component in the RichFaces has a pre-defined set of classes you can manipulate with. If defined, those
- classes overwrite the ones come from the skin.
+ Each component in RichFaces has a pre-defined set of CSS classes you can manipulate. If defined, those
+ classes overwrite the ones that come from the skin.
</rich:panel>
<rich:panel>
@@ -61,7 +61,7 @@
<f:facet name="header">
Panel header
</f:facet>
- Base on the previous layout, but some javascript behaviour added.
+ Base on the previous layout, but with javascript visual effects added.
</rich:panel>
<rich:panel style="width:200px;" bodyClass="body3">
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/simple.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/simple.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/panel/simple.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,10 +5,10 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>The panel is a rectangle area on a page that may contain any
- content including other panels. Panel has a header (optionally) and a
+ <p>The <b>rich:panel</b> component creates a rectangle shaped area on the page that may contain any
+ content including other panels. Panel's have a header (optional) and a
body. The default look-n-feel is based on the current skin. Look-n-feel
- of any parts of the panel, including color scheme, borders and paddings
+ of any part of the panel, including color scheme, borders and paddings
can be customizable using with pre-defined number of CSS classes.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/login.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/login.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/login.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,30 +5,19 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>In RichFaces 3.3.x many developers used <b>rich:dropDownMenu</b>
- component for creation of Search/Login popups attached to toolbars. And
- there were two reasons for that:</p>
- <ul>
- <li>Simplicity of usage. No script positioning required.
- rich:dropDownMenu performs popup positioning on its own and simply
- customizable by using <b>jointPoint</b> and <b>direction</b>
- attributes.</li>
- <li>RichFaces 3.3.x has no lightweight popup panel and <b>rich:modalPanel</b>
- usage for such cases required workarounds in order to make it
- non-modal</li>
- </ul>
- <p>But that approach has some disadvantages as well:</p>
- <ul>
- <li><b>rich:dropDownMenu</b> component was added with additional
- JavaScript code for inputs processing inside the <b>rich:menuItem</b>'s.
- That not really native task for menu so that code was really
- superfluous from simple menus point of view.</li>
- <li>Developer still has to work on styling of menu item removing
- hover effects and making it looks like panel rather than menuItem</li>
- </ul>
- <p>RichFaces 4.x provides clean api for popup panel and added
- non-modal state, so for now it's really easier and looking more native
- to use modal panel for such tasks. Below you could see two samples:</p>
+ <p>RichFaces 4.x provides a clean api for popup panels and added
+ non-modal state, so now its easy to use the popup panel for login, and
+ seach panels. The examples below show both variants; login, and search, but
+ of coarse you could use any content you wanted.</p>
+ <p>At the bottom of the page is a description and information for RichFaces
+ 3.3.X users who used rich:dropDownMenu components to accomplish this same
+ task. If that was you - it is worth a read.</p>
+ <p>The <b>rich:popupPanel</b> also allows you to pass options to the JavaScript show method
+ such as: <b>min/max width and height</b>, specific <b>width and height</b>, <b>top
+ and left</b> positions for the panel. So with <b>rich:hashParam</b> it's
+ really simple to build declarative calls for the panel which can use
+ dynamic properties.</p>
+
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
@@ -36,11 +25,29 @@
<ui:param name="openLabel" value="View Source" />
<ui:param name="hideLabel" value="Hide Source" />
</ui:include>
- <p>rich:popup panel allows you to pass next options to show method:
- <b>min and max width and height</b>, actual <b>width and height</b>, <b>top
- and left</b> positions for the panel. So with <b>rich:hashParam</b> it's
- really simple to build declarative call for the panel which uses
- dynamic properties.</p>
+ <p>In RichFaces 3.3.x many developers used the <b>rich:dropDownMenu</b>
+ component for creation of Search/Login popups attached to toolbars.
+ There were two main reasons for this:</p>
+ <ul>
+ <li>Simplicity of usage. No script positioning required.
+ rich:dropDownMenu performs popup positioning on its own and was simple
+ to customize by using <b>jointPoint</b> and <b>direction</b>
+ attributes.</li>
+ <li>RichFaces 3.3.x has no lightweight popup panel and <b>rich:modalPanel</b>
+ usage for such cases required workarounds in order to make it
+ non-modal</li>
+ </ul>
+ <p>But that approach also has some disadvantages:</p>
+ <ul>
+ <li><b>rich:dropDownMenu</b> component was created with additional
+ JavaScript code for input processing inside the <b>rich:menuItem</b>'s.
+ That is not really a native task for menus so that code was really
+ superfluous from simple menus point of view.</li>
+ <li>Developer still had to work on styling of menu item removing
+ hover effects and making it looks like panel rather than menuItem</li>
+ </ul>
+ <p>We think that the new features of the <b>rich:popupPanel</b> are an
+ excellent replacement for this and hope you will consider updating to it.</p>
</ui:composition>
</html>
\ No newline at end of file
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/modalPopup.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/modalPopup.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/modalPopup.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,11 +5,11 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>There you could check the modal panel which blocks the main
- screen for any operations defined by using <b>popupPanel</b> component
- with <b>modal="true"</b></p>
- <p>In that sample the panel also defined as resizable so you could
- change its sizes using mouse</p>
+ <p>This example of the <b>rich:popupPanel</b> shows you a modal style popup that
+ blocks the main screen from any operation. This is defined by setting the
+ <b>modal="true"</b> attribute.</p>
+ <p>In this example the panel is also defined as resizable so you could
+ change its sizes using the mouse</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/modalPopup-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/modalPopup-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/modalPopup-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -19,9 +19,8 @@
X
</h:outputLink>
</f:facet>
- <p>Additionally there you could check how to handle the clicks
- outside the panel.</p>
- <p>In this sample the click outside - closes the panel as well as
- clicking hide control in the header</p>
+ <p>You can also check and trigger events if the use clicks outside of the
+ panel.</p>
+ <p>In this example clicking outside closes the panel.</p>
</rich:popupPanel>
</ui:composition>
\ No newline at end of file
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/simplePopup-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/simplePopup-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/samples/simplePopup-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -19,9 +19,7 @@
X
</h:outputLink>
</f:facet>
- <p>Any content might be inside the panel.</p>
- <p>Consider inclusion of the form elements into the popup or
- redefinition of <b>domElementAttachment</b> attribute.</p>
+ <p>Any content might be inside this panel.</p>
<p>The popup panel is open and closed from the javascript function
of component client side object. The following code <a href="#"
onclick="#{rich:component('popup')}.hide()">hide this panel</a>: <f:verbatim>#</f:verbatim>{rich:component('popup')}.hide()</p>
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/simplePopup.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/simplePopup.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/popup/simplePopup.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,17 +5,17 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>Popup panel component used to create any kind of popups on the page.</p>
+ <p>The <b>rich:popupPanel</b> component is used to create any kind of popups on the page.</p>
<p>Main features:</p>
<ul>
- <li>Has two states modal and non-modal</li>
- <li>Could be defined as resizable</li>
- <li>Could be autosized according to content</li>
- <li>Could be moved across the screen</li>
- <li>Could be automatically positioned as centered or use user defined position</li>
+ <li>Two states; modal and non-modal</li>
+ <li>Can be defined as resizable</li>
+ <li>Can be autosized according to content</li>
+ <li>Can be moved across the screen</li>
+ <li>Can be automatically positioned as centered or use a defined position</li>
</ul>
- <p>This sample shows simple <b>non-modal popup</b> which are <b>movable</b> but not resizable
- as defined to use <b>autosizing</b> according to it's content</p>
+ <p>This example shows a simple <b>non-modal popup</b> which is movable but not resizable
+ and defined to use <b>autosizing</b> according to it's content</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
@@ -25,10 +25,10 @@
<ui:param name="hideLabel" value="Hide Source" />
</ui:include>
- <p>Besides this sample shows two variants of working with the component JS API:</p>
+ <p>This example also shows two variants of working with the component JavaScript API:</p>
<ul>
<li>The popup is called by the <b>rich:componentControl</b> attached to button</li>
- <li>The popup is closed by simple JS calls which defined using <b>rich:component</b> function</li>
+ <li>The popup is closed by a simple JavaScript call which is defined using the <b>rich:component</b> function</li>
</ul>
</ui:composition>
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/ajaxProgressBar.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/ajaxProgressBar.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/ajaxProgressBar.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,7 +5,11 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>ProgressBar worked in "ajax" mode </p>
+ <p>The <b>rich:progressBar</b> displays a standard progress widget, and allows
+ for additional facets such as initial, and finish state customizations. In
+ Ajax mode you simply bind the bar to a bean property that returns a value between the
+ 'minValue' and 'maxValue'. This value is then polled from the browser using
+ the specified interval.</p>
<br/>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/clientProgressBar.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/clientProgressBar.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/clientProgressBar.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,7 +5,10 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>ProgressBar worked in "client" mode </p>
+ <p>The <b>rich:progressBar</b> in client mode is strictly based on values in
+ the client browser, and so is not determined by server-state. Using
+ JavaScript component API calls trigger the start, stop, and progress of
+ the component. Take a look at the source code below for an example.</p>
<br/>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/ajaxProgressBar-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/ajaxProgressBar-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/ajaxProgressBar-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -11,7 +11,7 @@
minValue="0" maxValue="100" reRenderAfterComplete="progressPanel">
<f:facet name="initial">
<h:panelGroup>
- <h:outputText value="Process doesn't started yet" />
+ <h:outputText value="Process hasn't started yet" />
<a4j:commandButton action="#{progressBarBean.startProcess}"
value="Start Process" execute="@form" render="pb"
rendered="#{progressBarBean.buttonRendered}"
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/clientProgressBar-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/clientProgressBar-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/progressBar/samples/clientProgressBar-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -36,7 +36,7 @@
<h:form id="form2">
<rich:progressBar mode="client" id="progressBar" value="-1">
<f:facet name="initial">
- <h:outputText value="Process doesn't started yet" />
+ <h:outputText value="Process hasn't started yet" />
</f:facet>
<f:facet name="complete">
<h:outputText value="Process Done" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/simple.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/simple.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/simple.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,12 +5,9 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>Tab panel is used to create "tabbed" pages.
- RichFaces tab panel can be switched in 3 ways: using "normal" server-side
- update, using "ajax" style update, when only tab panel area is updated
- on the page, and using "client" type, without any interaction with the
- server. Note, that in case of a "client" switch type, all tabs are
- rendered at the same time. </p>
+ <p>The <b>rich:tabPanel</b> component is used to create "tabbed" sections or pages.
+ RichFaces tab panel can be switched in the 3 ways detailed in the
+ <b>rich:togglePanel</b> example.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/valueManagement.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/valueManagement.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tabPanel/valueManagement.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,18 +5,13 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>That sample shows how to use external controls for switching the
- panel</p>
- <p><b>toggleControl</b> behavior used as for any other switchable
- panel (<i>togglePanel, accordion</i>)</p>
- <p><b>targetItem</b> could be <b>defined with tab name</b> and
- additionally tabPanel supports next <b>predefined shortcuts</b>:</p>
- <ul>
- <li>@next</li>
- <li>@prev</li>
- <li>@first</li>
- <li>@last</li>
- </ul>
+ <p>This example shows how to use external controls, and special shortcuts
+ to switch the tabbed panels</p>
+ <p>The <b>rich:toggleControl</b> behavior used by any of the other switchable
+ panels (<i>togglePanel, accordion</i>) can be used with <b>rich:tabPanels</b>
+ as well.</p>
+ <p>So you can set the <b>targetItem</b> to be defined as a specific tab name
+ or use one of the shortcuts detailed in the <b>rich:togglePanel</b> example.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
@@ -24,8 +19,8 @@
<ui:param name="openLabel" value="View Source" />
<ui:param name="hideLabel" value="Hide Source" />
</ui:include>
- <p>Additionally you could manage the current tab at server side
- using <b>activeItem</b> attribute at tabPanel <b>bound to some Bean
- property</b> which holds current tab name.</p>
+ <p>Additionally you can manage the current tab on the server side
+ using the <b>activeItem</b> attribute on the tabPanel <b>bound to some Bean
+ property</b> which then holds current tab name.</p>
</ui:composition>
</html>
\ No newline at end of file
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/simple.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/simple.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/simple.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,18 +5,31 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
-<p><b>togglePanel</b> is a base component for all switchable panels in RichFaces. It renders
-sequence of states that can be switched (toggled) by a behavior
-called <b>toggleControl</b>. rich:togglePanel has no default appearance. You can define it using
-the set of child <b>togglePanelItem's</b> with any given content inside. </p>
-<p> <b>switchType</b> attribute defines the strategy of switching. The possible values for this attributes are:</p>
+<p>The <b>rich:togglePanel</b> is a core component for all switchable panels in RichFaces. It renders
+a sequence of panels based on state that can be switched (toggled) by a behavior
+called <b>rich:toggleControl</b>. All of these other panels (e.g. tabPanel, accordion, etc...) share
+the basic sets a features defined below.</p>
+<p>The <b>switchType</b> attribute defines the strategy used to toggle between panels. The possible values for this attributes are:</p>
<ul>
-<li><b>client</b> - switching happens on the client without any request to the server. The jsf form is not required in this mode</li>
-<li><b>ajax</b> - when states are switched, the content of new states comes from the server in Ajax way.</li>
+<li><b>client</b> - switching happens on the client without any request to the server. A jsf form is not required in this mode</li>
+<li><b>ajax</b> - when states are switched, the content of new states comes from the server via Ajax requests.</li>
<li><b>server</b> - the whole page is reloaded when states are switched</li>
</ul>
-<p>As the component not provides any predefined layout it could be used for creation of any kind of switchable panels easilly.
-Here is the sample of simplest tabbed pane organized using that component:</p>
+<p>There is also a very useful set of shortcut toggle values that allow you to
+create many custom effects like wizards. See the other switchable panel examples.
+Available shortcuts are defined below:</p>
+ <ul>
+ <li>@next</li>
+ <li>@prev</li>
+ <li>@first</li>
+ <li>@last</li>
+ </ul>
+<p> A <b>rich:togglePanel</b> has no default appearance, and allows you to customize it's
+look-n-feel any way you like. You create a set of child <b>rich:togglePanelItem</b>'s
+with any content you want inside of them. </p>
+<p>As the component does not provide any predefined layout it could be used for
+creation of any kind of switchable panels. This example is a very simple
+tabbed pane organized using that component:</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/wizard.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/wizard.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/togglePanel/wizard.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,22 +5,21 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>And here is simple wizard example constructed using <b>rich:togglePanel</b>
- component.</p>
- <p>Main advantages of using that component for wizard creation:</p>
+ <p>This is a more complex use-case of a wizard constructed using the
+ <b>rich:togglePanel</b> component.</p>
+ <p>Main advantages of using this component for wizard creation:</p>
<ul>
<li>You're not defining any navigation rules and not managing
- current page shown in your code. You just inserting
- <b>rich:togglePanelItem</b> components in needed order and switching between
- them. Current page could be stored using activeItem additionally.</li>
- <li>You not bound anywhere in controls to which panel you need to
- switch. Just the <b>@next</b> and <b>@prev</b> shortcuts used. In that case you
- could easilly add/remove additional panels without making changes in
+ current page shown in your code. You're just inserting
+ <b>rich:togglePanelItem</b> components where needed and switching between
+ them. Also the current page state could be stored using activeItem.</li>
+ <li>You are not bound anywhere in controls to which panel you need to
+ switch. Just the <b>@next</b> and <b>@prev</b> shortcuts are used. In that
+ case you could easily add/remove additional panels without making changes in
switching code. Though you still could use names in targetItem in case
- really need to perform switch to any concrete one. or could use two
- more shortcuts - <b>@first</b>, <b>@last</b>.</li>
+ you really need to perform a specific switch.</li>
<li>Opposite to 3.3.x where toggle controls were encoded as links
- - in RF 4.x <b>rich:toggleControl</b> is just a behavior so any control could
+ - in RF 4.x <b>rich:toggleControl</b> is just a behavior so any control can
be used for switching.</li>
</ul>
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/samples/tooltip-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/samples/tooltip-sample.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/samples/tooltip-sample.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -32,20 +32,20 @@
<h:panelGrid columns="2">
<rich:panel id="sample1" styleClass="tooltip-text"
bodyClass="rich-laguna-panel-no-header">
- <p>Here you can see <b>default client-side</b> tool-tip</p>
+ <p>Here you can see a <b>default client-side</b> tool-tip</p>
<rich:tooltip id="tt1" styleClass="tooltip" layout="block">
<span style="white-space: nowrap"> This tool-tip content was
<strong>pre-rendered</strong> to the page.<br />
- Also the tooltip following mouse by default </span>
+ The tool-tip is also following mouse around.</span>
</rich:tooltip>
</rich:panel>
<rich:panel id="sample2" styleClass="tooltip-text"
bodyClass="rich-laguna-panel-no-header">
- <p>This tool-tip will not <b>follow mouse</b>. Also this tool-tip
- has a <b>delay 1.5 sec</b>, so be patient!</p>
+ <p>This tool-tip will not <b>follow the mouse</b>, and
+ has a <b>delay of 1.5 seconds</b>, so be patient!</p>
<rich:tooltip followMouse="false" showDelay="1500"
styleClass="tooltip-custom-body" layout="block">
- <span style="white-space: nowrap"> This tool-tip content also
+ <span style="white-space: nowrap"> This tool-tip content is also
<strong>pre-rendered</strong> to the page.<br />
</span>
</rich:tooltip>
@@ -53,11 +53,11 @@
<h:form>
<rich:panel id="sample3" styleClass="tooltip-text"
bodyClass="rich-laguna-panel-no-header">
- <p>This tool-tip rendered on server <b>in separate request</b>.
+ <p>This tool-tip was rendered on the server using an Ajax request.
</p>
<rich:tooltip mode="ajax" styleClass="tooltip" layout="block">
<span style="white-space: nowrap">This tool-tip content was
- <strong>rendered on server</strong> </span>
+ <strong>rendered on the server</strong> </span>
<h:panelGrid columns="2">
<h:outputText style="white-space:nowrap"
value="tooltips requested:" />
@@ -70,7 +70,8 @@
<h:form>
<rich:panel id="sample4" styleClass="tooltip-text"
bodyClass="rich-laguna-panel-no-header">
- <p>This tool-tip will be <b>activated on mouse click</b>.</p>
+ <p>This tool-tip will be <b>activated on a mouse click</b>, and
+ has default content defined.</p>
<rich:tooltip showEvent="click" mode="ajax" styleClass="tooltip"
layout="block">
<f:facet name="defaultContent">
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/tooltip.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/tooltip.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/tooltip/tooltip.xhtml 2011-03-15 21:41:44 UTC (rev 22230)
@@ -5,18 +5,21 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>Tooltip is a small non-modal pop-up that could be used to
- display additional information, that is usually hidden.<br />
+ <p>The <b>rich:tooltip</b> component creates a small non-modal pop-up that
+ can be used to display additional information for nearly anything on the page.
</p>
- <p>Major tooltip features:</p>
+ <p>Major features:</p>
<ul>
- <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>Tooltip <b>look is fully customizable</b> using both -
+ <li>Tool-tip content may be <b>pre-rendered</b> on a page using client
+ mode or <b>loaded dynamically</b> using separate Ajax requests via Ajax
+ mode.</li>
+ <li>In Ajax mode <b>default content</b> can be shown while the
+ request is being executed</li>
+ <li>Tool-tip's <b>look-n-feel is fully customizable</b> using both
Richfaces skins and CSS style classes</li>
</ul>
+ <p>There are various other options available such as delays, follow modes,
+ and more that are in the example below:</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22229 - branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation.
by richfaces-svn-commits＠lists.jboss.org
Author: jbalunas(a)redhat.com
Date: 2011-03-15 15:42:29 -0400 (Tue, 15 Mar 2011)
New Revision: 22229
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsfValidators.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsr303.xhtml
Log:
RFPL-1214 updates to showcase text
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsfValidators.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsfValidators.xhtml 2011-03-15 19:00:35 UTC (rev 22228)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsfValidators.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
@@ -5,18 +5,19 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p><b>RichFaces Client Validation</b> feature allows you to add
- client side validation without writing any line of JavaScript!</p>
- <p>All the JSF validators and JSR-303 standard validators will be
- available on client side after just <b><rich:validator/></b> to
- the inputs which you want to be validated at client side. If you using
- any custom validators or some additional for example hibernate
- validators which we not implemented in first version - Ajax fallback
- mechanism will be used. It means that behavior will try to execute all
- client vlidators available and then send Ajax request for unknown to
- get results from server side.</p>
- <p>In that sample - pay attention that no requests fired when
- typing wrong values in first the fields. </p>
+ <p>The <b>RichFaces Client Validation</b> feature allows you to have true
+ client side validation without writing a single line of JavaScript!</p>
+ <p>The standard JSF validators and JSR-303 (bean validation) constraints will
+ be available on the client side just by adding <b><rich:validator/></b> to
+ the desired inputs. If you are using any custom validators or extensions
+ such as from hibernate an Ajax fallback mechanism will be used triggered.
+ This will be basically seamless to the user, as an Ajax request will handle
+ that specific validation. In future versions we plan to implement additional
+ extensions such as these including custom client side validation.
+ The behavior will try to execute all client validators available and then
+ send an Ajax request to get results from server side if needed.</p>
+ <p>In this example we are using standard JSF validators and notice that no
+ requests are fired when typing values in these fields. </p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
@@ -27,17 +28,13 @@
<fieldset>
<legend><b>Notes:</b></legend>
<ul>
- <li>Some JSR-303 validators still not implemented. Them will start work transparently for you after new snapshots with implementations added</li>
- <li>We will provide information about how to provide client validation for custom validators soon!</li>
+ <li>Some JSR-303 validators are not yet implemented for various reasons
+ (localization primarily). As we complete these implementations they
+ will work transparently after upgrading, plus Ajax fallbacks will work fine
+ for these, so there is no reason not to start using them now!</li>
+ <li>In future versions custom client side validators will be possible, and we'll
+ update our examples to showcase them.</li>
</ul>
</fieldset>
- <fieldset>
- <legend><b>What to expect additionally:</b></legend>
- After we will complete all standard validators migration and instructions for custom ones we plan to work on next features:
- <ul>
- <li>Client Validation for submit components to perform bulk form validation.</li>
- <li>Ways of default validation definitions without usage of <b><rich:validator/></b> tag for every input.</li>
- </ul>
- </fieldset>
</ui:composition>
</html>
\ No newline at end of file
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsr303.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsr303.xhtml 2011-03-15 19:00:35 UTC (rev 22228)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/clientValidation/jsr303.xhtml 2011-03-15 19:42:29 UTC (rev 22229)
@@ -5,19 +5,20 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p><b>RichFaces Client Validation</b> feature allows you to add
- client side validation without writing any line of JavaScript!</p>
- <p>All the JSF validators and JSR-303 standard validators will be
- available on client side after just <b><rich:validator/></b> to
- the inputs which you want to be validated at client side. If you using
- any custom validators or some additional for example hibernate
- validators which we not implemented in first version - Ajax fallback
- mechanism will be used. It means that behavior will try to execute all
- client vlidators available and then send Ajax request for unknown to
- get results from server side.</p>
- <p>In that sample - pay attention that no requests fired when
- typing wrong values in all the fields and only checkbox activation
- causes Ajax fallback.</p>
+ <p>The <b>RichFaces Client Validation</b> feature allows you to have true
+ client side validation without writing a single line of JavaScript!</p>
+ <p>The standard JSF validators and JSR-303 (bean validation) constraints will
+ be available on the client side just by adding <b><rich:validator/></b> to
+ the desired inputs. If you are using any custom validators or extensions
+ such as from hibernate an Ajax fallback mechanism will be used triggered.
+ This will be basically seamless to the user, as an Ajax request will handle
+ that specific validation. In future versions we plan to implement additional
+ extensions such as these including custom client side validation.
+ The behavior will try to execute all client validators available and then
+ send an Ajax request to get results from server side if needed.</p>
+ <p>In this example we are using Bean Validation constraints and checking
+ them at the client, so no requests are fired when typing values
+ in the fields. Note that only checkbox activation causes Ajax fallback.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
@@ -31,24 +32,16 @@
<ui:param name="openLabel" value="View ValidationBean Source" />
<ui:param name="hideLabel" value="Hide ValidationBean Source" />
</ui:include>
- <fieldset><legend><b>Notes:</b></legend>
- <ul>
- <li>Some JSR-303 validators still not implemented. Them will
- start work transparently for you after new snapshots with
- implementations added</li>
- <li>We will provide information about how to provide client
- validation for custom validators soon!</li>
- </ul>
- </fieldset>
- <fieldset><legend><b>What to expect
- additionally:</b></legend> After we will complete all standard validators migration
- and instructions for custom ones we plan to work on next features:
- <ul>
- <li>Client Validation for submit components to perform bulk form
- validation.</li>
- <li>Ways of default validation definitions without usage of <b><rich:validator/></b>
- tag for every input.</li>
- </ul>
- </fieldset>
+ <fieldset>
+ <legend><b>Notes:</b></legend>
+ <ul>
+ <li>Some JSR-303 validators are not yet implemented for various reasons
+ (localization primarily). As we complete these implementations they
+ will work transparently after upgrading, plus Ajax fallbacks will work fine
+ for these, so there is no reason not to start using them now!</li>
+ <li>In future versions custom client side validators will be possible, and we'll
+ update our examples to showcase them.</li>
+ </ul>
+ </fieldset>
</ui:composition>
</html>
\ No newline at end of file
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22228 - in branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces: queue and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: jbalunas(a)redhat.com
Date: 2011-03-15 15:00:35 -0400 (Tue, 15 Mar 2011)
New Revision: 22228
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/attachQueue/attachQueue.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/queue/queue.xhtml
Log:
RFPL-1211 updates to showcase text
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/attachQueue/attachQueue.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/attachQueue/attachQueue.xhtml 2011-03-15 17:29:41 UTC (rev 22227)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/attachQueue/attachQueue.xhtml 2011-03-15 19:00:35 UTC (rev 22228)
@@ -3,14 +3,16 @@
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j">
- <p>In RichFaces 4 all request settings related to queue was moved
- out of components attributes and now customization available using new
- <b>a4j:attachQueue</b> tag. Next sample shows how <b>requestDelay</b>
- could be changed for single component.</p>
- <p>Note that when you typing in input - status appears with two
- seconds delay because <b>default queue contains requestDelay="2000"</b>.
- And when you clicking save button - it appears immediately because <b>requestDelay
- changed to 0 for the button</b>.</p>
+ <p>The <b>a4j:attachQueue</b> component allow you to funnel requests
+ from specific components or behaviors through a 'named' queue (see queue
+ example), but also allows you to override queue settings right from the
+ component. </p>
+ <p>This sample shows how <b>requestDelay</b>
+ can be changed for single component.</p>
+ <p>Note that when you are typing in the input - the status appears with a two
+ seconds delay because the <b>default queue contains requestDelay="2000"</b>.
+ However when you are clicking the save button - it appears immediately
+ because <b>requestDelay changed to 0 for the button</b>.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/queue/queue.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/queue/queue.xhtml 2011-03-15 17:29:41 UTC (rev 22227)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/queue/queue.xhtml 2011-03-15 19:00:35 UTC (rev 22228)
@@ -3,31 +3,32 @@
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets">
- <p>JSF 2 provides queue mechanism out-of the box already. And
- RichFaces queue just provides some additional customizations to improve
- the queue usability and allow to tune your performance while using Ajax
- as much as possible.</p>
- <p>The only big difference which the developers who used queue in
- 3.3.x should remember: as JSF 2 already provides single queue and not
- allows to have more than one queue instance(currently) you can't really
- fire concurrent requests anymore. So the queue in RF now not actually
- defines logical queue but just a component for defining queueing
- options.</p>
- <p>Here you could explore additional optimization parameters of the
- queue and learn how they influence Ajax requests. This example is a
- good start to learn about Ajax requests flood protection.</p>
+ <p>JSF 2 provides a queuing mechanism out-of the box in order to sequence
+ client side events with the built-in Ajax implementation. This queue is
+ lacking in some very essential tuning options. The RichFaces
+ <b>a4j:queue</b> provides these basic options in addition to other
+ enhancements. There are two primary options available; 'requestDelay' and
+ 'ignoreDupResponse'. These are explained more in the example below.</p>
+ <p>Many of the features of the RichFaces 3.3.X queue have been ported to
+ RichFaces 4.0 version. However it is important to remember that the 4.0
+ queue is a logical queue on top of JSF's. There is only a single physical
+ queue allowed and there is no way to override that (for now).</p>
+ <p>In this example you can tweak different queue options and see what effect
+ that has on the number of events fired, and how often the DOM is updated.
+ This provides a good way to learn about Ajax requests flood protection.</p>
- <p>Pay attention to next point in the example:</p>
+ <p>Attribute details:</p>
<ul>
- <li>Setting <b>requestDelay</b> to greater value reduces the greatly
- requests count on fast typing. (More similar requests are combined in
- the result)</li>
- <li>Setting requestDelay to smaller value(just for easier exploration) but using <b>ignoreDupResponse</b> flag set to true
- - reduces greatly DOM updates count.</li>
+ <li><b>requestDelay</b> is the number of milliseconds to wait before
+ sending a request in order to combine similar requests. The greater the
+ value the fewer requests will be sent when fast typing. Similar requests
+ in the queue are combined while waiting for the request delay</li>
+ <li>If <b>ignoreDupResponse</b> is true then RichFaces will not waste
+ time updating the client side DOM if it knows another request for the same
+ thing is pending. The best way to see that in this demo is set
+ requestDelay to a very small value and type quickly. You will see the
+ number of DOM updates be smaller than requests sent.</li>
</ul>
- <p>Also pay your attention to the queue definition. Such definition
- (inside some form without a name) means that the queue options becomes
- global for the form.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
@@ -36,17 +37,19 @@
<ui:param name="openLabel" value="View Source" />
<ui:param name="hideLabel" value="Hide Source" />
</ui:include>
- <p>Queue could be defined as</p>
+ <p><b>Queue scopes, and names:</b></p>
+ <p>You can define a queue so that it is the default queue for all requests
+ from a complete view, a specific form, or even specific components.</p>
<ul>
- <li><b>Default for view.</b> In this case - the parameters will
- be used for all the Ajax requests in view(if not redefined). In order
- to define such queue - just place <b>a4j:queu</b> outside of any forms
- without defining <b>name</b></li>
- <li><b>Default for form.</b> Similar to view-scoped but should be
- defiend in some form without defining <b>name</b></li>
- <li><b>Referenced from ajax behaviors/components.</b> Queue
- should be defined with name and referenced using attachQueue tag(see
- corresponding sample).</li>
+ <li><b>View scoped:</b> Place an <b>a4j:queue</b> with no name
+ attribute outside of any form, and it will be the default
+ queue for all requests on the page.</li>
+ <li><b>Form scoped</b> Place a nameless <b>a4j:queue</b> within a form
+ to make it the default queue for all requests within it.</li>
+ <li><b>Named queue</b> Define an <b>a4j:queue</b> with a specific name.
+ Then you can make any component, or behavior use that queue with the
+ <b>a4j:attachQueue</b> component. See the next queue example for details.
+ </li>
</ul>
</ui:composition>
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22227 - in modules/tests/metamer/trunk/application/src/main: webapp/components/richPopupPanel and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: ppitonak(a)redhat.com
Date: 2011-03-15 13:29:41 -0400 (Tue, 15 Mar 2011)
New Revision: 22227
Added:
modules/tests/metamer/trunk/application/src/main/webapp/components/richPopupPanel/formInsidePanel.xhtml
Modified:
modules/tests/metamer/trunk/application/src/main/java/org/richfaces/tests/metamer/bean/RichPopupPanelBean.java
Log:
added sample with a form inside popup panel
Modified: modules/tests/metamer/trunk/application/src/main/java/org/richfaces/tests/metamer/bean/RichPopupPanelBean.java
===================================================================
--- modules/tests/metamer/trunk/application/src/main/java/org/richfaces/tests/metamer/bean/RichPopupPanelBean.java 2011-03-15 16:02:57 UTC (rev 22226)
+++ modules/tests/metamer/trunk/application/src/main/java/org/richfaces/tests/metamer/bean/RichPopupPanelBean.java 2011-03-15 17:29:41 UTC (rev 22227)
@@ -45,6 +45,9 @@
private static final long serialVersionUID = -1L;
private static Logger logger;
private Attributes attributes;
+ private String value1;
+ private String value2;
+ private String value3;
/**
* Initializes the managed bean.
@@ -78,4 +81,35 @@
public void setAttributes(Attributes attributes) {
this.attributes = attributes;
}
+
+ public String getValue1() {
+ return value1;
+ }
+
+ public void setValue1(String value1) {
+ this.value1 = value1;
+ }
+
+ public String getValue2() {
+ return value2;
+ }
+
+ public void setValue2(String value2) {
+ this.value2 = value2;
+ }
+
+ public String getValue3() {
+ return value3;
+ }
+
+ public void setValue3(String value3) {
+ this.value3 = value3;
+ }
+
+ public String save() {
+ logger.warn("1: " + value1);
+ logger.warn("2: " + value2);
+ logger.warn("3: " + value3);
+ return null;
+ }
}
Added: modules/tests/metamer/trunk/application/src/main/webapp/components/richPopupPanel/formInsidePanel.xhtml
===================================================================
--- modules/tests/metamer/trunk/application/src/main/webapp/components/richPopupPanel/formInsidePanel.xhtml (rev 0)
+++ modules/tests/metamer/trunk/application/src/main/webapp/components/richPopupPanel/formInsidePanel.xhtml 2011-03-15 17:29:41 UTC (rev 22227)
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:metamer="http://java.sun.com/jsf/composite/metamer"
+ xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j">
+
+ <!--
+JBoss, Home of Professional Open Source
+Copyright 2010-2011, Red Hat, Inc. and individual contributors
+by the @authors tag. See the copyright.txt in the distribution for a
+full listing of individual contributors.
+
+This is free software; you can redistribute it and/or modify it
+under the terms of the GNU Lesser General Public License as
+published by the Free Software Foundation; either version 2.1 of
+the License, or (at your option) any later version.
+
+This software is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with this software; if not, write to the Free
+Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+02110-1301 USA, or see the FSF site: http://www.fsf.org.
+ -->
+
+ <ui:composition template="/templates/template.xhtml">
+
+ <ui:define name="view">
+ <f:metadata>
+ <f:viewParam name="templates" value="#{templateBean.templates}">
+ <f:converter converterId="templatesListConverter" />
+ </f:viewParam>
+ </f:metadata>
+ </ui:define>
+
+ <ui:define name="component">
+ input1 <h:inputText id="input1" value="#{richPopupPanelBean.value1}"/>
+
+ <br/><br/>
+
+ <h:commandButton id="openPanelButton" value="Call the popup">
+ <rich:componentControl target="popupPanel" operation="show" />
+ </h:commandButton>
+
+ <rich:popupPanel id="popupPanel" modal="true" header="header">
+ <f:facet name="controls">
+ <h:outputLink value="#" onclick="#{rich:component('popupPanel')}.hide(); return false;">X</h:outputLink>
+ </f:facet>
+
+ <h:panelGrid id="inputs" columns="2">
+ input2 <h:inputText id="input2" value="#{richPopupPanelBean.value2}"/>
+ input3 <h:inputText id="input3" value="#{richPopupPanelBean.value3}"/>
+ </h:panelGrid>
+
+ <a4j:commandButton action="#{richPopupPanelBean.save}" value="Save"
+ render="output1 output2 output3" execute="input1 input2 input3"/>
+ </rich:popupPanel>
+
+ <h:panelGrid id="outputs" columns="2">
+ output1 <h:outputText id="output1" value="#{richPopupPanelBean.value1}"/>
+ output2 <h:outputText id="output2" value="#{richPopupPanelBean.value2}"/>
+ output3 <h:outputText id="output3" value="#{richPopupPanelBean.value3}"/>
+ </h:panelGrid>
+
+ </ui:define>
+
+ <ui:define name="outOfTemplateAfter">
+ </ui:define>
+
+ </ui:composition>
+</html>
\ No newline at end of file
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22226 - branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning.
by richfaces-svn-commits＠lists.jboss.org
Author: ilya_shaikovsky
Date: 2011-03-15 12:02:57 -0400 (Tue, 15 Mar 2011)
New Revision: 22226
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml
Log:
just changed wrong context-param names.
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml 2011-03-15 16:02:57 UTC (rev 22226)
@@ -71,18 +71,18 @@
<p>There three ways of applying skinning to application:</p>
<ul>
- <li>By default <b>org.richfaces.ENABLE_CONTROL_SKINNING</b> context
+ <li>By default <b>org.richfaces.enableControlSkinning</b> context
param is set to <b>true</b> and it means that all standard elements
on the page will be skinned. (CSS style classes for elements based on
their names and type attribute values will be applied). You may
redefine it to <b>disable</b> in order to turn it off.</li>
- <li>By default <b>org.richfaces.ENABLE_CONTROL_SKINNING_CLASSES</b>
+ <li>By default <b>org.richfaces.enableControlSkinningClasses</b>
context param is set to <b>false</b> and it means that basic elements
nested to element having <i>rich-container</i> class will be skinned.
It could be also turned off using <b>disable</b> value.</li>
<li>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.ENABLE_CONTROL_SKINNING_CLASSES</b>
+ This classes added to the page also according to <b>org.richfaces.enableControlSkinningClasses</b>
context-param.</li>
</ul>
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22225 - in branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces: commandButton and 4 other directories.
by richfaces-svn-commits＠lists.jboss.org
Author: jbalunas(a)redhat.com
Date: 2011-03-15 10:56:45 -0400 (Tue, 15 Mar 2011)
New Revision: 22225
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/ajax.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/selectsUpdates.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandButton/commandButton.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandLink/commandLink.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/jsFunction/jsFunction.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/clientParam.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/param.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/skinChange.xhtml
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/poll/poll.xhtml
Log:
RFPL-1211 updates to showcase text
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/ajax.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/ajax.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/ajax.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -6,8 +6,9 @@
xmlns:a4j="http://richfaces.org/a4j">
<ui:composition>
- <p>The behavior that adds javascript call for sending Ajax request
- to specified event on parent component</p>
+ <p><b>a4j:ajax</b> is one of our core behaviors, extending the base JSF 2.0
+ f:ajax tag. This tag triggers an Ajax request when the specified parent
+ event is triggered.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}"/>
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}"/>
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/selectsUpdates.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/selectsUpdates.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/ajax/selectsUpdates.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -6,9 +6,10 @@
xmlns:a4j="http://richfaces.org/a4j">
<ui:composition>
- <p>Typical use-case of dependent select components. When you
- choosing the type in the first select - corresponding items appears in
- second one.</p>
+ <p>This is a slightly more complex use-case for <b>arj:ajax</b> involving
+ dependent select components. When you choose a value from the first select
+ component, the second select component is rendered with dynamic content
+ based on you first choice. </p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandButton/commandButton.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandButton/commandButton.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandButton/commandButton.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -5,8 +5,9 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>The combination similar to h:commandButton with f:ajax. Inherits
- all a4j:ajax special options.</p>
+ <p>The <b>a4j:commandButton</b> combines the standard h:commandButton with our own
+ a4j:ajax. This not only reduces typing, but also inherits all a4j:ajax
+ special options.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandLink/commandLink.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandLink/commandLink.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/commandLink/commandLink.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -6,8 +6,9 @@
<ui:composition>
- <p>The combination similar to h:commandLink with f:ajax. Inherits
- all a4j:ajax special options.</p>
+ <p>The <b>a4j:commandLink</b> combines the standard h:commandLink with our own
+ a4j:ajax. This not only reduces typing, but also inherits all a4j:ajax
+ special options.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/jsFunction/jsFunction.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/jsFunction/jsFunction.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/jsFunction/jsFunction.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -6,11 +6,17 @@
<ui:composition>
- <p><b>a4j:jsFunction</b> component also designed to send Ajax
- requests, but allows to perform an the requests 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 a page is re-rendered when a user hovers over the names.</p>
+ <p>The <b>a4j:jsFunction</b> component creates a JavaScript function that
+ allows you to send JSF Ajax requests from any JavaScript. You define the
+ Ajax and JSF properties just like a4j:ajax, or a4j:commandButton, and
+ <b>a4j:jsFunction</b> creates the JavaScript for you. The component sends a
+ request using the standard JSF mechanisms. Note that this means a JSF form
+ is required.</p>
+
+ <p> The following example shows how to use <b>a4j:jsFunction</b> to create a
+ function named updateName. This is then called on mouseover of the
+ different names. This triggers the full round trip Ajax request and renders
+ the updated name.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/clientParam.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/clientParam.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/clientParam.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -5,12 +5,14 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>It is possible to use javascript variable of custom function for
- the 'value' attribute. In this case the 'noEscape' attribute should be
- set to true. When noEscape="true", the 'value' can contain any
- javascript expression or javascript function invocation and the result
- of them will be send to the server as a value of a4j:actionparam. The
- following example demonstrates how to assign the backing bean with
+ <p>Another great feature for the <b>a4j:param</b> component is the
+ ability to use JavaScript to assign the 'value' attribute. In this case the
+ 'noEscape' attribute should be set to true. When noEscape="true", the 'value'
+ can contain any JavaScript expression or JavaScript function. This will be
+ executed and the result will be sent to the server as the value of
+ a4j:param.</p>
+
+ <p>The following example demonstrates how to assign the backing bean with
browser screen size values.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/param.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/param.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/param.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -5,11 +5,10 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>a4j:actionparam is a component which extends regular f:param
- with the possibility to assign the value to the property of the manager
- bean directly using the assignTo attribute. Using this feature you can
- update model values without invoking even a single line of java code on
- the server side.</p>
+ <p>The <b>a4j:param</b> component extends the regular f:param
+ tag. The primary extension is the ability to assign a value to a property
+ on a managed bean directly using the assignTo attribute. Using this feature you can
+ update model values without invoking a single line code.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/skinChange.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/skinChange.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/param/skinChange.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -5,10 +5,9 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>You can use a4j:param not only with ajax components, but with
- non-ajax command components and for GET navigation components also. In
- the following example, the used skin of the demo is changed when the
- whole page is refreshed with the regular h:link.</p>
+ <p>You can also use <b>a4j:param</b> with non-ajax command components
+ including GET navigation components. In this example, the skin of the demo
+ is changed when using a standard h:link tag.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/poll/poll.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/poll/poll.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/poll/poll.xhtml 2011-03-15 14:56:45 UTC (rev 22225)
@@ -6,17 +6,14 @@
xmlns:rich="http://richfaces.org/rich">
<ui:composition>
- <p>a4j:poll is one of the way how you can organize the periodical
- polling of server data and updating the page. a4j:poll is a standard
- RichFaces Ajax component. Thus, you can use the same approach as for
- a4j:commandButton for example. I.e. you can use action attribute to
- invoke the action method and reRender attribute to update area(s) on
- the client when Ajax Response returns back. RichFaces uses the standard
- form based request, so the form around the a4j:poll component is
- required.</p>
- <p>The following example shows how the date and time is updated on
- the page based on the data taken from the server. To turn off polling,
- press "Stop Polling" button.</p>
+ <p>The <b>a4j:poll</b> component defines a way to periodically poll a server
+ in order to trigger state changes, or update parts of your page. You can
+ use the same options, and settings as the a4j:ajax or a4j:commandButton. So you
+ can set execute, and render attributes, as well as any normal JSF action
+ attributes. RichFaces uses a standard form based request, so the form around the
+ a4j:poll component is required.</p>
+ <p>The example below updates the date and time on the page based on the data on
+ the server. To turn off polling, press "Stop Polling" button.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
@@ -32,7 +29,7 @@
<ui:param name="hideLabel" value="Hide Bean Source" />
</ui:include>
<rich:panel>
- <b>NOTE:</b>polling is automatically disabled in this demo after one minute of working.
+ <b>NOTE:</b> polling is automatically disabled in this demo after one minute.
</rich:panel>
</ui:composition>
</html>
\ No newline at end of file
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22224 - branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/samples.
by richfaces-svn-commits＠lists.jboss.org
Author: ilya_shaikovsky
Date: 2011-03-15 08:15:43 -0400 (Tue, 15 Mar 2011)
New Revision: 22224
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/samples/grid-sample.xhtml
Log:
https://issues.jboss.org/browse/RF-10752
@Gleb checked
Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/samples/grid-sample.xhtml
===================================================================
--- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/samples/grid-sample.xhtml 2011-03-15 12:03:23 UTC (rev 22223)
+++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/samples/grid-sample.xhtml 2011-03-15 12:15:43 UTC (rev 22224)
@@ -13,7 +13,7 @@
border:none;
}
.pbody {
- width: 200px;
+ width: 180px;
}
</style>
<rich:panel>
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22223 - branches/RF-10753/examples/richfaces-showcase.
by richfaces-svn-commits＠lists.jboss.org
Author: artdaw
Date: 2011-03-15 08:03:23 -0400 (Tue, 15 Mar 2011)
New Revision: 22223
Modified:
branches/RF-10753/examples/richfaces-showcase/pom.xml
Log:
RF-10024: GAE is updated to 1.4.2 version
Modified: branches/RF-10753/examples/richfaces-showcase/pom.xml
===================================================================
--- branches/RF-10753/examples/richfaces-showcase/pom.xml 2011-03-15 06:25:13 UTC (rev 22222)
+++ branches/RF-10753/examples/richfaces-showcase/pom.xml 2011-03-15 12:03:23 UTC (rev 22223)
@@ -18,7 +18,7 @@
<name>Richfaces Examples: Richfaces Showcase Application</name>
<properties>
- <gae.version>1.4.0</gae.version>
+ <gae.version>1.4.2</gae.version>
</properties>
<dependencies>
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22222 - trunk/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid.
by richfaces-svn-commits＠lists.jboss.org
Author: SeanRogers
Date: 2011-03-15 02:25:13 -0400 (Tue, 15 Mar 2011)
New Revision: 22222
Modified:
trunk/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/grid.xhtml
Log:
Revised showcase text for rich:dataGrid - RFPL-1215
Modified: trunk/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/grid.xhtml
===================================================================
--- trunk/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/grid.xhtml 2011-03-15 06:20:22 UTC (rev 22221)
+++ trunk/examples/richfaces-showcase/src/main/webapp/richfaces/dataGrid/grid.xhtml 2011-03-15 06:25:13 UTC (rev 22222)
@@ -5,11 +5,11 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p>The component takes iterates a model as any other iteration
- component and outputs it the same way as <h:PanelGrid> does for
- inline data. To define grid properties and styles, use the same
- definitions as for <h:panelGrid>.</p>
- <p>The following example shows the dataGrid component in use:</p>
+ <p>The <b>rich:dataGrid</b> component accepts the same data sources as other iteration components
+ and renders them in a grid format, the same way as the <b>h:PanelGrid</b> component does for
+ in-line data. To define the grid's properties and styles, use the same
+ definitions as for the <b>h:panelGrid</b> component.</p>
+ <p>This example demonstrates basic use of the <b>rich:dataGrid</b> component.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
<ui:param name="src" value="#{demoNavigator.sampleIncludeURI}" />
@@ -18,4 +18,4 @@
<ui:param name="hideLabel" value="Hide Source" />
</ui:include>
</ui:composition>
-</html>
\ No newline at end of file
+</html>
13 years, 3 months
- 1
- 0
JBoss Rich Faces SVN: r22221 - trunk/examples/richfaces-showcase/src/main/webapp/richfaces/list.
by richfaces-svn-commits＠lists.jboss.org
Author: SeanRogers
Date: 2011-03-15 02:20:22 -0400 (Tue, 15 Mar 2011)
New Revision: 22221
Modified:
trunk/examples/richfaces-showcase/src/main/webapp/richfaces/list/lists.xhtml
Log:
Revised showcase text for rich:list - RFPL-1215
Modified: trunk/examples/richfaces-showcase/src/main/webapp/richfaces/list/lists.xhtml
===================================================================
--- trunk/examples/richfaces-showcase/src/main/webapp/richfaces/list/lists.xhtml 2011-03-15 06:15:30 UTC (rev 22220)
+++ trunk/examples/richfaces-showcase/src/main/webapp/richfaces/list/lists.xhtml 2011-03-15 06:20:22 UTC (rev 22221)
@@ -5,10 +5,11 @@
xmlns:ui="http://java.sun.com/jsf/facelets">
<ui:composition>
- <p><b>rich:list</b> component allows to build one of the HTML lists
- (UL, OL, DL) dynamically from backend data</p>
- <p>It accepts the same data types as the other iteration components
- and renders them according to <b>type</b> attribute.</p>
+ <p>The <b>rich:list</b> component allows to build lists
+ dynamically from back-end data. The lists can be
+ ordered lists, unordered lists, or definition lists.</p>
+ <p>The <b>rich:list</b> component accepts the same data sources as other iteration components
+ and renders them according to the <b>type</b> attribute.</p>
<ui:include src="#{demoNavigator.sampleIncludeURI}" />
<ui:include src="/templates/includes/source-view.xhtml">
@@ -19,4 +20,4 @@
</ui:include>
</ui:composition>
-</html>
\ No newline at end of file
+</html>
13 years, 3 months
- 1
- 0