Libraries tagged by php to html
bugo/fa-php-helper
33 Downloads
Helper classes to get FontAwesome icons html code
ibraheem-ghazi/html-stripper
22 Downloads
php parser for html tags and html inline styles , to allow or prevent some css styles with any value or specific value
bozworks/bouncer.php
5 Downloads
🖐️ Bouncer is a library that allows you to flexible, quickly and easy to use filter and validate HTML forms.
mykemeynell/html-currency-entities
7 Downloads
Object of HTML currency entities mapped to their corresponding Alpha-3 (ISO 4217) representation
optipic-io/optipic-cdn-php
3 Downloads
OptiPic CDN library to convert image urls contains in html/text data
jeffmilanes/php-html-dom-parser
3 Downloads
Composer adaptation for: A simple PHP HTML DOM parser written in PHP5+, supports invalid HTML, and provides a very easy way to find, extract and modify the HTML elements of the dom. jquery like syntax allow sophisticated finding methods for locating the elements you care about.
php-extended/php-html-parser-interface
15596 Downloads
Interfaces to implement parsing of bbcode text into html tree structure.
php-extended/php-css-selector-parser-interface
15592 Downloads
A library to parse css selectors to use in css sheet parsing or html attribute findings
wan3574489/php-dom-wrapper
20 Downloads
Simple DOM wrapper to select nodes using either CSS or XPath expressions and manipulate results quickly and easily.
vladshut/php-dom-wrapper
21 Downloads
Simple DOM wrapper to select nodes using either CSS or XPath expressions and manipulate results quickly and easily.
substacks/php-barcode-generator
16 Downloads
An easy to use, non-bloated, barcode generator in PHP. Creates SVG, PNG, JPG and HTML images from the most used 1D barcode standards.
ss-mokumoku/php-barcode-generator
6 Downloads
An easy to use, non-bloated, barcode generator in PHP. Creates SVG, PNG, JPG and HTML images from the most used 1D barcode standards.
p-ba/php-barcode-generator
288 Downloads
An easy to use, non-bloated, barcode generator in PHP. Creates SVG, PNG, JPG and HTML images from the most used 1D barcode standards.
ne0bot/php-dom-wrapper
14 Downloads
Simple DOM wrapper to select nodes using either CSS or XPath expressions and manipulate results quickly and easily.
matthewbaggett/docker-api-php-client
6 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```