On Aug 6, 2007, at 4:51 AM, Karoly Negyesi wrote:
- Beyond FAPI and the Schema API: next steps (*) - A plan to get some more CCK/Views into core (*)
I do not think we (Eaton+me) will have more ideas for FAPI, all the common grunts were solved w/ FAPI3, not until D6 is out, modules are ported and projects are ongoing will the flaws come to light. Let's get back to FAPI at the spring Drupalcon (Toronto?).
Yep, I'm with Karoly on this one. There are some cleanup bits and things we didn't necessarily have time for in FAPI3 (making form_set_values() and form_set_error() simpler, etc) but those are tweaks and polishing moves rather than architectural shifts. It will take time, time for porting and exploration and envelope- pushing, to make it clear what changes the next generation will need. SchemaAPI and how it ties in to both CCK and Views is definitely an important issue. There's also the possibility of programmatically generating basic CRUD screens from SchemaAPI definitions; now that we can store table and column metadata, and are beginning to explore relationships, Ruby-esque auto-generation of CRUD scaffolding is within the realm of possibility. --Jeff