I will try to understand better how things works. What I really need is to get the new browser size after a search form has been submitted so I can try to send the size properties in the search form (as you do in thee postback form) and then update the ClientProperties in... some way.
This would be a specific solution and maybe does not really need the ClientProperties to handle browser size cause I will have direct access to the form submitted value. If I have correctly understood, what you suggest is a more general solution where I could put some javascript in the main template page of my webapp that continuously send information about changes. Such a solution would send a lot of event from client to server and the most will not be considered... this is the way a swing app works but maybe it is "too much" for a webapp, isn't it? Anyway, I will investigate on the problem in next days and let you know. Thanks for support. On 1/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On 1/31/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote: > > ok, my project is using 1.3 shapshot in fact i can get the browser > > size properties. > > However, like you said, properties are refreshed just at the beginning > > of the session. > > I have tried to include the code found in BrowserInfoPage all in the > > 1.3 snapshot quickstart project: I have inserted: > > > > 1) <script> block inside <head> block in index.html with just the two > > lines of javascript that send browser size properties. > > 2) the onload in the <body> block. > > 3) the form postback in html and in java with just browser size properties > > > > well, no result, browser size is just refreshed at the beginning of > > the session, not at every reload that is what I am expecting. > > There is no such facility in Wicket, and very probably in no other > framework either. What you can do is write a piece of Java script that > reacts on changes, and sends any changes back to the server. It would > also send the current URL with it, so that right after updating, > Wicket redirects to the current URL again, so that a re-render of the > page would be done (this time with updated info). > > I think it is doable, though I lack the time currently to investigate > this further. Maybe you can try to implement this Daniele; a patch > would be welcome. > > Anyone else have ideas? > > Eelco > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
