November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Brian Leathem updated RF-4308: ------------------------------ Labels: low_hanging_fruit order picklist sort (was: order picklist sort) > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1 > Reporter: Martin Höller > Labels: low_hanging_fruit, order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Brian Leathem updated RF-4308: ------------------------------ Component/s: component-selects > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1 > Reporter: Martin Höller > Labels: order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Brian Leathem updated RF-4308: ------------------------------ Affects Version/s: 5.0.0.Alpha1 4.3.4 > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1 > Reporter: Martin Höller > Labels: order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Brian Leathem commented on RF-4308: ----------------------------------- RichWidget issue [#137|https://github.com/richwidgets/richwidgets/issues/137] has been resoloved; the client-side hook is now in place. Further work required to resolve this issue involves: # Extending [ClientSelectItem|https://github.com/richfaces/richfaces/blob/master/frame...] to track the sequence number of the Selectitem in the pick list # Adding a _data-rf-index_ attribute to the items in the pick list [CDK template|https://github.com/richfaces/richfaces/blob/master/framework/src...] # Adding a _sortFunction_ option to the pick-list widget invocation in the [pick-list-bridge|https://github.com/richfaces/richfaces/blob/master/frame...] ---- In the mean time, a workaround would be to implement your own pick list widget _sortFunction_ by listening for the widget _create_ event: {code} $('<my-selector>').on('picklist', 'create', function(a, b) { return ... }); {code} A concrete example of this looks like: {code} $('#list').on('picklistcreate', function(event, ui) { $('#list').pickList('option', 'sortFunction', function(a, b) { return $(a).data('key') - $(b).data('key'); }); }); {code} > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.2.2 > Reporter: Martin Höller > Labels: order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Brian Leathem commented on RF-4308: ----------------------------------- If we resolve RichWidget issue [#137|https://github.com/richwidgets/richwidgets/issues/137] with the proposed javascript callback method, then the RichFaces 5 picklist CDK template could define a _data-index_ attribute, and the widget-bridge could implement a sort callback that sorted on that _data-index_ attribute. Using this sort would be activated by setting the _orderable = false_ facelet attribute. > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.2.2 > Reporter: Martin Höller > Labels: order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Brian Leathem updated RF-4308: ------------------------------ Fix Version/s: 5-Tracking (was: 3.Future) > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.2.2 > Reporter: Martin Höller > Labels: order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13352) Introduce @Category(FailingOnFirefox.class) to pom.xml

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13352: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Introduce @Category(FailingOnFirefox.class) to pom.xml > ------------------------------------------------------ > > Key: RF-13352 > URL: https://issues.jboss.org/browse/RF-13352 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Macko > Assignee: Lukáš Macko > Fix For: 5.0.0.Alpha2 > > > Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=c...], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests. > It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope

by Mohammad Weshah (JIRA)

[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ] Mohammad Weshah edited comment on RF-13323 at 11/18/13 11:57 AM: ----------------------------------------------------------------- default Jboss AS 7.1 jsf API (2.1.7) Java 1.6.0_24-b07 64bit was (Author: wish79): default Jboss AS 7.1 jsf API (2.1.7) > FileUploadEvent listener reset the list value with Viewscope > ------------------------------------------------------------ > > Key: RF-13323 > URL: https://issues.jboss.org/browse/RF-13323 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: Jboss 7.1 > Richfaces 4.3.4 > JSF 2.1.9 > > Reporter: Mohammad Weshah > Assignee: Jiří Štefek > Labels: rich:fileUpload > Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war > > > Hello All, > i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow : > > {code} > protected List<UploadedImage> files = new ArrayList<UploadedImage>(); > > public void FileUploadlistener(FileUploadEvent event) throws Exception { > UploadedFile item = event.getUploadedFile(); > UploadedImage file = new UploadedImage(); > file.setLength(item.getData().length); > file.setName(item.getName()); > file.setData(item.getData()); > > files.add(file); > } > {code} > > but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ? > > Regards > Wish79 -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope

by Mohammad Weshah (JIRA)

[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ] Mohammad Weshah commented on RF-13323: -------------------------------------- default Jboss AS 7.1 jsf API (2.1.7) > FileUploadEvent listener reset the list value with Viewscope > ------------------------------------------------------------ > > Key: RF-13323 > URL: https://issues.jboss.org/browse/RF-13323 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: Jboss 7.1 > Richfaces 4.3.4 > JSF 2.1.9 > > Reporter: Mohammad Weshah > Assignee: Jiří Štefek > Labels: rich:fileUpload > Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war > > > Hello All, > i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow : > > {code} > protected List<UploadedImage> files = new ArrayList<UploadedImage>(); > > public void FileUploadlistener(FileUploadEvent event) throws Exception { > UploadedFile item = event.getUploadedFile(); > UploadedImage file = new UploadedImage(); > file.setLength(item.getData().length); > file.setName(item.getName()); > file.setData(item.getData()); > > files.add(file); > } > {code} > > but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ? > > Regards > Wish79 -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13356) ExtendedDataTable: row height strechted to 100% of the table height

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13356: ------------------------------- Summary: ExtendedDataTable: row height strechted to 100% of the table height (was: RF-8602 Reproduced in 4.3.3.Final) > ExtendedDataTable: row height strechted to 100% of the table height > ------------------------------------------------------------------- > > Key: RF-13356 > URL: https://issues.jboss.org/browse/RF-13356 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > > The same as in the parent issue: > Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing). -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013