On Sunday 07 May 2006 16:23, Earl Miles wrote:
Unless there's going to be some way to resync node field changes from a beta site to live site as easily as uploading a new version of a module, let's not get rid of "classic" nodes completely.
As I've been doing more of my work for actual, professional sites, I've realized that database dependency on data can be damaging for a site of that kind. It made me extremely glad that I did Views the way I did; as I understand it, CCK will follow the same model, where modules can specify their fields and default node types to support those fields, so that ideally none of that will NEED to be in the database. Not entirely sure how far JonBob's been planning to go with that model, of course.
I don't know either, but it would be a really good idea. I rather like the way Views does that. It takes a while to wrap your head around, but once you do, it makes a lot of sense. -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson