June 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8272) when in multi sort mode, provide an option to render numbers in each sorted column that indicates the current sort precedence of the columns

by Ian Springer (JIRA)

when in multi sort mode, provide an option to render numbers in each sorted column that indicates the current sort precedence of the columns -------------------------------------------------------------------------------------------------------------------------------------------- Key: RF-8272 URL: https://jira.jboss.org/jira/browse/RF-8272 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Ian Springer For example, if a table is currently multi-sorted by three columns - Name, Description, and Price, there is no quick way to know for each of these three columns, whether it is the primary, secondary, or tertiary sort column. A tiny "1", "2", and "3" next to the up or down arrow icon would clear this up nicely. For the RHQ project, we currently have a custom sorting facet which supports this feature. The facet is applied to a column as follows: <rich:column> <f:facet name="header"> <onc:sortableColumnHeader sort="res.resourceType.name"> <h:outputText styleClass="headerText" value="Type"/> </onc:sortableColumnHeader> </f:facet> <h:outputText value="#{resourceComposite.resource.resourceType.name}"/> </rich:column> I've attached a screenshot that shows how the column headers are rendered with the little numbers. I am creating this issue, because we would prefer using a built-in RichFaces feature, rather than a custom facet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-8270) provide a way to render a commandButton based on a minimum and/or maximum number of rows currently selected in a rich:*dataTable

by Ian Springer (JIRA)

provide a way to render a commandButton based on a minimum and/or maximum number of rows currently selected in a rich:*dataTable -------------------------------------------------------------------------------------------------------------------------------- Key: RF-8270 URL: https://jira.jboss.org/jira/browse/RF-8270 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Ian Springer This is useful when a particular action only makes sense when a certain number of rows are selected - here are a few examples: 1) most CRUD actions only make sense when at least one row is selected 2) a diff/compare action would only make sense when at least two rows were selected For RHQ, we currently have a custom component for this but would prefer use something that was built-in to RichFaces. Here's what the usage of our component (onc:selectCommandButton) looks like (not the low and high attributes, which reflect the minimum and maximum rows that must be selected: <f:facet name="footer"> <rich:columnGroup> <rich:column colspan="4" width="100%"> <onc:selectCommandButton action="#{ResourceGroupOperationScheduleUIBean.unschedule}" value="UNSCHEDULE" target="selectedItems" styleClass="on-pager-button buttonsmall" low="1" rendered="#{ResourceGroupUIBean.permissions.control}"/> <onc:selectCommandButton action="#{ResourceGroupOperationScheduleUIBean.executeNow}" value="EXECUTE NOW" target="selectedItems" styleClass="on-pager-button buttonsmall" low="1" high="1" rendered="#{ResourceGroupUIBean.permissions.control}"/> </rich:column> </rich:columnGroup> </f:facet> However, I think a nicer way to implement this would be to add a new optional attribute to the rich:*dataTable components, e.g.: <rich:extendedDataTable selectedRowCount="#{MyManagedBean.selectedRowCount}" ... /> The extendedDataTable component would update this attribute any time the selection is changed by the GUI user. Then a standard commandButton could be used as follows: <h:commandButton value="MyAction" rendered="#{MyManagedBean.selectedRowCount eq 1}" .../> An alternative to a new 'selectedRowCount' attribute would be using the existing 'selection' attribute and adding a new getSelectedRowCount() method to the org.richfaces.model.selection.Selection interface that the 'selection' attribute updates. An example of what this option would look like: <rich:extendedDataTable selection="#{MyManagedBean.selection}" ... /> <h:commandButton value="MyAction" rendered="#{MyManagedBean.selection.selectedRowCount eq 1}" .../> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-8181) provide footer facets in all components which have header facets

by nimo stephan (JIRA)

provide footer facets in all components which have header facets ---------------------------------------------------------------- Key: RF-8181 URL: https://jira.jboss.org/jira/browse/RF-8181 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: nimo stephan Would be nice to provide facet:footers for ALL components which has a facet:header. For consistency, all components which have header-facets should also have footer-facets. For example, rich:modalPanel, rich:panel, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-8126) Development: subTable selection

by Anton Belevich (JIRA)

