php-qrcode/examples

php-qrcode examples

Simple examples that demonstrate the different output types

• image: Raster images via the GD extension
• ImageMagick: Raster Images via ImageMagick
• SVG: Scalable Vector Graphics
• HTML: HTML markup
• FPDF: PDF output via FPDF
• EPS: Encapsulated PostScript
• String: String output
• Multi mode: a demostration of multi mode usage
• Reflectance: demonstrates reflectance reversal
• QRCode reader: a simple reader example

Advanced output examples

• Custom output: a simple example that demonstrates the usage of custom output classes
• GD Image with logo: a logo on top of the QR Code
• GD image with text: description text under the QR Code (#35)
• GD Image with rounded modules: similar to the SVG "melted" modules example (#215)
• ImageMagick with logo: a logo on top of the QR Code
• ImageMagick with image as background: an image as full size background of the QR Code
• SVG with logo: an SVG QR Code with embedded logo (that is also SVG)
• SVG with "melted" modules: an effect where the matrix appears to be like melted wax (#127)
• SVG with randomly colored modules: a visual effect using multiple colors for the matrix modules (#136)
• SVG with a round shape and randomly filled quiet zone: example similar to the QR Codes of a certain vendor (#137)
• SVG with logo, custom module shapes and custom finder patterns: module- and finder pattern customization (#150)

Other examples

• Authenticator: create a QR Code that displays an URI for a mobile authenticator (featuring chillerlan/php-authenticator)
• Interactive output: interactive demo (via index.html)
• Custom module shapes: SVG paths to customize the module shapes (#150)
• ImageMagick SVG to raster conversion: uses ImageMagick to convert SVG output to a raster image, e.g. PNG (#216)
• HTML canvas SVG to PNG conversion: converts an SVG element or a data URI fom and image element to a PNG image via the HTML canvas element, includes a javascript class which handles the conversion.

Please note that the examples are self-contained, meaning that all custom classes are defined in an example file, so they don't necessarily respect the PSR-4 one file = one class principle.