Which part are you having problems understanding? Paging? Scrolling? Table?
I have not used this component, but paging is simple.
As you know, MVC separates the data from the presentation.
Imagine you got 100 records and your page size is 10 (max 10 records will be displayed at one time)
To navigate between the records, you need to provide the user with some controls (typically the previous/next button)
In pseudo code
1) Keep a counter for the page. defaults to 0
2) Have a RPC method which will accept this counter and return the appropriate records. e.g. If the counter is 1 you return records from 10-20
3) When the call returns the data, load them in your model and update your UI with this new set of data.