Don't work without composer autoload about fpdi

[JanSlabon]

@sovetski the information about "no fixed" dependencies is in the README.txt just some lines above your quoted text:

FPDI/README.md

Lines 20 to 22 in bda0af0

	Because FPDI can be used with FPDF, TCPDF or tFPDF we haven't added a fixed dependency in the main
	composer.json file. You need to add the dependency to the PDF generation library of your choice
	yourself.

So at the end it depends on the library you need how to install it - that's why Max send you a link to an example of FPDF.
I'm more wondering why you have a folder structure simliar to composer (the vendor folder) but require the package manually?

[MaximilianKresse]

You have to require FPDF too:

require_once('/your/path/to/fpdf/src/fpdf.php');

[sovetski]

You have to require FPDF too:

require_once('/your/path/to/fpdf/src/fpdf.php');

Is it something that we have in the documentation? If not, I can do a quick PR to precise that we have to do it

[MaximilianKresse]

This is part of the FPDF documentation and not of FPDI. It can be found in this example: http://www.fpdf.org/en/tutorial/tuto1.htm

[sovetski]

Thank you @JanSlabon for the clarification.

why you have a folder structure simliar to composer (the vendor folder) but require the package manually?

It was for a WordPress website, it is a real problem on this kind of CMS to load composer autoload, because we can get a conflict with package versions with other plugins which loads also their own composer. The solution is to prefix namespaces of dependencies or just load what we really need manually (a dirty solution but sometimes we have not choice)