[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12802 at 9/9/13 5:12 AM:
----------------------------------------------------------
We are still in the process of Page Fragments refactoring, however it is coming to the end.
Following actions need to be done to finish refactoring, so it can be reviewed by you guys:
* finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
* pair program the most complex refactoring of {{r:calendar}} and refactor tests accordingly
* unify proposed {{Wait}} API for all page fragments
* unify {{AdvancedInteractions}} API for all page fragments
* after review of page fragments from you guys, complete Javadoc
I will cross particular action once it is completed.
was (Author: jhuska):
We are still in the process of Page Fragments refactoring, however it is coming to the end.
Following actions need to be done to finish refactoring, so it can be reviewed by you guys:
* finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
* pair program the most complex refactoring of {{r:calendar}} and refactor tests accordingly
* unify proposed {{Wait}} API for all page fragments
* unify {{AdvancedInteractions}} API for all page fragments
* after review of page fragments from you guys, complete Javadoc
I will cross the action once they are completed.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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, 9 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-12802:
----------------------------------
We are still in the process of Page Fragments refactoring, however it is coming to the end.
Following actions need to be done to finish refactoring, so it can be reviewed by you guys:
* finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
* pair program the most complex refactoring of {{r:calendar}} and refactor tests accordingly
* unify proposed {{Wait}} API for all page fragments
* unify {{AdvancedInteractions}} API for all page fragments
* after review of page fragments from you guys, complete Javadoc
I will cross the action once they are completed.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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, 9 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13126:
------------------------------------
The line where the NPE is being thrown:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav...
indicates that the column is null. Have you verified that your table works as expected if you drop the tableState property? Can you post your complete facelet definition for your EDT?
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be RF-4855 + RF-13094 and RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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, 9 months