You're creating a new flexinode to replace CCK? That really makes me nervous - going from flexinode to CCK the first time was a pain in the ass because there was no easy upgrade path. Why not just fix CCK instead of pushing people back and forth? Or am I misinterpreting you? Right now I'm pretty happy with CCK and the modules that work with it and I don't relish the idea of ditching that. Bèr Kessels wrote:
Op donderdag 31 mei 2007, schreef Bèr Kessels:
Part of this is already implemented in my probably-never-to-be-released-because-too-litle-quality-time flexinode2, the superceder of CCK. Baked right into the core of it, in fact.
wrong quote. This was not reply to CRUD, but to the idea of letting modules define content types (and fields).
The crud is somthing that is already in flexinode1, so it will be in 2 too.
Bèr
-- Sean Robertson Web Developer NGP Software, Inc. seanr@ngpsoftware.com (202) 686-9330 http://www.ngpsoftware.com