It should be possible to combine Paginator and ImageLoader. It all
depends on how you want to structure the Paginator's template and the
markup in the paginated area. Once the Paginator is rendered, its
generated html elements will be available to wire up the ImageLoader.
However, while I'm not an ImageLoader expert, it appears to me that
your use case is not a good fit for the problem space that it is
targeted at. It's probably easier for you to manage the image src
urls in an array and have the Paginator's changeRequest listener
update a series of existing img tags in place with new src values
pulled from that array based on the Paginator's recordOffset.
The primary benefit to you of using ImageLoader would likely be
attaching to earlier events, such as mouseover, to load the images
ahead of the potential click. If your Paginator's template includes
PageLinks, then a mouseover hook could be a bad solution as the
trigger area (the page number links) are small and in close proximity
to one another, meaning anything less than precision mouse movement
will result in extraneous http requests for images on pages the user
is not aiming for.
That said, I don't really have a good idea of the details of your
implementation. When in doubt, just try it. Hopefully you'll find an
effective solution for your site's needs.
> But if i want to show images when my page link changes on pagination...
> that means on clicking page link 1 can i show images using image loader
> because image loader usually trigger on html element id...so i
> the way to map imageloder with pagination
> so is there a possibility to use image loader with pagination....
> Thanking You,