Hi,
I am still undecided if I should use display suite or panels to configure my custom pages with EVA.

Most important thing I noticed:
EVA displays seem to be not available as fields with panels!!
Damn.
But there are other considerations, see below.

------------------

Use case:
With organic groups, for each group page, I want to have
node/%: main group page, with a list of latest comments, grid of member thumbnails, etc. All of these should be EVA views displays.
node/%/members: List of group members.
node/%/forum: List of posts in group forum.
node/%/wiki: Wiki page.

All these as local tasks (tabs).

Some of this could be implemented with views pages with arguments, but I strictly don't want that. Performance considerations, and lack of flexibility to put other stuff on these pages.

Display suite:
All of the above would be custom router paths with custom build modes for the node display. The views would be EVA displays, positioned in the respective build mode as ds / nd fields.
+ EVA views displays appear as fields to be positioned.
+ Allows different layouts.
+ I have a good level of experience with ds from D6.
- Need custom module stuff (hook_menu, hook_menu_alter) to create the custom router paths, and deal with access stuff, and having different build modes and tab labels per node type. I have a nice home-grown API for this in store for D6, but I don't know yet if it is worth to port this to D7.
- A few other fields, that are available in Panels, are not available in Display suite, afaik.
- Somehow not as flexible about how things are positioned.

Panels:
With page manager, I would create router paths with variants and conditions (already tried that).
+ Powerful tools to set up those router paths.
+ Plenty of fields / displayable stuff available.
- EVA displays are NOT available as fields! Duh!
- I'm a panels noob.

--------

Maybe you could say something useful about this, anything I don't know yet :)
Thanks!

Comments

donquixote’s picture

donquixote commented

Hm, I found that Panels wants views displays configured as "Views content panes".
og_views already has some displays that are configured this way.
So then EVA would be out of the game, if I use Panels.

Unfortunately, those views_content displays are not available as ds fields..
#1379560: Make views content panes available as display suite fields?

---

Now, you can have a look if anything in this issue is worth reading, or if you have any thought I might be interested in.
Otherwise, feel free to close :)

mkadin’s picture

mkadin commented
Status: Active » Closed (fixed)

I'm closing this in the interests of cleaning up the issue queue. See the issue in #1 for more details about DS and embedding views.