Posted by adrian on May 2, 2006 at 11:57am
One of the things I came away with from the Vancouver DrupalCon, is that we already have our relationship API, in the form of CCK and what I want to do with forms 2.0.
Firstly, in forms 2.0, there will be 2 discrete steps.
Step 1: Defining Fields for form. (or node type, or whatever)
Step 2: Placing these fields within their final form structure (add tables, fieldsets etc).
Now I am basing this functionality off of the cck field definitions, so that all the validations and field type
code will be built using cck, and one of these field types is 'nodereference'
CCK already handles all the 'has, can have and single / multiple' bits of the relationship api, and with
some custom views, we are done. All that remains is making finding things easy.
Comments
good stuff
i like this direction a lot. It is one of the more sane ways of getting us to relationship API. cck got some nice themeing features recently so Step 2 may be possible today for certain cases.
And views fixes some of the
And views fixes some of the 'finding things' part of the equation. I have been working on reverse links for nodereference and userreference and the slickest solutions will involve using views to handle them when there are many-to-many relationships.