Nooooooooo. ONE part of the story is back button support. IN CASE you are using the second level session store thing that is default for 1.3 and 2.0 now, we don't need that multi-window support. If you don't use that, but e.g instead use the older page maps, you DO need it, as you don't want one window to be the reason another window expires. But the SECOND part of the story is the fact that we can recognize we're in separate windows in the first place. That's useful stuff to know at times! You can debate whether that should be turned on by default (I think it should, in order to support case one completely), but the functionality is useful without doubt imo. The API is still kind of awkward, but it is possible to e.g. use the page map to store information about the current user so that you can have separate users in separate windows, while still maintaining a nice programming model (alternatively, you could pass the current user around everywhere, but that would really suck).
Eelco On 11/22/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > i could do that.. > Just make a form post of every link > then store state in a special field (see 2.0 that has partial implementation > already) > > If you refresh the browsers url then we have to have the static mounts (that > we talked about) > and the page for that class is found and rendered (or not found then > created) > > johan > > > > On 11/22/06, Matej Knopp < [EMAIL PROTECTED]> wrote: > > Are you even sure tapestry is doing that? > > > > -Matej > > > > cowwoc wrote: > > > If you can't copy/paste that additional information anyway > (because > > > you'll get a Page Expired) then it shouldn't be visible at all so people > > > don't even make the mistake of including it. > > > > > > I agree with you that Wicket somehow has to know that window1 has > a > > > different state than window2 and if this isn't reflected somehow in the > > > URL then where is it stored? But I am also saying that Tapestry seems to > > > do that *somehow* and if we can do the same then we should do so. > > > > > > Gili > > > > > > Matej Knopp wrote: > > >> Again and again. > > >> What would do if you open the start.html page in two browsers windows? > > >> Or don't your users do that? The additional information in url is not > > >> there for fun. There is a good reason for that. > > >> > > >> And give us some time, after the refactor planed for 2.0 it should be > > >> possible to get rid of the "wicket" thing from url. > > >> > > >> -Matej > > >> > > >> cowwoc wrote: > > >>> heh, if I had to choose between: > > >>> > > >>> http://www.google.com/Start.html > > >>> > > >>> and > > >>> > > >>> > http://www.google.com/Main/Start?wicket:interface=:0:: > > >>> > > >>> I'd choose the first time time and time again. There is the > interface > > >>> part which I'd love to hide from users (they shouldn't ever be > > >>> explicitly pasting that anyway because you'll end up with Page > Expired) > > >>> and there is also the fact that they don't seem to require some sort > of > > >>> base context path or there is some sort of "magic" going on to hide > it. > > >>> Either way it looks better than Wicket :) > > >>> > > >>> Gili > > >>> > > >>> Matej Knopp wrote: > > >>>> Nice URLS? > > >>>> > > >>>> Well.. I don't know, to me it doesn't look that great. I mean it seem > to > > >>>> miss an information. What happens if you open the page in multiple > > >>>> browser windows? If the URL is same, how > > >>>> will tapestry reconstruct the data? > > >>>> > > >>>> And also, does the Tapestry 5 finally supports dynamically changing > > >>>> components hierarchy? Or nested components? Or is it still the > [1]page > > >>>> [0..n]Components approach? > > >>>> > > >>>> In Wicket the URLs will look much better in 2.0 than they look now - > as > > >>>> we will persist the mount path after requests, but it will take some > > >>>> time to implement. > > >>>> > > >>>> -Matej > > >>>> > > >>>> cowwoc wrote: > > >>>>> Two questions about: > > >>>>> > http://howardlewisship.com/blog/2006/10/tapestry-5-screencast-2.html > > >>>>> > > >>>>> 1) How did they get "instantaneous" page reloads working? > > >>>>> 2) How did they get their URLs to remain "nice" even though the > > >>>>> underlying state is changing? > > >>>>> > > >>>>> and what is the implications for Wicket? I suspect you guys have > seen > > >>>>> this before. Can you please comment on why Wicket does not do > something > > >>>>> similar? Is it something to do with the amount of client-side state > they > > >>>>> use? > > >>>>> > > >>>>> Thanks, > > >>>>> Gili > > >>>>> > > >>>>> > > >>>>> > > >>>>> > ------------------------------------------------------------------------ > > >>>>> > > >>>>> > ------------------------------------------------------------------------- > > >>>>> 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 > > >>>>> [email protected] > > >>>>> > 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 > > >>>> [email protected] > > >>>> > 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 > > >>> [email protected] > > >>> > 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 > > >> [email protected] > > >> > 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 > > > [email protected] > > > > 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 > > [email protected] > > 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 > [email protected] > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
