Guiding the eye of users to points of attentions is key for a good UX. Especially in a data-heavy environment that most foundry use cases live in (just asuming your use case requests are similar to mine ).
For this - other platforms allow pretty neat visual cues like data bars and conditional icons.
I would love to have this type of flexibility in object ables and pivot tables
Here two examples (with notional data) from a platform I will not mention here by name
Additionally I would love to have icons generally more dynamic condition-based. Just like how we can set colors on metric cards dynamically, it would be cool to also switch the icon.
Love the idea of expanding conditional formatting with more functionality, like adding icons. In the past I’ve done this with little helper functions - normally a version that returns a “display” version of the property and then another version that implements the object type <> string map function to it can be used as a derived property in an object list or table widget.
I particularly like using the basic color emojis for “stoplight” style indications:
I’ve also written some functions in the past to use the empty and filled square emojis to create inline charts/progress bars, which work nicely both in Metric Cards or as derived properties
Progress: (0/11)
Also also, if you model the relevant data as a time series, Workshop has quite a feature set for inline “sparkline” style rendering.
Awesome idea @lrhyne ! Could you share an example screenshot and code snippet how a metric card looks? I understand your function return a string that has the icon code (or directly iconized symbol?). But, the color coding you still control via the usual conditional formatting of the underlying base value, right?
For the tables, yes my thoughts also went into the direction of sparklines. However, you don’t always have time series friendly data (last time I checked e.g. categorical states were not supported).
And imho workshop is so no-code friendly - achieving this should be more convenient than always using function backed columns (variables) or timeseries OTs
).
