A lot of what has been discussed in this thread, will be possible if the architecture of views are upgraded, in that views databases become accessible to users as Views Entities, just like other databases, this would be a leap in the power of Fibery.
(As a workaround I’m now trying to mimick that with a ‘View’ database and a URL field, which sucks and is not scalable)
The good thing is that Fibery Views are not merely configuration like in data management systems with dynamic configuration views, but in Fibery they are already entities with Id, so the step to upgrade them is pretty straigtforward.
If List/Table/Board Views become first class citizens in Fibery, we can do all kinds of things them, including:
the feature that is worked on now, being Entity Views as announced last week:
- July 4, 2024 / New shapes in Whiteboard view, hide when empty per field setting in views - #11 by Zauri
- July 4, 2024 / New shapes in Whiteboard view, hide when empty per field setting in views - #18 by Zauri
…which basically means that the same List View could have multiple List Entity Views that the user can create and configure.