[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13082.
----------------------------
Verified. Closing.
> 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
> Labels: needs-qe
> 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
> * listWidth
> * onlist*
> 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 width CSS attributes are better set with CSS styles, rather than via facelet attributes.
> We will drop 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
12 years, 4 months
[JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13077?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13077.
----------------------------
Verified. Closing.
> Allow programatically configure Resource Mapping by exposing a service interface
> --------------------------------------------------------------------------------
>
> Key: RF-13077
> URL: https://issues.jboss.org/browse/RF-13077
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.).
> {code:java}
> public interface ResourceMapper {
> /**
> * @return null when no mapping should be involved
> public ResourceMapping mapResource(ResourceKey key);
> }
> public interface ResourceMapping {
> URL getURL(FacesContext context);
> }
> public interface StaticURLResourceMapping implements ResourceMapping {
> URL getURL();
> }
> public class FacesResourceMapping implements ResourceMapping {
> public ResourceKey getResourceKey() {
> ...
> }
> }
> {code}
> This way people may decide e.g. move all resources from given resource library to another library.
> This is related to RF-11543.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13063) RichFacesInputNumberSlider setValueByDragging
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13063?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13063:
----------------------------------
Verified also in 5.0.0.Alpha2.
Just a note: in 5.Alpha2 you can access the method as: {{mySlider.advanced().dragHandleToPointInTrace(55)}}, or just use {{mySlider.slideToValue(double)}}.
Closing.
> RichFacesInputNumberSlider setValueByDragging
> ---------------------------------------------
>
> Key: RF-13063
> URL: https://issues.jboss.org/browse/RF-13063
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: qe
> Affects Versions: 4.3.2
> Reporter: Bernard Labno
> Assignee: Jiří Štefek
> Priority: Minor
> Fix For: 4.3.4, 5.0.0.Alpha2
>
>
> In richfaces-qa/page-fragments there is RichFacesInputNumberSlider fragment. It would be great to be able to test setting value as percentage of width implemented as dragging the handle.
> One can do it like that:
> {code}
> ((JavascriptExecutor) GrapheneContext.getProxy()).executeScript("arguments[0].scrollIntoView(true);", weightSlider.getNumberSlider().getRoot());
> waitGui();
> final int width = weightSlider.getNumberSlider().getWidth();
> final int where = (int) (width * percentage);
> final WebElement handle = weightSlider.getNumberSlider().getHandleElement();
> final Action action = new Actions(GrapheneContext.getProxy()).clickAndHold(handle)
> .moveToElement(weightSlider.getNumberSlider().getRoot(), where, 0)
> .release(handle)
> .build();
> {code}
> It is very important to bring component into view before dragging.
> If you do not do that and component is very far to the right (you need to scroll to the right to see it) then calculations are wrong.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13063) RichFacesInputNumberSlider setValueByDragging
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13063?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13063.
----------------------------
> RichFacesInputNumberSlider setValueByDragging
> ---------------------------------------------
>
> Key: RF-13063
> URL: https://issues.jboss.org/browse/RF-13063
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: qe
> Affects Versions: 4.3.2
> Reporter: Bernard Labno
> Assignee: Jiří Štefek
> Priority: Minor
> Fix For: 4.3.4, 5.0.0.Alpha2
>
>
> In richfaces-qa/page-fragments there is RichFacesInputNumberSlider fragment. It would be great to be able to test setting value as percentage of width implemented as dragging the handle.
> One can do it like that:
> {code}
> ((JavascriptExecutor) GrapheneContext.getProxy()).executeScript("arguments[0].scrollIntoView(true);", weightSlider.getNumberSlider().getRoot());
> waitGui();
> final int width = weightSlider.getNumberSlider().getWidth();
> final int where = (int) (width * percentage);
> final WebElement handle = weightSlider.getNumberSlider().getHandleElement();
> final Action action = new Actions(GrapheneContext.getProxy()).clickAndHold(handle)
> .moveToElement(weightSlider.getNumberSlider().getRoot(), where, 0)
> .release(handle)
> .build();
> {code}
> It is very important to bring component into view before dragging.
> If you do not do that and component is very far to the right (you need to scroll to the right to see it) then calculations are wrong.
--
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
12 years, 4 months