[eluser]tonanbarbarian[/eluser]
with the same code you have given i do not question whether some of the pagination code should be moved to the model.
I feel it is exactly where it should be
what i question is whether the table generation code should be moved to the view.
because the table generation code is taking data and preparing it to be presented, it really should be in the view.
now some people say that my web designers who work with my views would not understand that code and would not be able to update it. That is fine and there are ways around it, but views are used to present data.
Personally I do not use the table class for this very reason. If I use the PHP heavy code of the table class to generate a table 2 things will happen
1. Any competent web designer who is working on my views will complain that I have used a table when I should have used divs
2. The same competent web designer will want to strip the php code out and use html in its place to create the table so that it is easier for them to control the styling by the addition of ids, classes and using sub elements inside the table cells such as divs, spans and the like.
Just my opinions and I am sure others will disagree