[
https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Giberius updated RF-11916:
------------------------------
Description:
Situation:
1) extendDataTable with a verticall ScrollBar
2) Insert or delete record by insert/delete in myBean and by a re-render of the
table.
3) The re-render causes a full rebuild of the table in the DOM and the effect
is that the scrollbar goes up to the beginning.In fact this makes a scrollable
extendedDataTable not useful for inserting/deleting records.
Partial Table Render for extendedDataTable is available in RF 4.1 with a
construction like:
render="myTable@rows(myBean.listOfUpdateRows):myColumn"
This works fine for already available rows and indeed it is an UPDATE.
Also @body, @header and @footer are available for partial table update.
I would like to have a kind of partitial table INSERT and UPDATE where not the
whole table is "re-draw", only the record(s) are INSERTED or DELETED and where
the scroll position for the user visually stays the same. Maintaining the
scroll position is the reason for this request, a user should be able to
insert/delete rows any where in a scrollalbe table larger then the table height.
It could look like:
render="myTable@insert(myBean.Row)
render="myTable@delete(myBean.RowKey)
Also take care of the "selected" row:
* For deletes the RowKey is passed, so no problem
* For inserts one could consider:
- Pass RowKey as parameter and insert before/after the given RowKey
- Use the current "selected record"
E.g.current selected record:
* No record - then insert in first position
* A record selected - insert after selected records
The inserted record is anyway the new "selected row"
Also with a delete you should consider what the "selected record" should be if
a selected record is deleted.
I use the selected record (single selection mode) in insert/delete. For that I
made some changes to the JavaScript of the extendenDataTable.
If you have questions I will gladly elaborate on above.
was:
Situation:
1) extendDataTable with a verticall ScrollBar
2) Insert or delete record by insert/delete in myBean and by a re-render of the
table.
3) The re-render causes a full rebuild of the table in the DOM and the effect
is that the scrollbar goes up to the beginning.In fact this makes a scrollable
extendedDataTable not useful for inserting/deleting records.
Partial Table Render for extendedDataTable is available in RF 4.1 with a
construction like:
render="myTable@rows(myBean.listOfUpdateRows):myColumn"
This works fine for already available rows and indeed it is an UPDATE.
Also @body, @header and @footer are available for partial table update.
I would like to have a kind of partitial table INSERT and UPDATE where not the
whole table is "re-draw", only the record(s) are INSERTED or DELETED and where
the scroll position for the user visually stays the same. Maintaining the
scroll position is the reason for this request, a user should be able to
insert/delete rows any where in a scrollalbe table larger then the table height.
It could look like:
render="myTable@insert(myBean.Row)
render="myTable@delete(myBean.RowKey)
If you have questions I will gladly elaborate on above.
> extendedDataTable partial update => extend the functionality with INSERT and
> DELETE row where scroll position does not go up.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-11916
> URL: https://issues.jboss.org/browse/RF-11916
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Tom Giberius
>
> Situation:
> 1) extendDataTable with a verticall ScrollBar
> 2) Insert or delete record by insert/delete in myBean and by a re-render of
> the table.
> 3) The re-render causes a full rebuild of the table in the DOM and the effect
> is that the scrollbar goes up to the beginning.In fact this makes a
> scrollable extendedDataTable not useful for inserting/deleting records.
> Partial Table Render for extendedDataTable is available in RF 4.1 with a
> construction like:
> render="myTable@rows(myBean.listOfUpdateRows):myColumn"
> This works fine for already available rows and indeed it is an UPDATE.
> Also @body, @header and @footer are available for partial table update.
> I would like to have a kind of partitial table INSERT and UPDATE where not
> the whole table is "re-draw", only the record(s) are INSERTED or DELETED and
> where the scroll position for the user visually stays the same. Maintaining
> the scroll position is the reason for this request, a user should be able to
> insert/delete rows any where in a scrollalbe table larger then the table
> height.
> It could look like:
> render="myTable@insert(myBean.Row)
> render="myTable@delete(myBean.RowKey)
> Also take care of the "selected" row:
> * For deletes the RowKey is passed, so no problem
> * For inserts one could consider:
> - Pass RowKey as parameter and insert before/after the given RowKey
> - Use the current "selected record"
> E.g.current selected record:
> * No record - then insert in first position
> * A record selected - insert after selected records
> The inserted record is anyway the new "selected row"
> Also with a delete you should consider what the "selected record" should be
> if a selected record is deleted.
> I use the selected record (single selection mode) in insert/delete. For that
> I made some changes to the JavaScript of the extendenDataTable.
> If you have questions I will gladly elaborate on above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
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
