Use case would be to have multiple views to select from similar to how this module does it: https://drupal.org/project/viewreference.
The feature your module offers that the other doesn't is the embedded exposed filters/sorting functionality. Your module is powerful but it would currently require creating multiple view fields vs. manipulating one.
Thanks

Comments

webmorozov’s picture

webmorozov commented

Hi apmsooner,

Thanks for your Feature request!

I don't think that manipulating one field with different views better than multiple view fields (1 field - 1 view). Please, don't think that I just don't want to fix it.
We should use more common practice. Why Drupal Core not provide possibilities to create one multiple field with different select elements:
First item - Color (select):

  • -red
  • -white
  • -black

Second item - Opacity (select):

  • -0
  • -50
  • -100

We will have the disorder in the system. In this case We can not use the field in another entity.

As You may see viewreference does not store settings about views in field instance. Viewreference save two params views&argument in each node and it's different way.

Let's discuss it and try to find better solution...
How much Views you should attach to node?

apmsooner’s picture

apmsooner commented

Thank you for your reply. So.... my other feature request > https://drupal.org/node/2217203

Is that one doable? If there was a way to expose the fields to output, then I could feasibly reuse one view as you describe. I wouldn't particularly need the ability to rearrange the fields as the dynamic fields module does, just control their output. Ctools does the same thing thing i'm asking with views displays of type "content pane" where the fields can be ticked on/off through the panels interface.

Yuri’s picture

Yuri commented

I agree with this feature request of this post. We need to take viewreferece as example and expand on that to include the features of thismodule. At this point this module is very limited because only a single view per field can be set for all nodes of the node type.

webmorozov’s picture

webmorozov commented

I see that more than one person need that feature. In that case we can implement it but it should be agile...

You propose select view/display in node like in viewreferece? In that case we should render exposed forms by AJAX. I used very complex exposed forms with more than 20 fields that use JS and sometimes AJAX (date, autocomplete, etc.) Second solution configure multiple view/display on field instance. For me better select view/display in field settings.

Or implement switcher: if you select default view/display - render it for each field item (multiple), if not you can select it in node. Sometimes users should have possibilities to select only some views or not select it (he can broke site, or render some system view...).

What do you think?

Yuri’s picture

Yuri commented

Yes, the switcher option sounds very good!