Form API is perhaps the most loved and talked about API shipped with Drupal core. As such, it may very well be the most hated API too.
The API in its current form has been around for a while; we've been traversing hash-flagged array since time immemorial and AHAH has never really lived up to its name.
This session will demonstrate some of FAPI's shortcomings and those of the renderable array system on which it is built. Most of them can be changed without changing the architecture, but what if we do change the fundamentals of how forms are processed? Will that make us happier and Drupal better?
This session has no intention of showing the path to a better form API, but rather to demonstrate why we should think of updating the API, and shows ideas of how we might do that. A rough example module that incorporates some ideas can be found at http://github.com/bartfeenstra/fapitng.
Drupal core developers who want a cleaner and more flexible Form API.
Comments
Core conversations?
This might be good in Core Conversations if it doesn't get in as a session.
I now realise I should
I now realise I should rephrase the intended audience: this session is for all developers who use Form API, but specifically for those who want to work at getting a better one in core.
This means you're most welcome as a developer of contributed modules, because those modules probably use more advanced FAPI black magic than Drupal core does.
Good Core Conversations Topic
I feel this would be best served as a Core Conversations topic.