On 1/23/06, Srini Pillai <[EMAIL PROTECTED]> wrote: > ...but looks > like we have to code our own tag... Thanks anyway :)
At least for the display of pages and the whole next/last stuff, make this an open source tag:) I just haven't gotten around to making one myself. It should take something like: sizeOfCollection maxRowsDisplayed currentPage url based on that information it should be pretty easy to create a nice tag that generates google-like page numbers, first, next, last, previous. etc. My thought was the tag would generate those links using the url passed in and append the appropriate pageNumber. On the server side there would be the use of a "PagationObject" that holds that same information listed above in Session scope. When the user clicks on one of the links from the tag it can figure out based on the pageNumber submited in the link what rows to retrieve from the db. The display part into the table should be pretty easy. For that we could just steal and tweak the display tag code. To me this would be a really nice tag. If you/we/whoever wanted to really go crazy, we could provide a PagationServlet that handles almost all of this but it would obviously then mean a lot more information would have to be passed into the tag such as... "collectionName" "classNameToCallForCollection" "methodNameToCall" or something along those lines. Then our Servlet along with the Pagation object could use reflection to execute the appropriate method to get the List and put it into request scope. (Obviously the developer would still have to make sure to code an appropriate method somewhere that got the Collection based off the row range passed to it). Tie this all in with Ajax to update the display and you have a real winner:) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
