QrcodeToolkit v1.0.0 Documentation
Composer

Turn the knobs.
Take the code.

Every option the package takes, wired to a live symbol and to the PHP that produces it. The encoder and the SVG writer here are ports of the ones in the package, checked against them byte for byte — what you see is what Qr::make() writes on your server.

Content

The string below is encoded exactly as it stands.

Shapes
1.00

How much of its cell a module fills. Below 0.65 the report turns cautious; below 0.45 it calls the code risky.

leaf and pointy turn with the finder they belong to, so each eye aims at its own corner. module draws the eye out of the module shape.

Colour

Off, the three eyes take one ring colour and one pupil colour. On, each of the three is addressed separately.

Logo

Read in your browser and never uploaded anywhere. On the server the package takes a local path or a base64 data URI, runs twelve checks over it, and raises the error correction to H because the logo erases modules.

0.20
0
Caption and frame
16
Canvas
300

Pixels across, the quiet zone and the frame included.

4

In modules. Four is what the specification asks for.

40 mm

 

What this is not. PNG, PDF and EPS come out of the same geometry on the server, but only SVG can be drawn here, so the preview is the SVG one. The logo you pick is read in your browser and inlined; the package would run it through its twelve checks first and refuse a remote URL, a stream wrapper, a MIME mismatch or a decompression bomb. Everything else — the matrix, the shapes, the colours, the report — is the package's own code, ported and checked against it.