February 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Commented: (RF-9592) Review BaseRenderer/RendererUtils etc. Remove obsolete code from them.

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RF-9592?page=com.atlassian.jira.plugin.sy... ] Jay Balunas commented on RF-9592: --------------------------------- What kind of changes are we talking about here? We need to understand the impact of changes, to make sure there is not too much risk. > Review BaseRenderer/RendererUtils etc. Remove obsolete code from them. > ----------------------------------------------------------------------- > > Key: RF-9592 > URL: https://issues.jboss.org/browse/RF-9592 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: architectural > Affects Versions: 4.0.0.ALPHA1 > Reporter: Anton Belevich > Assignee: Alexander Smirnov > Fix For: 4.0.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-10224) rich:validator doesn't work with f:converter

by Juergen Zimmermann (JIRA)

rich:validator doesn't work with f:converter -------------------------------------------- Key: RF-10224 URL: https://issues.jboss.org/browse/RF-10224 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone5 Reporter: Juergen Zimmermann <rich:validator> inside <h:inputText> has no effect when <f:convertNumber> is also there. I have these tags: <h:inputText id="umsatz" value="..." converterMessage="..."> <f:convertNumber type="currency" currencyCode="EUR" maxFractionDigits="2"/> <rich:validator render="..."/> </h:inputText> Everything works fine if I'm using <f:ajax event="blur" render="..."/> instead of <rich:validator> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-9658) Components: specify localization information in requirements

by Nick Belaevski (JIRA)

Components: specify localization information in requirements ------------------------------------------------------------ Key: RF-9658 URL: https://jira.jboss.org/browse/RF-9658 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone4 Reporter: Nick Belaevski Assignee: Ilya Shaikovsky Fix For: 4.0.0.Milestone5 We need to specify in component requirements how will localization of component labels work. Proposed: - Message bundle used: either org.richfaces.Messages oor application message bundle - Names format: org.richfaces.<componentName>.<bundlePropertyName>, e.g. org.richfaces.calendar.APPLY_BUTTON_LABEL. Q.: should we use calendar or UICalendar? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Issue Comment Edited: (RF-7571) Client-side library: make code compatible with Portlet environment

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RF-7571?page=com.atlassian.jira.plugin.sy... ] Jay Balunas edited comment on RF-7571 at 2/9/11 3:29 PM: --------------------------------------------------------- Based on discussions with Nick, the required steps for this is too risky and complex for this stage of the release. We will need to review and plan for portlet support in a near term future release. Nick: What we need to get this working in portlets 1) use module pattern in JS - already done 2) overwrite CSS class names - add portlet namespaces to them - affects renderer code & CSS files 3) overwrite CSS class names in JavaScript - this is I believe the trickiest part Either we 1) overwrite or 2) externalize class names into hash passed into module pattern constructor These 2) & 3) parts affects almost all components - and I expected this to be covered by unified approach backed by CDK was (Author: jbalunas(a)redhat.com): Based on discussions with Nick, the required steps for this is too risky and complex for this stage of the release. We will need to review and plan for portlet support in a near term future release. What we need to get this working in portlets 1) use module pattern in JS - already done 2) overwrite CSS class names - add portlet namespaces to them - affects renderer code & CSS files 3) overwrite CSS class names in JavaScript - this is I believe the trickiest part Either we 1) overwrite or 2) externalize class names into hash passed into module pattern constructor These 2) & 3) parts affects almost all components - and I expected this to be covered by unified approach backed by CDK > Client-side library: make code compatible with Portlet environment > ------------------------------------------------------------------ > > Key: RF-7571 > URL: https://issues.jboss.org/browse/RF-7571 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component, core, portal > Affects Versions: 4.0.0.ALPHA1 > Reporter: Anton Belevich > Assignee: Alexander Smirnov > Fix For: 4.Future > > > use anonimous functions to hide internal code, pass all public methods names with ExternalContext.encodeNamespace(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-7571) Client-side library: make code compatible with Portlet environment

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RF-7571?page=com.atlassian.jira.plugin.sy... ] Jay Balunas updated RF-7571: ---------------------------- Fix Version/s: 4.Future (was: 4.0.0.CR1) > Client-side library: make code compatible with Portlet environment > ------------------------------------------------------------------ > > Key: RF-7571 > URL: https://issues.jboss.org/browse/RF-7571 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component, core, portal > Affects Versions: 4.0.0.ALPHA1 > Reporter: Anton Belevich > Assignee: Alexander Smirnov > Fix For: 4.Future > > > use anonimous functions to hide internal code, pass all public methods names with ExternalContext.encodeNamespace(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (RF-7571) Client-side library: make code compatible with Portlet environment

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RF-7571?page=com.atlassian.jira.plugin.sy... ] Jay Balunas commented on RF-7571: --------------------------------- Based on discussions with Nick, the required steps for this is too risky and complex for this stage of the release. We will need to review and plan for portlet support in a near term future release. What we need to get this working in portlets 1) use module pattern in JS - already done 2) overwrite CSS class names - add portlet namespaces to them - affects renderer code & CSS files 3) overwrite CSS class names in JavaScript - this is I believe the trickiest part Either we 1) overwrite or 2) externalize class names into hash passed into module pattern constructor These 2) & 3) parts affects almost all components - and I expected this to be covered by unified approach backed by CDK > Client-side library: make code compatible with Portlet environment > ------------------------------------------------------------------ > > Key: RF-7571 > URL: https://issues.jboss.org/browse/RF-7571 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component, core, portal > Affects Versions: 4.0.0.ALPHA1 > Reporter: Anton Belevich > Assignee: Alexander Smirnov > Fix For: 4.Future > > > use anonimous functions to hide internal code, pass all public methods names with ExternalContext.encodeNamespace(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-10459) Calendar: incorrect behavior of default label with incorrect date input

