Name already in use

…d been changed to simpler and easier to remember `Widget::Error` :).

…zerangue for asking about validating for numeric values :).

…r (TEXT columns cannot use default value). This fixes #5 reported by @danielepennati (thanks!).

…used yet. Added list of parameters available for use in Conditionalizer textarea. Fixed code that extracts parameters from data-sources and moved it into Conditionalizer library.

…sion input fields are now textareas. Shows nice error box after conditions were not met for saving an entry.

Conflicts:
	extension.driver.php

…-source edit pages, so Conditionalizer fields are not required anymore (and data-source can be omitted earlier in the process) and conditions can be applied to any type of data-source, e.g., Dynamic XML :).

…Changed name from `filterfield` to `conditionalizer`.

Add "IF NOT EXISTS" to install() function. Thanks kirkstrobeck!

…filter field does not show up on publish pages).

…of one). Fixed example in code comment.

…y with it :).

… :).

…urce and Section edit pages and errors will be shown if syntax is invalid. From now on it is possible to filter Data Source by both expression and field value ('yes' or 'no').

…ion and event.section.php (part of Symphony). Field now stores 'yes' or 'no' value (depends on return from publish filtering expresssion).

…ld} instead. So, if POST field name is "fields[published]" one can use "{published}" to get POSTed value.

…ues/closed#issue/1 by http://github.com/bzerangue. Thanks\!