[richfaces-svn-commits] JBoss Rich Faces SVN: r22237 - in branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces: autocomplete/samples and 10 other directories.

Author: jbalunas(a)redhat.com Date: 2011-03-15 21:38:50 -0400 (Tue, 15 Mar 2011) New Revision: 22237 Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/cachedAjax.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/clientFilter.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/samples/cachedAjax-sample.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/calendar.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/clientStylingDisablement.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/dataModel.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/fileUpload/imgUpload.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceInput/inplaceInput.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/inplaceSelect.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/samples/inplaceSelect-sample.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/samples/sliders-sample.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/sliders.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSpinner/spinners.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/samples/select-sample.xhtml branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/select.xhtml Log: RFPL-1219 updates to showcase text Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/cachedAjax.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/cachedAjax.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/cachedAjax.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,15 +5,16 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>Autocomplete component - simple Input component which provides suggestions during input.</p> - <p>Could works using three modes: + <p>The <b>rich:autocomplete</b> component looks like a simple input component, + but has advanced options and features to provide suggestions to the user during input.</p> + <p>There are three different <i>modes</i> for how it fetches suggestions: <ul> - <li>Client - preloads data to the client side and makes suggestions according to entered prefix on the client</li> - <li>Ajax - fetches the data on every input change using ajax requests</li> - <li>Cached Ajax - loads data via ajax to make suggestions when the prefix length satisfies minchars attribute. Then all the suggestions done at client side except the case when initial prefix changed or token entered. Then loads data again.</li> + <li><b>Client</b> - preloads data to the client and makes suggestions according to the entered prefix on the client</li> + <li><b>Ajax</b> - fetches the data on every input change using Ajax requests</li> + <li><b>Cached Ajax</b> - loads data via Ajax to make suggestions when the prefix length satisfies <i>minChars</i> attribute value. Then all the suggestions are handled at the client until the initial prefix is changed. At that point it will reload with the new prefix.</li> </ul> </p> - <p>Here is the sample for new cachedAjax mode. </p> + <p><b>1)</b> Autocomplete American state names using the cached Ajax mode with <i>minChars="2"</i>.</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/autocomplete/clientFilter.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/clientFilter.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/clientFilter.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,17 +5,18 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>Except the server-side <b>"autocomplete"</b> method which could - be used to collect suggestion strings according to entered prefix, <b>rich:autocomplete</b> - allows to define similar method for filtering at client side. It should - be defined using <b>clientFilterFunction</b> attribute which accepts - custom filter function name. Function should accepts two parameters <b>subString</b>(current - input value considering tokens) and <b>value</b>(currently iterated - item value) and return boolean flag which means if the value satisfies + <p>When a suggestion request is sent to the server via an Ajax call you + have full control over the suggestion list. Once that data is on the + client the default filter is <i>startsWith</i>. This + can be changed to any custom JavaScript filter you wish. This example + shows you how to define and call a custom filter for <i>contains</i> instead + of <i>startsWith</i>.</p> + <p>The <b>clientFilterFunction</b> attribute accepts + a custom JavaScript function name. This function should have two parameters; + <b>subString</b>(current input value considering tokens) and <b>value</b> + (currently iterated item value) and return boolean flag which means if the value satisfies the substring passed. The function will be called for every available - suggestion in order to construct new list of suggestions.</p> - <p>This sample shows how to change the client filtering to <b>"contains"</b> - instead of <b>"startsWith"</b></p> + suggestion in order to construct a new list of suggestions.</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/autocomplete/samples/cachedAjax-sample.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/samples/cachedAjax-sample.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/autocomplete/samples/cachedAjax-sample.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,31 +5,25 @@ xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich"> - <p>Default autocomplete in cachedAjax mode</p> <h:form> - <rich:autocomplete mode="cachedAjax" minChars="0" + <rich:autocomplete mode="cachedAjax" minChars="2" autocompleteMethod="#{autocompleteBean.autocomplete}" /> </h:form> - <p>Autocomplete without direct suggestions to input(<b>autoFill="false"</b>). - Also in the sample comma and space are input <b>tokens</b>, so separate - autocompletion requests will be fired for different parts in input</p> + <p><b>2)</b> Allows multiple selections using tokens ', and ' '. This means + you will be able to separate different values with a space or comma + and get a new suggestion for a second value. The <b>autoFill</b> + attribute is set to false so you will notice values are not automatically added.</p> <h:form> - <rich:autocomplete mode="cachedAjax" tokens=", " minChars="0" + <rich:autocomplete mode="cachedAjax" tokens=", " minChars="1" autofill="false" autocompleteMethod="#{autocompleteBean.autocomplete}" /> </h:form> - <p>In that sample <b>selectFirst</b> set to false so pressing enter - will not choose the value from list but just submit currently entered + <p><b>3)</b> With the <b>selectFirst</b> attribute set to false pressing enter + will not choose the value from list automatically, but just submit currently entered value.</p> <h:form> <rich:autocomplete mode="cachedAjax" tokens=", " minChars="0" autoFill="false" selectFirst="false" autocompleteMethod="#{autocompleteBean.autocomplete}" /> </h:form> - <fieldset><legend><b>NOTE:</b> </legend> The developer has - full control under filtering on server side according to prefix. But in - client and cachedAjax modes - just built-in startWith method used. In - near future the component will be updated with one more attribute which - will allow the developer to define client side comparator function to - customize that behavior.</fieldset> </ui:composition> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/calendar.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/calendar.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/calendar.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,11 +5,11 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p><b>rich:calendar</b> allows to select the date using monthly calendar - elements on pages. It is possible to use the component in a <b>popup or - inline mode.</b> At a popup mode Calendar is initially rendered as input for - date and button on the right side to call a popup. In case of an inline - mode, the monthly calendar is located on a page initially.</p> + <p>The <b>rich:calendar</b> component allows you to select a date using a + monthly calendar widget. It is possible to use the component in a <b>popup or + inline mode</b>. In popup mode the calendar is initially rendered as an input for + date with a button on the right side to trigger the popup. For inline + mode, the monthly calendar is rendered on the page initially.</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/calendar/clientStylingDisablement.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/clientStylingDisablement.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/clientStylingDisablement.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,8 +5,8 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>This simple example shows the way of client side dates - disablement and styling without dataModel usage.</p> + <p>This example shows how to define days that are disabled. In this example + we are using client side scripts to define the dates.</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/calendar/dataModel.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/dataModel.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/calendar/dataModel.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,18 +5,16 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>Calendar may use a special Data Model to provide data for - element rendering. You can re-define the default Calendar Model using - the dataModel attribute pointed to the object that implements + <p>The calendar may also use a special data model to provide data for + element rendering. You can re-define the default calendar model using + the <i>dataModel</i> attribute and point to an object that implements the CalendarDataModel interface.</p> - <p>In next simple example next rules applied using model:</p> + <p>In this example we are using a custom data model to implement the following + rules:</p> <ul> - <li>Weekend days are disabled (sunday and saturday) and uses bold - and italic text style.</li> - <li>Thuesday and Thursday are disabled also. (just RichFaces team - meeting days) So grayed out as busy days.</li> - <li>All the values in the past disabed and styled as boundary - dates.</li> + <li>Weekend days are disabled and use bold and italic text style.</li> + <li>Tuesdays and Thursdays are disabled, and grayed out to represent busy days.</li> + <li>All the values in the past are disabled and styled as boundary dates.</li> </ul> <ui:include src="#{demoNavigator.sampleIncludeURI}" /> <ui:include src="/templates/includes/source-view.xhtml"> @@ -39,20 +37,17 @@ <ui:param name="openLabel" value="View CalendarModelItem Source" /> <ui:param name="hideLabel" value="Hide CalendarModelItem Source" /> </ui:include> - <p>Calendar may use a special Data Model to provide data for - element rendering. You can re-define the default Calendar Model using - the dataModel attribute pointed to the object that implements - <b>CalendarDataModel</b> interface.</p> - <p>CalendarDataModel has the following methods:</p> + <p>There are two primary interfaces that make up the calendar data model.</p> + <p><i>CalendarDataModel</i>:</p> <ul> <li><b>CalendarDataModelItem[] getData(Date[])</b> is called every time when components need the next block of CalendarDataItems. That may - happens when the calendar is rendered, or when you navigate to the + happen when the calendar is rendered, or when you navigate to the next/previous month or in any other case when the calendar is - rendered. This method is called in an Ajax mode when the calendar - renders a new page.</li> + rendered. This method is called in Ajax mode when the calendar + renders for a new page.</li> </ul> - <p>CalendarDataModelItem provides the following methods:</p> + <p><i>CalendarDataModelItem</i>:</p> <ul> <li><b>Boolean isEnabled()</b> returns "true" if date is "selectable" on the calendar, the default implementation returns "true"</li> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/fileUpload/imgUpload.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/fileUpload/imgUpload.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/fileUpload/imgUpload.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,16 +5,14 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p><b>rich:fileUpload</b> is a component which provides files - upload functionality and extends functionality of standard <b>input</b> - with <b>type="file"</b>.</p> - <p>The next example shows you File Upload which allows you to - upload files to the server. Files number allowed to upload is managed - with <b>maxFilesQuantity</b> attribute. Every uploaded file should be - managed with <b>fileUploadListener</b> which is called after every - single file upload is finished.</p> - <fieldset><legend><b>Sample limitations</b></legend>This - example allows to download <b>up to 5 files</b>. The file extension is + <p>The <b>rich:fileUpload</b> component allows you to upload files from the users + machine to the server with various options.</p> + <p>This example allows you to upload files to the demo server. The number of + files allowed at once is managed with the <b>maxFilesQuantity</b> attribute. + Every uploaded file will be processed with a <b>fileUploadListener</b> which + is called after every single file upload operation is finished.</p> + <fieldset><legend><b>Example limitations</b></legend>This + example allows you to upload <b>up to 5 files</b>. The file extension is limited to <b>GIF, JPG, BMP, PNG</b> and the maximum size of each file must not exceed 100kB</fieldset> <ui:include src="#{demoNavigator.sampleIncludeURI}" /> @@ -34,10 +32,10 @@ web.xml:</b></p> <ul> <li><b>createTempFiles</b> boolean attribute which defines whether the - uploaded files are stored in temporary files or available in listener - just as byte[] data (false for this example).</li> + uploaded files are stored in temporary files or available in the listener + directly as byte[] data (false for this example).</li> <li><b>maxRequestSize</b> attribute defines max size in bytes of the - uploaded files (<u>1000000 for this example</u>).</li> + uploaded files (<i>1000000 for this example</i>).</li> </ul> </ui:composition> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceInput/inplaceInput.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceInput/inplaceInput.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceInput/inplaceInput.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,8 +5,12 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>InplaceInput is a simple input component which displays the current value as outputText and switches to inputText based representation after a defined event to allow editing this value. -You could use simplest examples below. For the first demo, just click on a label to edit the value and click somewhere outside the component to store this value(Or just press ENTER button).</p> + <p>The <b>rich:inplaceInput</b> component displays the current value rendered + as outputText and switches to inputText after a customizable event + (i.e. click) to allow editing this value. There are various other options + such as default text, and styling. For this example, click on a label + to edit the value and either click enter, or somewhere outside the component to store this + value.</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/inplaceSelect/inplaceSelect.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/inplaceSelect.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/inplaceSelect.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,7 +5,7 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p><b>Inplace</b> Select is a simple input component which displays current + <p>The <b>rich:inplaceSelect</b> component displays the current selected value as outputText and switches to Select based representation after a defined event to allow editing this value.</p> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/samples/inplaceSelect-sample.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/samples/inplaceSelect-sample.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inplaceSelect/samples/inplaceSelect-sample.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -6,9 +6,9 @@ xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich"> <h:form> - <p>Try the simplest example below. Just click on a label to edit + <p>In the example below click on the label to edit the value and click somewhere outside the component to store this - value(Or just press ENTER button).</p> + value.</p> <rich:panel style="width:220px;"> <f:facet name="header"> <h:outputText value="Simples select"></h:outputText> @@ -22,23 +22,18 @@ <f:selectItem itemValue="4" itemLabel="Option 5" /> </rich:inplaceSelect> </rich:panel> - <p>In that sample component customized in next way:</p> + <p>In the next example we have customized the component in the following ways:</p> <ul> <li><b>f:selectItems</b> tag is used to define a list of items to use.</li> - <li>Controls "save" and "cancel" are turned on with <b>showControls</b> + <li>Controls "save" and "cancel" are turned on with the <b>showControls</b> attribute</li> - <li><b>editEvent</b> set to dblclick and used to switch to edit - state.</li> - <li><b>saveOnSelect</b> defined as false causes component not to store - value right after choosing but wait till buttons will be used or - focus lost.</li> - <li><b>saveOnBlur</b> defined as false causes component to cancel new - value if it was chosen and focus was lost without save button - activation. That could be useful on interfaces where every change - causes long processing. And if use true value - it will works like in - spreadsheets where leaving the changed field causes new value to be - applied.</li> + <li><b>editEvent</b> is set to dblclick to trigger to edit the mode.</li> + <li><b>saveOnSelect</b> is set to 'false' so that the value will + not be stored until the "save" button is clicked.</li> + <li><b>saveOnBlur</b> is set to 'false' so that the value will + not be stored unless until the "save" button is clicked. This could + be useful on pages where every change could cause extended processing.</li> </ul> <rich:panel style="width:220px;"> <f:facet name="header"> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/samples/sliders-sample.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/samples/sliders-sample.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/samples/sliders-sample.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -10,7 +10,7 @@ <rich:inputNumberSlider value="50" /> - <p>Here is "minimalistic" input:</p> + <p>Here is "minimalistic" example:</p> <rich:inputNumberSlider value="50" showInput="false" enableManualInput="false" showBoundaryValues="false" @@ -21,7 +21,7 @@ <rich:inputNumberSlider value="500" width="500" maxValue="1000" step="50" showArrows="true" showTooltip="false" /> - <p>The same variant but the control disabled:</p> + <p>The same variant but the control is disabled:</p> <rich:inputNumberSlider value="500" width="500" maxValue="1000" step="50" showArrows="true" showTooltip="false" disabled="true" /> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/sliders.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/sliders.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSlider/sliders.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,8 +5,9 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>InputNumberSlider is a highly customizable component that is used to define numeric - input in a given range. You can use a slider or just type some value into an input field.</p> + <p>The <b>inputNumberSlider</b> is a highly customizable component that is used to define numeric + input in a given range. It is rendered as a slider or you can type in + a specific value into an optional input field.</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/inputNumberSpinner/spinners.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSpinner/spinners.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/inputNumberSpinner/spinners.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,8 +5,9 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p>InputNumberSpinner is a highly customizable component that is used to define a numeric - input in a given range. A user can use a spinner control or just type some text into an input field.</p> + <p>The <b>rich:inputNumberSpinner</b> is a highly customizable component that is used to define a numeric + input in a given range. It is rendered as a spinner control or you can enter + the value in the input field.</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/select/samples/select-sample.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/samples/select-sample.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/samples/select-sample.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -6,7 +6,7 @@ xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich"> <h:form> - <p>There is simple sample where select behaves as standard one:</p> + <p>This example shows a select component that behaves basically the same as the standard:</p> <rich:panel style="width:220px;"> <f:facet name="header"> <h:outputText value="Simples select"></h:outputText> @@ -19,9 +19,8 @@ <f:selectItem itemValue="4" itemLabel="Option 5" /> </rich:select> </rich:panel> - <p>There you could check keyboard filtering within the select - component. It allows to enter only valid items from the list. Wrong - input will be reseted.</p> + <p>In the next example you can manually enter values, and any invalid + entries are not allowed.</p> <rich:panel style="width:220px;"> <f:facet name="header"> <h:outputText value="Select with manual input"></h:outputText> Modified: branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/select.xhtml =================================================================== --- branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/select.xhtml 2011-03-15 23:04:14 UTC (rev 22236) +++ branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/select/select.xhtml 2011-03-16 01:38:50 UTC (rev 22237) @@ -5,14 +5,15 @@ xmlns:ui="http://java.sun.com/jsf/facelets"> <ui:composition> - <p><b>rich:select</b> component is designed to replace standard - h:selectOneMenu. Main features which differs from base component:</p> + <p>The <b>rich:select</b> component is designed to replace standard + h:selectOneMenu. It adds various features and options including core Ajax + functionality, and skinning. Some of the notable features are:</p> <ul> - <li>Skinned according to RichFaces standard principles. That + <li>Skinning following RichFaces standard principles. This allows the component to have unified look and feel across all the browsers.</li> - <li>Provides better navigation across select items using keyboard</li> - <li>Provides default label functionality which is common for all the RichFaces inputs.</li> + <li>Better navigation across select items using the keyboard</li> + <li>Default label functionality which is common for all the RichFaces inputs.</li> </ul> <ui:include src="#{demoNavigator.sampleIncludeURI}" />