by Nick Belaevski (JIRA)

Calendar: incorrect behavior of default label with incorrect date input ----------------------------------------------------------------------- Key: RF-10459 URL: https://issues.jboss.org/browse/RF-10459 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Reporter: Nick Belaevski 1) Update input-demo/examples/calendar.xhtml, set enableManualInput=true 2) Open http://localhost:8080/input-demo/examples/calendar.jsf 3) Enter 'abc' and remove focus - defaultLabel is shown back, but 'abc' is expected to stay -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-10404) Client API: dataTable: problems with sorting/filtering API

by Ilya Shaikovsky (JIRA)

Client API: dataTable: problems with sorting/filtering API ---------------------------------------------------------- Key: RF-10404 URL: https://issues.jboss.org/browse/RF-10404 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: client-lib, component-tables Affects Versions: 4.0.0.Milestone5 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski filter() causes js error. (checked method and there is really undefined id variable) sort() - second parameter not considered. RichFaces.$('j_idt317:table').sort('name','ascending') - for dataTable always renders ascending state. But in EDT - switches to opposite occurs. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-10389) Autocomplete: update markup to remove positioned elements (WAS: rich:extendedDataTable - overflows table area in IE7)

by Ilya Shaikovsky (JIRA)

Autocomplete: update markup to remove positioned elements (WAS: rich:extendedDataTable - overflows table area in IE7) --------------------------------------------------------------------------------------------------------------------- Key: RF-10389 URL: https://issues.jboss.org/browse/RF-10389 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone4 Environment: RichFaces 4.0.0.20101110-M4 r.20021 Metamer 4.0.0.20101110-M4 r.20033 Mojarra 2.0.3-FCS Apache Tomcat 6.0.29 OpenJDK Runtime Environment 1.6.0_18-b18 @ Linux Internet Explorer 7.0 @ Win32 Reporter: Ilya Shaikovsky Assignee: Konstantin Mishin Fix For: 4.0.0.Milestone6 Attachments: Screenshot-29.png, Screenshot-30.png http://localhost:8080/metamer/faces/components/richExtendedDataTable/comp... http://localhost:8080/metamer/faces/components/richExtendedDataTable/comp... See attached screenshots. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-10423) richfaces-showcase: add sorting through JS API sample

by Ilya Shaikovsky (JIRA)

richfaces-showcase: add sorting through JS API sample ----------------------------------------------------- Key: RF-10423 URL: https://issues.jboss.org/browse/RF-10423 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.Milestone5 Reporter: Ilya Shaikovsky Assignee: Ilya Shaikovsky Fix For: 4.0.0.Milestone6 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2011