Libraries tagged by Paginated

php artisan command to generate fully working crud with grid paginated server side only by having database tables

Go to Download

Pagination as TYPO3 DataProcessor

Go to Download

Go to Download

This is a filament-theme based package that provides a panel with a functional pagination system

Go to Download

Add Pagination to your resource collections

Go to Download

Paginated list extension

Go to Download

Symfony Front Twig Extension Bundle

Go to Download

php artisan command to generate fully working crud with grid paginated server side only by having database tables

Go to Download

php artisan command to generate fully working crud with grid paginated server side only by having database tables - forked from kEpEx/laravel-crud-generator

Go to Download

Symfony third party bundle allow to generate paginated, sortable and filterable grids and lists, based on given data provider

Go to Download

Paginated comment list for Textpattern CMS

Go to Download

Help you to render array of data as a paginated table

Go to Download

This library wraps the NoshPOS API and allows you to retrieve paginated basic data from NoshPOS.

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download

Support swipe touch gestures to navigate in paginated lists and on Tidypics image pages.

Go to Download