On 1/6/06, Jonathan Locke <[EMAIL PROTECTED]> wrote:
no, actually i cant. rebuilding a page from constructor arguments just means that you lose all the interaction that happened on the page. this is where wicket shines - the user interacts with components that are isolated from the page and keep their own state. i went through a few pages i recently wrote to see how feasible this would be, and it was possible in a few situations, but in most it would not be. even something as simple as a dataview: the dataprovider pulls out page 4 which consists of 10 detachable models. in order to reconstruct that you would have to keep the ids of the 10 objects the models represent and store them somewhere, then you would need a way to initialize the data provider to load those particular 10 objects when the dataview requests page 4 after being reconstructed ( you need to fake it because page 4 at a later time does not insure the same 10 objects). it seems too much trouble to go through personally.
but then you have the situation where those same critics are now saying that this newly added feature solves nothing because its too limiting. and look at all the trouble we have to go through to get it working, i dont think converting all links to posts is trivial.
-Igor
it definitely can get harder. but it depends on the page. you can
imagine a pretty complex page too where the whole page can be
reconstructed in the correct state from just the page constructor
arguments... you just save the arguments and you can rebuild from that.
no, actually i cant. rebuilding a page from constructor arguments just means that you lose all the interaction that happened on the page. this is where wicket shines - the user interacts with components that are isolated from the page and keep their own state. i went through a few pages i recently wrote to see how feasible this would be, and it was possible in a few situations, but in most it would not be. even something as simple as a dataview: the dataprovider pulls out page 4 which consists of 10 detachable models. in order to reconstruct that you would have to keep the ids of the 10 objects the models represent and store them somewhere, then you would need a way to initialize the data provider to load those particular 10 objects when the dataview requests page 4 after being reconstructed ( you need to fake it because page 4 at a later time does not insure the same 10 objects). it seems too much trouble to go through personally.
i personally would probably not use this feature even on a high volume
site, perhaps unless it truly had to be clustered. but it seems not too
hard to provide and it gives users options and critics (who may or may
not be well informed) less to find lacking.
but then you have the situation where those same critics are now saying that this newly added feature solves nothing because its too limiting. and look at all the trouble we have to go through to get it working, i dont think converting all links to posts is trivial.
-Igor
