[WIP] An autocompletion plugin

[wouterj]

See sonata-project/SonataDoctrinePhpcrAdminBundle#340 for the story behind this PR.

Fixes #76

[dbu]

cool! what is missing here?

could we support autocomplete on document titles in the same plugin? and is there a way we could limit the editable area to a sub path? although, for the scenario of having 10-100 documents to pick from, one can also use the EntityChoice dropdown, maybe with something like the chosen plugin.

[wouterj]

what is missing here?

Some tests and some local testing.

[wouterj]

Hmmm, lots of things went wrong there...

[dbu]

the good thing with git is that a branch can be restored ;-)

did you want to trigger a travis restart? for that i could also try to give you permissions to do so on travis, if you not already have them. (its the circle icon on the top right of the travis pages. there is a global one for the whole build, and one on each detail page of a matrix entry)

[wouterj]

did you want to trigger a travis restart? for that i could also try to give you permissions to do so on travis, if you not already have them. (its the circle icon on the top right of the travis pages. there is a global one for the whole build, and one on each detail page of a matrix entry)

I already can restart builds. I don't know what happend exactly...

[wouterj]

could we support autocomplete on document titles in the same plugin?

This plugin is using the HTML 5 datalist element. Browser inconsistently support it (Chrome matches both label and value, FireFox matches only label, etc). However, I just discovered datalist is not supported by IE 9 and Safari, so I have to rewrite it (and may use a jQuery autocomplete plugin for that part).

[dbu]

even the latest safari? i would have no problem saying that this only works with IE10+ for windows users. is safari even still relevant? or is everybody on mac using chrome anyways?

[ElectricMaxxx]

can you rebase please?

[wouterj]

Skipped this PR for 2.0. It's not required and needs lots of love.