At work, in some of the larger custom .NET and PHP apps we basically have a single "view", in the form of a data grid that is indeed paginated.
As in large data sets pagination isn't practical, yet endless rows aren't an option either, the data grid itself allows for all sorting combinations just by clicking on their headers. This removes the need for seperate views.
Still, this only sorts results, and does not limit their amount. To help with that, there's a filter panel above the grid, where users can set one or more filters, typically custom designed.
Finally, and optional, there may be a free text search. Often we also make a second "my view" for records only applying to the current user.
All of these parts are needed to make it usable, and I'd argue it still isn't nearly as usable as a desktop-style data browsing application.
At work, in some of the larger custom .NET and PHP apps we basically have a single "view", in the form of a data grid that is indeed paginated.
As in large data sets pagination isn't practical, yet endless rows aren't an option either, the data grid itself allows for all sorting combinations just by clicking on their headers. This removes the need for seperate views.
Still, this only sorts results, and does not limit their amount. To help with that, there's a filter panel above the grid, where users can set one or more filters, typically custom designed.
Finally, and optional, there may be a free text search. Often we also make a second "my view" for records only applying to the current user.
All of these parts are needed to make it usable, and I'd argue it still isn't nearly as usable as a desktop-style data browsing application.