I have been playing with Editview, views and viewfields.
I've found some little "flaws" in the plan :-(... But I think we can make something really good :-)
I think the use case is something like this:
I have a content type, which, within it, wants to refer to a list of objects. The list of objects are themselves more complex than a single entry (otherwise, multi-value would do the trick!)
So, we need two content types, the parent content type, and a child content type.
So, a nice solution to this is to have a "viewfield" in the CCK of the parent content type that enables the list of children nodes to be displayed. We create a field, using the viewfield field type and give it a "default" of the view which shows the "children". This view is simple enough to set up so long as the child node has a node-reference that is set to the parent type. (We can of course control this viewfield, just as we do any other field we create, placing it anywhere in the output, etc)
But, when the parent type is edited, rather than seeing the view as an editable list of child-nodes (which would be ideal), we only see the name of the view (which is not something we should want to change)
DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.
