The last update was packed, this one is more reasonable
Wide Rich-Text Field Content
In the previous update, we limited the width of the Entity View for a better reading experience on wide screens. Now we acknowledge the ârichâ part of the term ârich textâ and allow to widen some elements beyond the main layout:
images and videos;
embedded Views;
URL embeds;
text tables;
relation Views.
The table of contents also now uses the horizontal space wiser. Altogether, these changes should make better use of your 32" display.
Minor Improvements
Board View rows and columns feature icons, not just names of selects and Entities:
Timeline View weekends take into consideration user location. For example, if you are located in Asia/Jerusalem, you will see Friday and Saturday as the weekend.
Experiments
Mirrored context Folders are not that rough around the edges and are looking to graduate from experimental in the next update.
Pinned Fields on Entity View are not expandable anymore: the experiment has proven useful (thanks for your feedback!) but we have taken a slightly different approach to Entity View layouts in the end. A new experiment is coming next week.
Fixed Bugs
Itâs possible to add content into read-only rich text fields for Integration items via Automations
Emoji-id is shown in slack notifications instead of emoji alias
Weird records in activity log for DBs if restore it along with the Space
Broken board setup if âhide empty lanesâ option is on and database used in lanes is renamed
Some fields are fully white in Whiteboard even if the dark theme is on
IfEmpty(âŚ) formula after saving - IfEmpty(Employee,Study.Employee).Name
Is there a reason why youâve chosen to make the width editable on a âper elementâ basis instead of just making the entire main column fill the available space responsively? It just seems more confusing than it needs to be.
This is all I care about (assuming youâre not talking about just relation views embedded in Rich Text fields but the actual related fields themselves)! Hope itâs next week.
Text becomes harder to read when the line width approaches 100+ characters. Check out your favourite blogs and online newspapers â I bet most of them wonât take the full width of a 27" screen.
Yeah, we donât really use Fibery a lot for docs/big blocks of text, itâs more for contextual entity to entity linking with usually short names, but I can understand how it could be annoying for others with huge amounts of copy.
Is the sub-grouping by field in lists/tables feature still coming soon too?
Both the improved width options and more flexible grouping will help us out immensely!
I reworked some of my entity views to put lot of fields in this section⌠they are not workable anymoreâŚ
Why donât you maintain the experimental flag until the next release and a little bit more to adjust things ?
I know that was not ideal but it was a least better than nothing
It was technically challenging to maintain both the old and the new approach so weâve sacrificed the old one to get the new one to production faster.
Iâm sorry weâve erased your effort with pinned Fields. Usually, our experimental features simply graduate after some polishing based on customer feedback. This time it was the idea, not just the implementation, that was experimental and this idea turned out to be somewhat of a dead-end.
I hope youâll eventually like the new approach more
Iâm grateful for this. The âNotionificationâ trend in UI updates of apps is helpful in some contexts but I think that the Fibery Entity view is doing something unique. Iâm happy that this isnât the future for us.
Wide Rich-Text Field Content
text tables;
Minor Improvements
Experiments
Fixed Bugs
I reworked some of my entity views to put lot of fields in this section⌠they are not workable anymoreâŚ
