From richfaces-svn-commits at lists.jboss.org Tue Apr 5 03:32:40 2011 Content-Type: multipart/mixed; boundary="===============7208285212559406942==" MIME-Version: 1.0 From: richfaces-svn-commits at lists.jboss.org To: richfaces-svn-commits at lists.jboss.org Subject: [richfaces-svn-commits] JBoss Rich Faces SVN: r22366 - in modules/docs/trunk/Component_Reference/src/main/docbook/en-US: extras and 1 other directories. Date: Tue, 05 Apr 2011 03:32:40 -0400 Message-ID: <201104050732.p357WeX6004328@svn01.web.mwc.hst.phx2.redhat.com> --===============7208285212559406942== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: SeanRogers Date: 2011-04-05 03:32:40 -0400 (Tue, 05 Apr 2011) New Revision: 22366 Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exa= m-Component_Reference-richmessage-Message_icons.css modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/t= abl-richmessages.xml Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Compo= nent_Reference-Drag_and_drop.xml modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Compo= nent_Reference-Output_and_messages.xml modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exa= m-Component_Reference-richmessage-richmessage_example.xml_sample modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exa= m-Component_Reference-richprogressBar-Initial_and_complete_states.xml_sample modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exa= m-Component_Reference-richprogressBar-Using_nested_child_components.xml_sam= ple modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exa= m-Component_Reference-richprogressBar-Using_the_label_attribute.xml_sample modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exa= m-Component_Reference-richtoolTip-Attaching_the_tool-tip.xml_sample modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/v= lst-richdragIndicator.xml Log: Completed up to Drag and Drop from Engineering review (RFPL-1380) including= message icon details (RFPL-1123) Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/cha= p-Component_Reference-Drag_and_drop.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Comp= onent_Reference-Drag_and_drop.xml 2011-04-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Comp= onent_Reference-Drag_and_drop.xml 2011-04-05 07:32:40 UTC (rev 22366) @@ -30,7 +30,7 @@ Use the dragIndicator parameter to customize the ap= pearance of a dragged object while it is being dragged. The dragIn= dicator parameter must point to the id identif= ier of a <rich:dragIndicator> component. If the dragIndicator attribute is not defined, the drag indicator= appears as a clone of the <rich:dragSource> compo= nent's parent control. - To bind data to the dragged object, use the dragValue attribute. The dragValue attribute specifies an item = in a data model, which is then bound to the parent component when it is dra= gged. This facilitates handling event data during a drop event. + To bind data to the dragged object, use the dragValue attribute. The dragValue attribute specifies a server= -side object, which is then bound to the parent component when it is dragge= d. This facilitates handling event data during a drop event. = @@ -70,7 +70,7 @@
<sgmltag><rich:dropTarget></sgmltag> - The <rich:dropTarget> component can be added t= o a component so that the component can accept dragged items. The dragged i= tems must support the <rich:dragSource> component,= and be of a compatible drop type. + The <rich:dropTarget> component can be added t= o a component so that the component can accept dragged items. The dragged i= tems must be defined with a compatible drop type for the <rich:= dragSource> component. =
@@ -89,7 +89,7 @@
Handling dropped data - To provide additional parameters for a drop event, use the dr= opValue attribute. + To provide additional parameters for the server-side drop event, use t= he dropValue attribute. The <rich:dropTarget> component raises the DropEvent server-side event when an object is dropped. The= event uses the following parameters: @@ -159,21 +159,8 @@
Basic usage - If included without any attributes specified, the drag indicator will = appear as an empty dotted outline, as shown in = + To use a drag indicator, define the inner content that appears during = a drag event. No additional attributes are required. If a drag indicator is= not used, a clone of the drag source is used instead. -
- An empty drag indicator - - - - - - - An empty drag indicator appears as an empty dotted outline. - - - -
=
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/cha= p-Component_Reference-Output_and_messages.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Comp= onent_Reference-Output_and_messages.xml 2011-04-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Comp= onent_Reference-Output_and_messages.xml 2011-04-05 07:32:40 UTC (rev 22366) @@ -11,8 +11,11 @@
<sgmltag><rich:message></sgmltag> - The <rich:message> component renders a single = message relating to another specific component. The message consists of two= parts, both of which are optional: the marker icon and the textual label. = The appearance of the message can be customized, and tool-tips can be used = for further information about the message. + The <rich:message> component renders a single = FacesMessage message instance added for the componen= t. The appearance of the message can be customized, and tool-tips can be us= ed for further information about the message. + + The <rich:message> component is rendered in th= e same way as the standard <h:message> component, = but allows separate styling of the message summary and detail. It allows un= ified icons to be set using background images in predefined classes. +
rich:message component @@ -30,67 +33,34 @@
Basic usage - The <rich:message> component needs the for attribute to point to the id identifier= of the related component. The message is displayed depending on the state = of the linked component's requests. + The <rich:message> component needs the for attribute to point to the id identifier= of the related component. The message is displayed after the Fa= cesMessage message instance is created and added for the client= identifier of the related component. - The <rich:message> component is automatically= rendered after an Ajax request, even without the use of an <a4= j:outputPanel> component. + The <rich:message> component is automatically= rendered after an Ajax request. This occurs without the use of an <a4j:outputPanel> component or a specific reference throug= h the render attribute of the Ajax request source. + + rich:message example + + + The example contains a text input for zip codes. The simple validatio= n requires the entered zip code to be between 4 and 9 characters long. The = <rich:message> component references the input box,= and reports any messages relating to the input validation. + +
=
Appearance - The passedLabel attribute contains a message to dis= play when there are no errors; that is, when validation passes successfully= . The showSummary attribute specifies whether to display= only a summary of the full message. The full message can be displayed in a= tool-tip when hovering the mouse over the summary. + The showSummary attribute specifies whether to disp= lay only a summary of the full message. The full message can be displayed i= n a tool-tip when hovering the mouse over the summary. - Facets are used to define the marker icons for different message state= s: + Use CSS (Cascading Style Sheets) to customize the appearance and icon = for the <rich:message> component. To use a custom = icon, set the background-image property to the icon gr= aphic, as shown in . Refer to for a complete list of style cla= sses for the <rich:message> component. - - - errorMarker - - - Defines the icon for messages with the error sev= erity class. - - - - - fatalMarker - - - Defines the icon for messages with the fatal sev= erity class. - - - - - infoMarker - - - Defines the icon for messages with the info seve= rity class. - - - - - passedMarker - - - Defines the icon for messages that are not of the error, fatal, info, or war= n severity classes. - - - - - warnMarker - - - Defines the icon for messages with the warn seve= rity class. - - - - - - rich:message example - - + + Message icons + + + The example demonstrates how an icon for an error message could be ad= ded using CSS. +
= @@ -135,7 +105,7 @@
<sgmltag><rich:messages></sgmltag> - The <rich:messages> components works similarly= to the <rich:message> component, but can display = validation messages for a group of components instead of just a single comp= onent. Refer to for details on the <rich:message> component. + The <rich:messages> components works similarly= to the <rich:message> component, but can display = all the validation messages added for the current view instead of just a si= ngle message. Refer to for details on the <rich:message><= /sgmltag> component.
rich:messages component @@ -154,68 +124,27 @@
Basic usage - The <rich:messages> component doesn't require= any extra attributes for basic usage. It displays all messages relating to= requests from components in the same container element. + The <rich:messages> component doesn't require= any extra attributes for basic usage. It displays all messages relating to= requests from components. - The <rich:message> component is automatically= rendered after an Ajax request, even without the use of an <a4= j:outputPanel> component. + To limit the messages to a specific component, use the for attribute to reference the component's identifier. + + To show only those messages that are not attached to specific componen= ts, set globalOnly=3D"true". + + + The <rich:messages> component is automaticall= y rendered after an Ajax request. This occurs without the use of an <a4j:outputPanel> component or a specific reference throu= gh the render attribute of the Ajax request source. +
=
Appearance - The <rich:messages> component displays error = messages for each validating component in the same container. The = passedLabel attribute contains a message to display when there ar= e no errors; that is, when validation for all components passes successfull= y. The layout attribute defines how the messages are pre= sented: either using list for a list layout, or table for a tabular layout. + The <rich:messages> component displays error = messages for each validating component in the same container. - All messages use the same state icons, specified by using facets in th= e same way as for the <rich:message> component: + The <rich:messages> component can be further = styled through CSS, the same as for the <rich:message> component. Refer to for an example of message styling, and refer to for a complete list of style classes for the <rich:me= ssage> component. - - - errorMarker - - - Defines the icon for messages with the error sev= erity class. - - - - - fatalMarker - - - Defines the icon for messages with the fatal sev= erity class. - - - - - infoMarker - - - Defines the icon for messages with the info seve= rity class. - - - - - passedMarker - - - Defines the icon for messages that are not of the error, fatal, info, or war= n severity classes. - - - - - warnMarker - - - Defines the icon for messages with the warn seve= rity class. - - - - - - rich:messages example - - -
=
@@ -251,9 +180,7 @@ =
Style classes and skin parameters - - The <rich:messages> component uses the same s= tyling as the <rich:message> component. Refer to <= xref linkend=3D"sect-Component_Reference-richmessage-Style_classes_and_skin= _parameters" /> for details. - +
= @@ -290,7 +217,7 @@
Basic usage - Basic usage of the <rich:progressBar> compone= nt requires only the value attribute, which points to th= e method that provides the current progress. + Basic usage of the <rich:progressBar> compone= nt requires the value attribute, which points to the pro= perty that holds the current progress value. When the value is greater than= or equal to the minimum value (0 by default), the progr= ess bar becomes active, and starts sending Ajax requests if in aja= x mode. Basic usage @@ -332,6 +259,7 @@ + - To define customized initial and complete states for the progress bar,= use the initial and complete facets.= The initial facet displays when the progress value is l= ess than or equal to the minimum value, and the complete= facet displays when the progress value is greater than or equal to the max= imum value. + Define the initial and finish fa= cets to customize the progress bar's appearance before progress has started= and after progress has finished. When the current progress bar value is le= ss than the minimum value, the initial facet is displaye= d. When the current progress bar is greater than the maximum value, the finish facet is displayed. - Initial and complete states + Initial and finished states
= -
- Using set intervals - - The <rich:progressBar> component can be set t= o constantly poll for updates at a constant interval. Use the inte= rval component to set the interval in milliseconds. The progress = bar is updated whenever the polled value changes. Polling is only active wh= en the enabled attribute is set to true. - - - Using set intervals - - -
- =
Update mode @@ -416,13 +334,24 @@ client - The progress bar updates on the client side, set using the JavaScri= pt API. + The progress bar must be explicitly updated on the client side thro= ugh the JavaScript API.
= +
+ Using set intervals + + The <rich:progressBar> component can be set t= o constantly poll for updates at a constant interval. Use the inte= rval component to set the interval in milliseconds. The progress = bar is updated whenever the polled value changes. Polling is only active wh= en the enabled attribute is set to true. + + + Using set intervals + + +
+ =
JavaScript API @@ -575,14 +504,14 @@
Attaching the tool-tip to another component - If not otherwise specified, the tool-tip is attached to the parent ele= ment in which it is defined. The for attribute is used t= o attach the tool-tip to another component, pointing to the target componen= t's id identifier. This allows the <rich:too= ltip> component to be specified outside the target element. Th= is approach is demonstrated in . + If not otherwise specified, the tool-tip is attached to the parent ele= ment in which it is defined. The target attribute is use= d to attach the tool-tip to another component, pointing to the target compo= nent's id identifier. This allows the <rich:= tooltip> component to be specified outside the target element.= This approach is demonstrated in . Attaching the tool-tip - The <rich:tooltip> component can alternativel= y be left unattached, and is instead invoked through an event handler on th= e target component. To leave the <rich:tooltip> co= mponent unattached, set attached=3D"false", and define the eve= nt handler to trigger the tool-tip on the target component. This approach i= s demonstrated in . When leaving the <rich:tooltip> component unattached, ensure it has an id identifie= r defined. If the <rich:tooltip> component is nest= ed inside the target element, it must be the last child. If it is defined o= utside the target element, it must be nested in an <a4j:form>= ; component. + The <rich:tooltip> component can alternativel= y be left unattached, and is instead invoked through an event handler on th= e target component. To leave the <rich:tooltip> co= mponent unattached, set attached=3D"false", and define the eve= nt handler to trigger the tool-tip on the target component. This approach i= s demonstrated in . When leaving the <rich:tooltip> component unattached, ensure it has an id identifie= r defined. If it is defined outside the target element, it must be nested i= n an <a4j:form> component. Unattached tool-tips @@ -593,10 +522,10 @@
Appearance - By default, the <rich:tooltip> component is p= ositioned intelligently based on the position of the mouse cursor. Use the = direction attribute to specify a corner of the target co= mponent at which to display the tool-tip instead. Possible values include <= literal>top-left, top-right, bottom-l= eft, and bottom-right. Use the horizo= ntalOffset and verticalOffset attributes to sp= ecify the horizontal offset and vertical offset at which to display the too= l-tip. + By default, the <rich:tooltip> component is p= ositioned intelligently based on the position of the mouse cursor. Use the = jointPoint attribute to specify a corner of the target c= omponent at which to display the tool-tip instead, and use the dir= ection attribute to specify the direction the tool-tip will appea= r relative to that corner. Possible values for both attributes are top-left, top-right, bottom-left, and bottom-right. Use the horizontalOff= set and verticalOffset attributes to specify t= he horizontal offset and vertical offset at which to display the tool-tip. - Use the hideEvent attribute to specify when the too= l-tip is hidden. The default value is none, so the tool-= tip remains shown. However, it can be linked to an event on the target comp= onent, such as the mouseout event. + Use the showEvent attribute to specify when the too= l-tip is shown. By default it appears when the attached component is hovere= d-over with the mouse. Use the hideEvent attribute to sp= ecify when the tool-tip is hidden. The default value is none, so the tool-tip remains shown. However, it can be linked to an event = on the target component, such as the mouseout event. Set followMouse=3D"true" to cause the tool-tip to follow = the user's mouse movements. @@ -726,7 +655,7 @@ - hide(event) + hide() Hide the tool-tip. Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras= /exam-Component_Reference-richmessage-Message_icons.css =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richmessage-Message_icons.css = (rev 0) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richmessage-Message_icons.css 2011-04-05 07:32:40 UT= C (rev 22366) @@ -0,0 +1,3 @@ +.rf-msg-err{ + background-image: url('#{facesContext.externalContext.requestContextPat= h}/images/icons/error.gif'); +} Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/ext= ras/exam-Component_Reference-richmessage-richmessage_example.xml_sample =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richmessage-richmessage_example.xml_sample 2011-04-0= 5 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richmessage-richmessage_example.xml_sample 2011-04-0= 5 07:32:40 UTC (rev 22366) @@ -1,8 +1,6 @@ - - - - - - - = - + + + + + Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/ext= ras/exam-Component_Reference-richprogressBar-Initial_and_complete_states.xm= l_sample =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richprogressBar-Initial_and_complete_states.xml_samp= le 2011-04-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richprogressBar-Initial_and_complete_states.xml_samp= le 2011-04-05 07:32:40 UTC (rev 22366) @@ -1,8 +1,8 @@ - + - - + + = Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/ext= ras/exam-Component_Reference-richprogressBar-Using_nested_child_components.= xml_sample =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richprogressBar-Using_nested_child_components.xml_sa= mple 2011-04-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richprogressBar-Using_nested_child_components.xml_sa= mple 2011-04-05 07:32:40 UTC (rev 22366) @@ -1,3 +1,3 @@ - + Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/ext= ras/exam-Component_Reference-richprogressBar-Using_the_label_attribute.xml_= sample =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richprogressBar-Using_the_label_attribute.xml_sample= 2011-04-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richprogressBar-Using_the_label_attribute.xml_sample= 2011-04-05 07:32:40 UTC (rev 22366) @@ -1 +1 @@ - + Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/ext= ras/exam-Component_Reference-richtoolTip-Attaching_the_tool-tip.xml_sample =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richtoolTip-Attaching_the_tool-tip.xml_sample 2011-0= 4-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/ex= am-Component_Reference-richtoolTip-Attaching_the_tool-tip.xml_sample 2011-0= 4-05 07:32:40 UTC (rev 22366) @@ -2,4 +2,4 @@ ... = - + Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinni= ng/tabl-richmessages.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/= tabl-richmessages.xml (rev 0) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/= tabl-richmessages.xml 2011-04-05 07:32:40 UTC (rev 22366) @@ -0,0 +1,146 @@ + + + + + Style classes (selectors) and corresponding skin parameters + + + + + + + + Class (selector) + Skin Parameters + Mapped CSS properties + + + + = + + + + + .rf-msgs + + + This class defines styles for the message itself. + + + + + + generalFamilyFont + font-family + + + generalSizeFont + font-size + + = + + + + + .rf-msgs-err + + + This class defines styles for an error message. + + + + + + errorColor + color + + = + + + + + .rf-msgs-ftl + + + This class defines styles for a fatal message. + + + + + + errorColor + color + + = + + + + + .rf-msgs-inf + + + This class defines styles for an information message. + + + + + + generalTextColor + color + + = + + + + + .rf-msgs-wrn + + + This class defines styles for a warning message. + + + + + + warningTextColor + color + + = + + + + + .rf-msgs-ok + + + This class defines styles for a basic OK mes= sage. + + + + + + generalTextColor + color + + = + + + + + .rf-msgs-sum + .rf-msgs-det + + + These classes define styles for the summary or details of a messa= ge. + + + + + + No skin parameters. + + = + + +
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/ski= nning/vlst-richdragIndicator.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/= vlst-richdragIndicator.xml 2011-04-05 00:21:23 UTC (rev 22365) +++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/= vlst-richdragIndicator.xml 2011-04-05 07:32:40 UTC (rev 22366) @@ -15,28 +15,28 @@ = - .rf-ind-drag + .rf-ind-drag.accept - This class defines styles for the indicator when it is being dragged. + This class defines styles for the indicator when it is over an accepta= ble drop target. = - .rf-ind-acpt + .rf-ind-drag.reject - This class defines styles for the indicator when it is over an accepta= ble drop target. + This class defines styles for the indicator when it is over an unaccep= table drop target. = - .rf-ind-rejt + .rf-ind-drag.default - This class defines styles for the indicator when it is over an unaccep= table drop target. + This class defines styles for the indicator when it is being dragged, = and is not over any drop targets. --===============7208285212559406942==--