From jira-events at lists.jboss.org Wed Sep 25 01:02:45 2013
Content-Type: multipart/mixed; boundary="===============5790378125275187455=="
MIME-Version: 1.0
From: Brian Leathem (JIRA) <jira-events at lists.jboss.org>
To: richfaces-issues at lists.jboss.org
Subject: [richfaces-issues] [JBoss JIRA] (RF-13082) Change the orderingList
 component to use the new orderingList widget
Date: Wed, 25 Sep 2013 01:02:45 -0400
Message-ID: <JIRA.12495826.1373048205000.2881.1380085365098@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: JIRA.12495826.1373048205000@jira02.app.mwc.hst.phx2.redhat.com

--===============5790378125275187455==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


    [ https://issues.jboss.org/browse/RF-13082?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12807109#com=
ment-12807109 ] =


Brian Leathem commented on RF-13082:
------------------------------------

I made some compromises (ie. not vertically centering the picklist button c=
olumn) and this is the style rule needed to set the pick-list size:
{code}
  <style type=3D"text/css">
    .pick-list .scrollBox {
      max-height: 250px;  // or height
    }
  </style>
{code}

The above css style results in a scrollbar being added to the source and ta=
rget lists when the number of elements in the respective lists is sufficien=
tly large.  This works well in both the large and small (responsive) views.=
  With this re-factoring, we _could_ expose this value as a widget-option/f=
acelet-attribute.

{panel:bgColor=3D#FFFFCE}
*Note:* Setting the height of the .pick-list itself will lead to overlappin=
g content in responsive mode.
{panel}
                =

> Change the orderingList component to use the new orderingList widget
> --------------------------------------------------------------------
>
>                 Key: RF-13082
>                 URL: https://issues.jboss.org/browse/RF-13082
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) =

>          Components: component-selects
>            Reporter: Brian Leathem
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Attributes to be dropped in the RF5 implementation:
> * disabledClass
> * headerClass
> * itemClass
> * selectItemClass
> * listHeight
> * listWidth
> * listMaxHeight
> * listMaxWidth
> It is felt that the *Class attributes are redundant.  Custom component st=
yling can be achieved with the combination of the CSS class specified by th=
e _styleClass_ attribute, along with the relevant stateful CSS class (_disa=
bled_, _header_, _ui-selectee_, ui-selected_).
> Similarly the height/width CSS attributes are better set with CSS styles,=
 rather than via facelet attributes.
> Additionally, we should consider dropping the onlist* event handlers, as =
there is considerable overlap with their on* counterparts.  For instance, a=
re there really use cases that require differentiating between onmouveover =
and onlistmouseover?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

--===============5790378125275187455==--