PluginConfigParser - Make examples/ and includes/ not mandatory

[akrohn]

Current plugin system is control oriented. But I'm currently working on a css plugin that installs no control. It crashed when I installed with only using:

$components = array();

// Taking the YAML contents
$components[] = new QPluginCssFile("yaml");
$components[] = new QPluginCssFile("images");
$components[] = new QPluginCssFile("css");

$objPlugin->addComponents($components);
$objPlugin->install();

Reason: files in /includes and examples/ were mandatory. This patch corrects that and checks if it exists, before parsing it.

[akrohn]

examples/ and includes/ not mandatory anymore

[VexedPanda]

Hmm, wouldn't it be easier for us to just initialize those two arrays instead?

[alex94040]

In my mind, checking for null versus initializing the array are both good solutions. I'd be fine shipping the patch as-is.

[alex94040]

(In [688]) Fixes #397: PluginConfigParser? - Make examples/ and includes/ not mandatory. Code by akrohn, reviewed by alex94040.

[akrohn]

Checked the changeset and it includes three new files that seem to belong to the autocomplete plugin. Are they correct?

[alex94040]

Yeah I screwed up that changelist. I fixed it in a later changelist.