Here is an idea: you could use YAML to generate the base form classes in the same way that Doctrine generates model classes. Then you could easily derive a custom class from this base class to fiddle with at run-time.

Allow for proper type definition of form elements (including types, defaults, validation), include field level security attributes and with clever use of the translation engine allow better default error messages & tooltips. Field grouping would be possible follows the same pattern we have in the generator.yml.

The use of the translation engine would allow text from resource files to be used in this scenario. The main changes needed to translation would be to implement a form of inherited lookup – best illustrated with an example:

all:
name:
label: Name
tooltip: Enter the name
validationError: You need to enter the name
…
registration:
name:
label: Login Name
tooltip: Enter the login name you’d like to use
validationError:
default: You need to register with a valid name
validationFail: That name already exists, try with another.

In the context of registration – the specific details would be used for the field – otherwise the site default would be used.

Generally what you’ve outlined is interesting – but while it’s simpler syntax – it’s much the same as we have already. I’d like to see something more flexible generally – where form fields are more component based and where the project structure defines more the defaults.

Something like:
lib\form\fields contains:
input.class.php [for the generic input field]
apps\thisApp\lib\form\fields:
input.class.php [overriding it for this application]
apps\thisApp\modules\thisMoule\form\fields:
input.class.php [overriding it for this module]

Symfony forms are awesome but I do feel an improved interface would simplify real-world projects, where (maybe due to my own inadequacies) I often spend most time tweaking with and/or fixing forms.

I’d definitely use this and encourage you to continue!

Well anyway great to see some community action around sfForm:-)