November 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-5043) Test cases development

by Nick Belaevski (JIRA)

Test cases development ---------------------- Key: RF-5043 URL: https://jira.jboss.org/jira/browse/RF-5043 Project: RichFaces Issue Type: Sub-task Components: planning_all, QA-environment Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Tsikhon Kuprevich Fix For: 3.3.0 -- 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

16 years

3
3
0 / 0

[JBoss JIRA] Created: (RF-5029) Add metainformation to image

by Andrey Markhel (JIRA)

Add metainformation to image ---------------------------- Key: RF-5029 URL: https://jira.jboss.org/jira/browse/RF-5029 Project: RichFaces Issue Type: Sub-task Reporter: Andrey Markhel Assignee: Andrey Markhel -- 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

16 years

2
5
0 / 0

[JBoss JIRA] Created: (RF-5049) Bug fixing and testing 1

by Nick Belaevski (JIRA)

Bug fixing and testing 1 ------------------------ Key: RF-5049 URL: https://jira.jboss.org/jira/browse/RF-5049 Project: RichFaces Issue Type: Sub-task Components: planning_all Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 3.3.0 - Global queue enabled in web.xml is created only when another queue exists on the page - Queue and AJAX requests: dynamic addition do not work. Implement it or add descriptive warning for this case as an alternative - Test queues in portal environments -- 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

16 years

2
4
0 / 0

[JBoss JIRA] Created: (RF-5066) add more detailed JUnit tests for the UIExtendedDataTable

by Anton Belevich (JIRA)

add more detailed JUnit tests for the UIExtendedDataTable --------------------------------------------------------- Key: RF-5066 URL: https://jira.jboss.org/jira/browse/RF-5066 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Denis Morozov -- 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

16 years

3
4
0 / 0

[JBoss JIRA] Created: (RF-5060) add more detailed JUnit tests for the UIPanelBar

by Anton Belevich (JIRA)

add more detailed JUnit tests for the UIPanelBar ------------------------------------------------ Key: RF-5060 URL: https://jira.jboss.org/jira/browse/RF-5060 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich -- 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

16 years

2
4
0 / 0

[JBoss JIRA] Created: (RF-5050) 3.3.0.Beta1

by Nick Belaevski (JIRA)

3.3.0.Beta1 ----------- Key: RF-5050 URL: https://jira.jboss.org/jira/browse/RF-5050 Project: RichFaces Issue Type: Release Components: planning_all Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 3.3.0 Build release -- 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

16 years

2
3
0 / 0

[JBoss JIRA] Commented: (RF-398) Language correction

by Svetlana mukhina (JIRA)

[ https://jira.jboss.org/jira/browse/RF-398?page=com.atlassian.jira.plugin.... ] Svetlana mukhina commented on RF-398: ------------------------------------- Also have a look at this case, noticed by Max "Example of correct but confusing technical thing is http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/... which seem to refer to maven/java property names as D<propertyname> instead of just <propertyname>. Small things but anyone who has technical java experience would consider that weird and confusing." > Language correction > ------------------- > > Key: RF-398 > URL: https://jira.jboss.org/jira/browse/RF-398 > Project: RichFaces > Issue Type: Task > Components: doc > Affects Versions: 3.2.0 > Reporter: Svetlana mukhina > Assignee: Michael Sorokin > Priority: Minor > Fix For: 3.3.0 > > > Correct mistakes of xml markup, spelling and grammar in the guide -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Assigned: (RF-398) Language correction

by Svetlana mukhina (JIRA)

[ https://jira.jboss.org/jira/browse/RF-398?page=com.atlassian.jira.plugin.... ] Svetlana mukhina reassigned RF-398: ----------------------------------- Assignee: Michael Sorokin (was: Svetlana mukhina) Language and content of the component suggestionbox should be improved below there are comments of Max Anderson on this component, use it also: *Description* "The component adds on-keypress suggestions capabilities to any input text component (like <h:inputText> ). When a key is pressed in the field Ajax request is sent to the server. When the suggestion action returns a list of possible values, it pop ups them inside the <div> element bellow the input." Initial description is ok, but a bit vague (e.g. what is the point of this box) "in the field Ajax request is sent" is broken english. "pop ups them" is broken english. "bellow the input" is misspelled (http://en.wikipedia.org/wiki/Bellows ) and the input is missing a adjective or reference, should be "below the input component" My suggestion: "<rich:suggestionbox> allows you to have a list show up when the user is typing in a input text component (like <h:inputText>) to provide suggestions to the user to quickly fill in the text component. The component works by sending a ajax request to the server when an on-keypress event occurs and if the suggstion action returns a list of values these values will be shown as a list inside a <div> element below the input. The user can then either continue typing or select one of the suggestions which will then be used as the value of the input text component." The image is good, but shows a complex suggestion which is not described in the following example. The example does not describe what the values inside the returned List should be - readers would assume a List of Strings when reading the Java code, but looking at the example there is a property named "text". After reading the text multiple times, looking at the livedemo and reading some more I realize that if just the Java code example had shown that it would return a list of non-string elements it would have made sense much faster. In other words the Java examples should be as complete as possible and not just a single line comment. *Details of usage* ""var" - a collection name that provides access for inputting into a table in a popup" I guess what is meant here is: "variable name that will be used for each element in the returned suggestion collection. Can be used in the <h:dataTable> and "fetch" attribute" "There are also two size attributes ( "width" and "height" ) that are obligatory for the suggestion component. The attributes have initial Defaults but should be specified manually in order to be changed." That sentence is broken english. If they have initial defaults why are they obligatory ? And what usage is it to be told that to change a value you have to specfiy them ? Note: It also look like from the examples that the <div> element will actually be rendered as if inside a h:dataTable - that is actually never written anywhere. Just implied. > Language correction > ------------------- > > Key: RF-398 > URL: https://jira.jboss.org/jira/browse/RF-398 > Project: RichFaces > Issue Type: Task > Components: doc > Affects Versions: 3.2.0 > Reporter: Svetlana mukhina > Assignee: Michael Sorokin > Priority: Minor > Fix For: 3.3.0 > > > Correct mistakes of xml markup, spelling and grammar in the guide -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (RF-4855) extendedDataTable: wrong column width

by Juergen Zimmermann (JIRA)

extendedDataTable: wrong column width ------------------------------------- Key: RF-4855 URL: https://jira.jboss.org/jira/browse/RF-4855 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RF 3.2.2.SR1, Mojarra, 1.2_10, Facelets 1.1.15.B1, JDK 6u10, IE 7 Reporter: Juergen Zimmermann The column headers are truncated or wider than necessary. Screenshot will be attached: Column 1: wider Columns 2-4: truncated -- 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

16 years

2
4
0 / 0

[JBoss JIRA] Created: (RF-1396) Add late rendering support for Calendar in client mode

by Boris Kirzner (JIRA)

Add late rendering support for Calendar in client mode ------------------------------------------------------ Key: RF-1396 URL: http://jira.jboss.com/jira/browse/RF-1396 Project: RichFaces Issue Type: Feature Request Reporter: Boris Kirzner Current implementation always renders a calendar on page load even if popup is true. The rendering operation takes about 100ms in average. Thus, adding 10 calendar instances to a page causes additional 1 second delay in page loading. This is completely redundant on page load since in real production scenario most of the dates have a big probability to remain untouched. Calendar should support late rendering, i.e. popup should be actually rendered only after user clicks in image for the first time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2008