[jira] [Commented] (WICKET-1177) partial ajax updates on repeater components

["Jens Zastrow (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410220#comment-13410220 ] 

Jens Zastrow commented on WICKET-1177:
--------------------------------------

btw. you can use a diff algorithm (e.g. the build in MyersDiff) to compare the id-lists of the old and new state and create the insert, remove javascript code. 
With this technique you should be able to handle all list-modifications....
                
> partial ajax updates on repeater components
> -------------------------------------------
>
>                 Key: WICKET-1177
>                 URL: https://issues.apache.org/jira/browse/WICKET-1177
>             Project: Wicket
>          Issue Type: Wish
>          Components: wicket
>    Affects Versions: 1.3.0-rc2
>            Reporter: Peter Ertl
>            Assignee: Matej Knopp
>
> I try to explain the problem using an example:
> Imagine having a guestbook page where you can add new user entries via ajax post...
> Assume we are using RefreshingView to display the user entries. Once a user submits a new post the view should not be re-rendered in the ajax response completely but only the new user entry.
> Technically it's easy to address the view items by using e.g. ListItem#setOutputMarkupId(true).
> However, things are more complicated.
> When the user clicks on the submit button a background ajax request is created and a form submit listener is invoked. There the new guestbook post is saved in the data model. Then you want to update the list with the new entry using target.addComponent(..) . Also, applying a yellow fade effect to the component would be cool as an visual indication for the user. However, there is no way I can think of to get the proper view item(s) for the model object (=new user entry).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira