To reduce visual clutter, I suggest that empty fields can be hidden from the entity display. This can be implemented in different ways, for example as an button that allows empty fields (which have been enabled, but are empty) to become visible to edit.
I am aware of the ability to show hide the right sidebar of the fields, but I mean to automatically hide the fields present in the entity display itself (vertically). Currently when empty you see:
I like to keep a lot of fields enabled but just not visually taking up so much space and attention when empty.
I would find it very helpful to have a âShow All Fieldsâ toggle in the fields selectors , which would TEMPORARILY (and only for the current user) show all fields⌠and which could simply be un-toggled to return to the previous selection of fields.
I see this (âtoggle to temporarily show all fields in entity viewâ) as more of a Creator level function, useful to temporarily âsee whatâs thereâ in order to better understand/remember the DB structure.
The primary need here is the visual clutter of how the single empty field currently looks (as shown in the main topic here) and if there are several field this quickly fills the whole browser window. This actually is scaring away people I showed Fibery. See below the actual fields that I use:
Ddefault hiding of empty fields, and a button âShow all empty fieldsâ.
Hiding everything of the field except the title, and making the rest appear on mouse hover.
Hiding everything of the field except the title, make stacking more compact, and make the title half-transparent.
Group the empty fields together at the bottom (yes get them out of the predefined place in the list) in a minimalistic style. When filling an empty field there, it will show up among the populated fields in its predefined place in the list.
This topic relates to the UX improvement of all fields, also the filled ones; making everything more compact and minimalistic.
So as an example, I would be happy with the following display of empty fields (option 3)
I know this has also been suggested elsewhere, but one of the other ways of dealing with this is to make field visibility to be also formula driven. This allows for a more sophisticated approach to what to show and when.
One of the things I find amazing about QGIS (open source GIS application) is that early on a decision was made that almost all inputs and options had the ability to be set using the expressions/formulas. This allows simple input for normal cases but ability to expand functionality that the programmers could not predict. Iâm hoping that fineryâs investments in building formulas and condition logic (for sorting and filtering) could be leveraged across the entire system wherever user input is needed.
agree with that, zen mode like this, using a lot in reading document. Itâd be nice to have a visual focus on the main things rather than distract by all other
Pinned fields can be hidden when empty, but the fields in the main entity view section cannot.
I donât want to see empty fields!
The new Multiple Entity Views (tabs) feature does NOT solve this!
A lot of my databases have many relations, and I try to workaround the clutter by spreading them over the new Entity View tabs. This reduces the clutter, but does not hide empty fields. Moreover, checking all tabs one by one is not practical!
Idea: A field that automatically includes all relations to the current entity
In the past I tried a workaround to create a field that includes ALL AND EVERY database the entity relates to, but that is a huge effort to created and maintain, so I dropped that approach.
Iâm interested if the Fibery team has plan to handle this?
Fully agree with this. The functionality already exists in compact relation views, I would think it would simple to bring it to the main section.
Adding that option to fields across the entire entity view could be the first step to conditional visibility (bc formulas more complexity) that would already reduce mental load for fields that are not relevant if empty.
Example:
As role x, i will never be assigned as owner of a client. Hence, on my user page, that value will always be zero. It is not relevant, is always empty, and should therefore be hidden.
Another example: people with no permissions to a relation should not see the multi-relation. But I tested this with compact relation, and it doesnât seem to work because of this: Do not show number of relations when people do not have access
I suspect that under the hood the relation view is not really empty due to seeing this:
So this would need some fixing before it would work for permissioning I presume.
Edit:
TIL that when you hide things on the top section or right section it adds a dropdown with â1 Moreâ to see the hidden fields. Where Pinned fields hidden when empty do not. I personally do not like that behaviour as it adds even more clutter. One more thing a user can do. Maybe a toggle in setup? Show dropdown for âhidden when emptyâ fields?
amazing!
