Hadass, This is possible with Wt, and the mechanism to be used is what we call the 'internal path' API. Some features of internal path: - The browser's back/forward buttons trigger the internal path changed signal, which you can use to display appropriate content on your page - internal paths enables the user to bookmark the page - internal paths enables search engines to index your site - links from external pages pointing to URLs such as http://www.webtoolkit.eu/wt#/documentation will work, as the /documentation path will be interpreted as the internal path - The link http://www.webtoolkit.eu/wt/documentation is equivalent to the one above and will also work for non-ajax browsers (such as search engines) - internal path avoids flicker of your screen by using Ajax to update the contents rather than reloading the full page when pressing forward/back
So if you display a page that you want a user to be bookmarkable or otherwise directly reachable, just set the internal path to something you can later interpret to display the appropriate contents. Listen to the internal path signals, and display the right content every time the signal is fired. It means that the user pressed forward/back, or selected a bookmark. For an example use of the internal path API, look at WMenu.C Regards, Wim. 2009/12/7 hadass yaari <[email protected]>: > Hey koen, > > I probably didn't explain good. The pages will be created in runtime. > I have a DB - the user will ask for info from DB (query) and I will have to > display the result. > What is the best way to do that.? Right now I just clear the screen and > display the info. But if the user will want to come back to the page he was > before in, he won't be able because it's the same page just with different > data. > | want to be able to navigate from page to page. > Is there a way to give as a path also parameters for page - I mean to create > dynamic page this way: a page will be called with parameters and will return > the page with the wanted data. That would be the perferct way. Basically > this way can be implemented but is it supported by the WT? > Thanks, > Hadas > > > Hey Hadass, > > 2009/12/1 hadass yaari <[email protected]>: >> Hello koen, >> I would like the pages to be displayed in the same window. I also wants to >> navigate back if I want to the pages that I've been in. This why I want to >> create this pages and not just to clear the screen and show other things >> in >> the same page. > > Then it sounds like you could use the same or a similar setup as the > homepage (which also is organized as different pages where you can > navigate back and forward) ? > > Technically, it does "clear the screen and show other things", but the > user does not really notice this ? > > You can either use the internal path API directly, or through a WMenu > + WStackedWidget. > > Regards, > koen > > ------------------------------------------------------------------------------ > Join us December 9, 2009 for the Red Hat Virtual Experience, > a free event focused on virtualization and cloud computing. > Attend in-depth sessions from your desk. Your couch. Anywhere. > http://p.sf.net/sfu/redhat-sfdev2dev > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > > ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
