rich:extendedDatatable frozenColumn should support pattern
----------------------------------------------------------

                 Key: RF-10546
                 URL: https://issues.jboss.org/browse/RF-10546
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: nimo stephan
            Priority: Minor


Imagine I have 8 columns (c1..c8):

I want to have c1, c2 frozen

AND

I want to have c3 till c5 not frozen (so scrollbar appears between the columns)

AND

I want to have c6 till c8 frozen.


This can be achieved something by providing a pattern as a value for 
frozenColumn.

For example:

<rich:extendedDatatable frozenColumn="1,2,6-8">
<!-- this column is be frozen -->
<rich:column id="1">
..
</rich:column>
<!-- this column is be frozen -->
<rich:column id="2">
..
</rich:column>
<!-- this column is NOT frozen -->
<rich:column id="3">
..
</rich:column>
<!-- this column is NOT frozen -->
<rich:column id="4">
..
</rich:column>
<!-- this column is NOT frozen -->
<rich:column id="5">
..
</rich:column>
<!-- this column is frozen -->
<rich:column id="6">
..
</rich:column>
<!-- this column is frozen -->
<rich:column id="7">
..
</rich:column>
<!-- this column is frozen -->
<rich:column id="8">
..
</rich:column>
</rich:extendedDatatable>

another solution could be to invite a frozen property for column-tag:

<rich:column frozen="true"> 

with this way, we can use frozen columns for all datatables (rich:datatable, 
rich:extendedDatatable,..). If column A is the neighbour (predeccesor or 
successor) of column B and both columns have frozen=false (default), then this 
should mean that the horizontal/vertical scrollbar should be within column A 
and column B.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to