Development: subTable selection ------------------------------- Key: RF-8126 URL: https://jira.jboss.org/jira/browse/RF-8126 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.ALPHA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (RF-8102) Development: dataTable columns menus support

by Anton Belevich (JIRA)

Development: dataTable columns menus support -------------------------------------------- Key: RF-8102 URL: https://jira.jboss.org/jira/browse/RF-8102 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.BETA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (RF-7611) fix default column width assigned to extendedDataTable

by Prabhat Jha (JIRA)

fix default column width assigned to extendedDataTable ------------------------------------------------------ Key: RF-7611 URL: https://jira.jboss.org/jira/browse/RF-7611 Project: RichFaces Issue Type: Bug Components: component-tables Affects Versions: 3.3.1 Reporter: Prabhat Jha Fix For: 3.3.2.CR1 See the referenced forum entry. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (RF-7718) statuses grouping in 4.0

by Ilya Shaikovsky (JIRA)

statuses grouping in 4.0 ------------------------ Key: RF-7718 URL: https://jira.jboss.org/jira/browse/RF-7718 Project: RichFaces Issue Type: Feature Request Components: component-a4j-core Affects Versions: 4.0.0.ALPHA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Fix For: 4.0.0.BETA1 check Nick's sample on grouping statuses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-7538) enable submit button when all the required fields within the form/region are set propertly

by Gary Hu (JIRA)

enable submit button when all the required fields within the form/region are set propertly ------------------------------------------------------------------------------------------ Key: RF-7538 URL: https://jira.jboss.org/jira/browse/RF-7538 Project: RichFaces Issue Type: Feature Request Reporter: Gary Hu The submit button is not enabled until all the required fields within the form/region are set properly. I can think of two ways to implement it. 1) add a new attribute to a4j:form/a4j:rigion to indicate that if this feature is turned on/off. In addition, new attributes could be added to indicate the ids of the submit button, and/or ids of the required fields. For example: <a4j:form id="myForm" enableSubmitButtonForRequriedFields="true" submitButtonId="btnId" requiredFieldIds="id1,id2..." /> 2) add a new attribute to a a4j:commandButton to indicate if this feature is turned on/off. In addtion, new attributes could be added to indicate the ids of the form/region and/or the ids of the required fields. For example: <a4j:commandButton id="btnId" enableSubmitButtonForRequriedFields="true" parentidforrequiredfields="myForm" /> The example showed above means after all the required fields are set properly with the form "myForm" the button is enable. <a4j:commandButton id="btnId" enableSubmitButtonForRequriedFields="true" requiredFieldIds="id1, id2..." /> The example showed above means after all the required fields specified by the attribute "requiredFieldIds" are set properly the button is enabled. Of course, the attribute "enableSubmitButtonForRequriedFields" could be optional. So only the "parentidforrequiredfields" or "requiredFieldIds" is checked to determine if the button needs to be enabled/disable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (RF-7492) a4j:queue support for standard form submits as well as AJAX request

by Jay Balunas (JIRA)

a4j:queue support for standard form submits as well as AJAX request ------------------------------------------------------------------- Key: RF-7492 URL: https://jira.jboss.org/jira/browse/RF-7492 Project: RichFaces Issue Type: Feature Request Components: component-misc Affects Versions: 3.3.1 Reporter: Jay Balunas Fix For: 4.0.0.BETA1 a4j:queue does not currently support forwarding standard form requests through an a4j:queue. This means that input items that are ajax enabled may be processed through a queue, but if the user clicks submit on the form that request that fire before items in the queue. A user reported a work around. Use a4j:commandButton and then rerender the most of the page - not optimal. We need to create an FAQ for the work around and investigate the standard form support. Brainstorming: This behavior may not be possible on a global or page coped queue. A form scoped a4j:queue could behave like a4j:support and inject the needed behavior into the form tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-6524) maxRequestSize for richfile upload should be made configurable per component and not globally.

by sathay sayee (JIRA)

maxRequestSize for richfile upload should be made configurable per component and not globally. ---------------------------------------------------------------------------------------------- Key: RF-6524 URL: https://jira.jboss.org/jira/browse/RF-6524 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Environment: ALL Reporter: sathay sayee The Richfaces fileupload control currently has maxRequestSize attribute which can be passed as a init-param in the web.xml It would be better if it can be configured on a percontrol basis and not global. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2010