HomePHP Page 6 - Previous or Next? Paginating Records with PHP - Part 2
Pager class implementation - PHP
In the first article in this series, we learned how to do simple pagination of records taken from a text file. In this article, we will look at pagination for a larger group of records, using an Objected Oriented rather than a procedural approach to creating the application.
Having listed the complete class code, we can show our first example, which is presented in the following way:
That's it. With four lines of code, we're displaying records from the text file "data.dat" and displaying the corresponding paging links, using a default value of five records per page.
If that's not good enough for you, here's another example, showing records from a text file "data2.dat", in sets of 10 records at a time:
Our newly developed class is very flexible and portable, and easy to implement in different situations, simply by changing the parameters passed to it. As usual, feel free to play with the code and tweak it to fit your particular needs. Certainly, the possibilities are numerous.
In this second part, we've developed in a step-by-step process, a PHP class to paginate records in websites. Noticeably, we've branched out to an OOP approach to illustrate the great advantages that classes offer to PHP programmers. However, before you start clamoring for more complex paginating solutions, we're not done yet.
In its current incarnation, the class lacks many desirable features that should be present in real-world applications. The first clear issue is that we're working with text files as a data source. If we're going to work with medium to large sites, we'll quickly encounter a relational database system. The second problem is the basic mechanism presented to apply some kind of visual format to the records. Thus, all of these relevant topics should be properly addressed without modifying the inner structure of the class, while maintaining the basics of the original code.
In the third part of this series, we'll apply some interesting improvements to the class, making it possible to work directly with MySQL, offering a flexible mechanism for defining the records' visual presentation. What more can we ask for? In the meantime, have some fun playing with the class. See you soon!