What is the difference between EVA and http://drupal.org/project/viewfield ?

  • with viewfield you can attach any view to any content (where fields are possible)
  • you can set up a viewfield to contain only default values (the view to use, the arguments (usually passed as tokens))
  • you can add as many viewfields to your field list as you want
  • viewfield is actively maintained

So, what is EVA for that viewfield does not provide?

My questions sounds provocative. But if I find modules that nearly do the same, I really get angry. More modules provide more errors, less synergy, more issues, less transparency and more confusion. I didn't install EVA, I only read the docs and the issue queues.

Did I miss something?

Comments

eaton’s picture

eaton commented
Status: Active » Closed (works as designed)

My questions sounds provocative. But if I find modules that nearly do the same, I really get angry. More modules provide more errors, less synergy, more issues, less transparency and more confusion. I didn't install EVA, I only read the docs and the issue queues.

I live to provoke anger. ;-)

Viewfield allows the author of a piece of content to choose a particular view and supply a manually-entered list of arguments. EVA Allows site builders to build views that will be displayed as part of a given piece of content, but are not controlled by users and store no information on the nodes themselves. If you'd like to do something like, say, always list related articles underneath a node or place a grid of images on a "gallery" node, EVA allows it to be a baked-in part of how a given type of content displays, with no authorial intervention necessary.

Think of EVA as a cleaner way of attaching views to particular content types than building arg-driven blocks and placing them in the 'content' region. That's much closer to its common use case than the ViewField example.

pepe roni’s picture

pepe roni commented

But if you supply default values to the views and args input fields on the viewsfield definition form and check "force default", you as the site builder define the view and arguments the node will use in this field, and not the author of the node. Say, you set view_myview (Display:Page) as the default view, [node:id] as the default argument to the view and check "force default", you have EVA without EVA. And that means: EVA can easily be replaced by viewfield without any additional effort!

danny1997’s picture

danny1997 commented

I just tested the 2 modules. For the case of building a photo gallery, I prefer EVA than viewsfield since it's easier and more simple to use.

delacosta456’s picture

delacosta456 commented
Issue summary: View changes
Related issues: +#3071157: Comparison of this module with Viewfield