2013/5/28 Martin Grigorov <[email protected]>: > On Tue, May 28, 2013 at 10:41 AM, Martin Makundi < > [email protected]> wrote: > >> > You could not use normal form processing, I guess, as there will not be >> any >> > form components at server side... (they will be removed after list is >> > displayed). So, you will have to do some ticks to map cliente state with >> > server state. >> > >> > The examples above could be make to work for non read-only situations... >> > but maybe not using wicket default form processing machinery... >> >> Feels like reinventing the wheel at both serverside and html ;) >> >> > You can try to do this in >> > org.apache.wicket.markup.html.form.Form#process(IFormSubmitter) { >> > rebuild(); >> > super.process(formSubmitter); >> >} >> >> Ok. Will try something along these lines. >> > > You will need to call #inputChanged() to all FormComponents in your > ListView, because this method is called earlier than > Form#process(IFormSubmitter).
Could it be possible to hook onto an earlier event before/during process to allow form to perform that natively? ** Martin > > >> >> ** >> Martin >> > >> > >> > On Tue, May 28, 2013 at 11:32 AM, Martin Makundi < >> > [email protected]> wrote: >> > >> >> > You could use something that builds itself at client side... while at >> >> > server side is still very lightweight. >> >> > Something like >> >> > >> >> > http://www.antiliasoft.com/wicket-angular-demo/filtering >> >> > >> >> > See for explanation. >> >> > >> >> > http://www.antiliasoft.com/wicket-angular-demo/ >> >> >> >> This is mainly read-only? We would like to allow in general all wicket >> >> actions...ofcourse we will go brute force if necessary, but we would >> >> like to try first a wicket 'inline' component that rebuilds itself for >> >> form processing and rendering but evaporates its body on detach. >> >> >> >> ** >> >> Martin >> >> > >> >> > >> >> > On Tue, May 28, 2013 at 11:01 AM, Martin Makundi < >> >> > [email protected]> wrote: >> >> > >> >> >> Hi! >> >> >> >> >> >> Is it possible to implement a listview that evaporates on detach and >> >> >> builds itself again whenever one iterates over its items? >> >> >> >> >> >> We have a huge page with thuge listview and the >> >> >> serialization/deserialization of the structure slows down the page. >> >> >> >> >> >> The models are detachable and maybe the components could be too..? >> >> >> >> >> >> ** >> >> >> Martin >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: [email protected] >> >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > Regards - Ernesto Reinaldo Barreiro >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> > >> > >> > -- >> > Regards - Ernesto Reinaldo Barreiro >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
