Just tried, you can embed only if they are not mirrored across the smart folder.
I mean creating an embedded view inside the rich text of an entity. This makes into a context view with context filters. I think under the hood it is just the exact same as a non-mirrored context view.
I note that the cons for #3 included that they can’t be mirrored, but the cons for #4 includes that they are always mirrored. Doesn’t that mean, at least for this problem (of mirroring) there is a solution with one or the other? - if you want a mirrored view, use a relation view; if you don’t want a mirrored view, create a rich-text embedded view.
Yes, but each comes with their cons as well. So an ideal would be consolidate it into something that has the pros from both. Maybe show the context views inside the entity, then a toggle to mirror into all entities or not.
Or allow each entity to have a different layout. Then technically its still there, but each entity is flexible to show or hide what it needs.
It feels like the solution is what is discussed here, no?
Yes, but only if it allows for ad hoc creation of views inside the entity (that looks and behaves like a relation view container). It needs to be really thought through.
This solves one aspect of views, the second one of having context built into views is another one. Similar to this: Convert pinned filters to tabs
Or if it made multiple of the same view with the context applied (like the way “Multiple Pie Charts” work in reporting.)
This way you can see the same view across the context you need. Sometimes you need Entity → Data
and sometimes you need
Data Per Entity.
Grouping helps with this, but doesn’t work great for things calendar and general grouping at the moment isn’t great.