[richfaces-issues] [JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12807046#comment-12807046 ] 

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

Using the jQuery _.css_ method to dynamically set css attributes sets the inline-style of an element.  This overrides the values in the stylesheet, which poses it's own set of problems when dealing with a responsive layout, as one can no longer rely on the media queries to set an elements height as the size of the viewport changes.

Some possible solutions:
# Manipulate the CSS stylesheet attributes directly through the DOM.  This would be gross.
# Dynamically generating and including a CSS stylesheet in the facelet renderer.  This does not solve the problem for styling the RichWidget.
# Reconsider the current layout approach, optimizing for ease of styling.

I will spend some time brainstorming on 3)
                
> 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 styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _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, are 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 administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira