Op dinsdag 6 februari 2007 07:42, schreef Larry Garfield:
(For me it's value-add fields rather than value-add form primitives, which I imagine would involve hook_elements and hook_widget merging or becoming more closely linked or something, but that's just my speculation based on banging my head against a CCK field module for the past few days. <g>)
This raises another issue, simplicity. I think we all somehow agree that the current field code is far too complex (and overengineerd?) to be copy-pasted into core. Personally I think flexinode field handling is a better model for core. read: model. Model. IMO the choices, when going for an existing solution, is either: CCK-stripped, flexinode-a-lot-cleaner, or profile-fields-made-modular. Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl