If your visitors' browsers support the navigation bar (Opera natively, Firefox with an extension, MSIE users luck out) you can add link elements to the page header, stating where the browser needs to go (up, down, next, previous, first, last, etc.).
That way, the visitor can use the same navigation bar (application buttons) for both the next and the previous set.
Obviously you'll still need to create a duplicate for moronic browsers like Microsoft's excuse.
Main Topics
Browse All Topics





by: ahoffmannPosted on 2007-09-15 at 02:47:49ID: 19897065
> 1. I can use the browser "Back" button if the clerk wants to go back a page.
if you mean go back to previous rows it has to be a back button of your page not the browser's back button
> 2. I can click the "Next" button to display the next group of 20 vendors. This would be an application based button.
yes it has to be a button in your page
> 3. This seems awkward since the user would have to use a browser button and an application button. Yuck!
yes
> How do I implement the "Back" button without having to go back to the database and reselect the previous 20 vendors?
you have to store the selection in server-side session object and hand over a session id identifying that session object uniquely to the user/browser, this (transporting the session id) is most likely done using cookies (if security is not that important:)
> Can this be done by programmatically caching the pages locally after they are displayed in the browser?
yes, see previous description
> The "Back" button would access the saved pages? Can this be done?
either the pages back button, or if you have implemented sessions (see above) then the browser's back button works also