Hi there Jen - thanks for circulating your work on the "batched pager" configuration for our "old-style" pager component :) Sadly, pressure of work has meant that the "new-style pager" is still half-baked in a branch somewhere so I am seeing your patch at https://source.fluidproject.org/svn/incubator/batched-pager/trunk/js/batched-pager.js as a valuable starting point for a bit of work I am currently doing with integrating the pager into another project which requires server-side paging. The patch looks ingenious and shows a good appreciation of the planned architecture (however half-baked :P) of the "old pager" - one question does occur to me which is that unless I am missing something the patch doesn't seem to deal with the issue of asynchrony. The configuration options "dataFunction" and "dataLengthFunction" appear to be invoked in the patch using a synchronous style, and I guess if they issue any I/O must also do it synchronously? What does the UI show in this case, is it just blocking on the click event that is at the base of the current stack? Or could you find a way to implement these configuration functions in your integration that operated asynchronously? If you could show me a little more of how you used this patch in practice without revealing any code you're not meant to, I'd appreciate it -
Cheers,
Antranig.
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to