[JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up.
11:04 p.m.
Tom Giberius created RF-11916:
---------------------------------
Summary: 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 hava a kind of partitial table INSERT and UPDATE where not the whole table
is "re-draw" by only the record(s) are INSERTED or DELETED and where the scroll
position for the user visually stays the same.
It could look like:
render="myTable(a)insert(myBean.Row)
render="myTable(a)delete(myBean.RowKey)
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
11:06 p.m.
[
https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.s...
]
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(a)insert(myBean.Row)
render="myTable(a)delete(myBean.RowKey)
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 hava a kind of partitial table INSERT and UPDATE where not the whole table
is "re-draw" by only the record(s) are INSERTED or DELETED and where the scroll
position for the user visually stays the same.
It could look like:
render="myTable(a)insert(myBean.Row)
render="myTable(a)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(a)insert(myBean.Row)
render="myTable(a)delete(myBean.RowKey)
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
11:24 p.m.
[
https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.s...
]
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(a)insert(myBean.Row)
render="myTable(a)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(a)insert(myBean.Row)
render="myTable(a)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(a)insert(myBean.Row)
render="myTable(a)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
11:40 a.m.
[
https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.s...
]
SBS JIRA Integration updated RF-11916:
--------------------------------------
Forum Reference: https://community.jboss.org/message/516078#516078
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(a)insert(myBean.Row)
render="myTable(a)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
8:31 p.m.
[
https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11916:
-------------------------------
Fix Version/s: 4.Future
Component/s: component-tables
Forum Reference: https://community.jboss.org/message/516078#516078 (was:
https://community.jboss.org/message/516078#516078)
Thanks for taking the time to file a feature request. We'll evaluate this in the near
future when we assess all the EDT feature requests.
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)
Components: component-tables
Reporter: Tom Giberius
Fix For: 4.Future
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(a)insert(myBean.Row)
render="myTable(a)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
2:57 p.m.
[
https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.s...
]
David BATTEUX commented on RF-11916:
------------------------------------
Hi Tom.
Do you have a solution to partially update extendedDataTable even if it's an INSERT or
an DELETE (without rebuild the table)?
If so, could you please contact me?!
Hope you read this in a close future.
Thanks!
David
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)
Components: component-tables
Reporter: Tom Giberius
Fix For: 5-Future
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(a)insert(myBean.Row)
render="myTable(a)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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4186
days inactive
4476
days old
richfaces-issues@lists.jboss.org
5 comments
4 participants
participants (4)
-
Brian Leathem (JIRA) -
David BATTEUX (JIRA)
-
SBS JIRA Integration (JIRA)
-
Tom Giberius (JIRA)