I think it makes a lot of sense. With Field/Field UI in core for D7 + CCK for D6, we can have better management of the UI, output, and access. In D7 we even can use fields with any fieldable entity (nodes, taxonomy terms, users, etc).

Comments

Dave Reid’s picture

Status: Active » Closed (won't fix)

I'm really leaning towards the Field UI and API being unready for something this big and I'm not eager to code it. For a 7.x-1.x branch I'm going to continue with custom storage and UI since it's much easier to control your own code and UI. Possibly for 7.x-2.x we can convert to using fields after the Field API matures by various uses in contrib modules.