August 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13733) dataTable built-in sorting and filtering

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13733?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13733: ---------------------------------- Assignee: Brian Leathem > dataTable built-in sorting and filtering > ---------------------------------------- > > Key: RF-13733 > URL: https://issues.jboss.org/browse/RF-13733 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.7 > Reporter: Edward I > Assignee: Brian Leathem > Labels: gss > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > dataTable built-in sorting is still not implemented - only implemented in extendedDataTable so far. Is this still being planned? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11453) Add autocomplete functionality to the rich:select component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11453?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11453: ------------------------------------ I'd like to see a PoC to RF-11332 prior to following this select-based approach. I believe RF-11332 will provide an overall simpler resolution to the use case. > Add autocomplete functionality to the rich:select component > ----------------------------------------------------------- > > Key: RF-11453 > URL: https://issues.jboss.org/browse/RF-11453 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Cody Lerum > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Add an "autocompleteMethod" to rich:select -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11453) Add autocomplete functionality to the rich:select component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11453?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11453: ------------------------------- Sprint: 4.5.0.Beta1 - Upgrade Sprint > Add autocomplete functionality to the rich:select component > ----------------------------------------------------------- > > Key: RF-11453 > URL: https://issues.jboss.org/browse/RF-11453 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Cody Lerum > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Add an "autocompleteMethod" to rich:select -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11332) Improve AutoComplete component to support Object values separate from AutoCompleteinput field

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11332: ------------------------------- Sprint: 4.5.0.Beta1 - Upgrade Sprint > Improve AutoComplete component to support Object values separate from AutoCompleteinput field > --------------------------------------------------------------------------------------------- > > Key: RF-11332 > URL: https://issues.jboss.org/browse/RF-11332 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1 > Reporter: Cody Lerum > Assignee: Brian Leathem > Labels: gss > Fix For: 4.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > {code} > <rich:autocomplete id="client" value="#{newService.client}" autocompleteMethod="#{entitySearch.appEntityClients}" var="_a" fetchValue="#{_a}"> > <h:outputText value="#{_a.name}" /> > </rich:autocomplete> > {code} > Given the above code the fetchValue which is placed in the generated inputText box is what is actually submitted with the form. > To support POJO selects what is needed is to have a value and a valueLabel so that the fetchValue can be displayed to the user but the acutal converted object value is submitted to the form. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11453) Add autocomplete functionality to the rich:select component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11453?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11453: ------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > Add autocomplete functionality to the rich:select component > ----------------------------------------------------------- > > Key: RF-11453 > URL: https://issues.jboss.org/browse/RF-11453 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Cody Lerum > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Add an "autocompleteMethod" to rich:select -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11332) Improve AutoComplete component to support Object values separate from AutoCompleteinput field

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11332: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours Fix Version/s: 4.5.0.Beta1 Labels: gss (was: ) > Improve AutoComplete component to support Object values separate from AutoCompleteinput field > --------------------------------------------------------------------------------------------- > > Key: RF-11332 > URL: https://issues.jboss.org/browse/RF-11332 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1 > Reporter: Cody Lerum > Assignee: Brian Leathem > Labels: gss > Fix For: 4.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > {code} > <rich:autocomplete id="client" value="#{newService.client}" autocompleteMethod="#{entitySearch.appEntityClients}" var="_a" fetchValue="#{_a}"> > <h:outputText value="#{_a.name}" /> > </rich:autocomplete> > {code} > Given the above code the fetchValue which is placed in the generated inputText box is what is actually submitted with the form. > To support POJO selects what is needed is to have a value and a valueLabel so that the fetchValue can be displayed to the user but the acutal converted object value is submitted to the form. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11332) Improve AutoComplete component to support Object values separate from AutoCompleteinput field

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11332?page=com.atlassian.jira.plugin.s... ] Brian Leathem reopened RF-11332: -------------------------------- >From a pragmatic perspective, adding an extra hidden input to the autocomplete for use with the converter is likely the _simplest_ solution for the given use case. As such I'm re-opening this issue. If after an initial PoC it does not prove to be a simpler approach than the select-based RF-11453 we can re-close the issue. > Improve AutoComplete component to support Object values separate from AutoCompleteinput field > --------------------------------------------------------------------------------------------- > > Key: RF-11332 > URL: https://issues.jboss.org/browse/RF-11332 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1 > Reporter: Cody Lerum > Assignee: Brian Leathem > > {code} > <rich:autocomplete id="client" value="#{newService.client}" autocompleteMethod="#{entitySearch.appEntityClients}" var="_a" fetchValue="#{_a}"> > <h:outputText value="#{_a.name}" /> > </rich:autocomplete> > {code} > Given the above code the fetchValue which is placed in the generated inputText box is what is actually submitted with the form. > To support POJO selects what is needed is to have a value and a valueLabel so that the fetchValue can be displayed to the user but the acutal converted object value is submitted to the form. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13733) dataTable built-in sorting and filtering

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13733?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13733: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > dataTable built-in sorting and filtering > ---------------------------------------- > > Key: RF-13733 > URL: https://issues.jboss.org/browse/RF-13733 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.7 > Reporter: Edward I > Labels: gss > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > dataTable built-in sorting is still not implemented - only implemented in extendedDataTable so far. Is this still being planned? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13733) dataTable built-in sorting and filtering

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13733?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13733: ------------------------------- Sprint: 4.5.0.Beta1 - Upgrade Sprint > dataTable built-in sorting and filtering > ---------------------------------------- > > Key: RF-13733 > URL: https://issues.jboss.org/browse/RF-13733 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.7 > Reporter: Edward I > Labels: gss > Fix For: 4.5.0.Beta1 > > > dataTable built-in sorting is still not implemented - only implemented in extendedDataTable so far. Is this still being planned? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13758) RF 4.5 with MyFaces, CSS not loaded

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13758?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13758: ------------------------------- Sprint: 4.5.0.Beta1 - Bug Fix Sprint, 4.5.0.Beta1 - Upgrade Sprint (was: 4.5.0.Beta1 - Bug Fix Sprint) > RF 4.5 with MyFaces, CSS not loaded > ----------------------------------- > > Key: RF-13758 > URL: https://issues.jboss.org/browse/RF-13758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Matej Novotny > Assignee: Michal Petrov > Priority: Critical > Labels: myfaces, needs-qe > Fix For: 4.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When you use MyFaces as JSF implementation, RF fail to get CSS files hence the components are displayed as plain text. > I tried this (among others) with simpleapp which I modified by adding a simple rich:panel. With Mojarra the css for panel was received and panel was displayed correctly. Then I modified pom.xml to use MyFaces. The app can be deployed but the panel is just a plain text and page contains no css for styling. > This can be reproduced with Metamer/simpleapp/showcase. > Please see steps to reproduce for reproducers with Metamer and simpleapp. > Showcase reproducer is more complicated due to RF-13757. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 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 August 2014