Wanted to reach out to the community about a naming issue

  • 1
  • Question
  • Updated 5 months ago
Kasey from Skuid Product Content here: 

If you’re a Skuid builder, you’re probably familiar with Conditional Rendering, a feature that allows you to show or hide a component based on set logic. A few years ago, we added Conditional Enabling, which makes a component editable (or not) based on logical conditions. Both of these are collectively referred to as Conditional Rendering, and are nested under the Rendering tab in components.

However, this is a little like defining a word by using that word within the definition.  Moreover, if we want to add additional “conditional” features, it might be better to have a different collective term for the concept of conditional component actions (changing how a component looks on the screen based on a set of conditions)--and this will likely result in re-naming the associated tab where those features are found.

Internally, we’ve narrowed it down to the following, but I’d like to get feedback from our community of  experienced Skuid builders.  Which of the following works best for you--and would take the least cognitive load to adjust to?

1. Display Logic -- Display logic tab

2. Display Logic -- Logic tab

3. Display Conditions -- Display Conditions tab

Vote for just one!  Voting is open now--and will close EOD March 15.

Photo of Kasey Arnold-Ince

Kasey Arnold-Ince, Employee

  • 132 Points 100 badge 2x thumb

Posted 6 months ago

  • 1
Photo of Skuidward Tentacles (Raymond)

Skuidward Tentacles (Raymond), Champion

  • 18,126 Points 10k badge 2x thumb
3
Photo of Mike Dwyer

Mike Dwyer, Champion

  • 4,716 Points 4k badge 2x thumb
Conditions belong to models. Rendering is display logic. A tab named Logic suggests a lot more than rendering/enabling/display.

Of the available choices: 1

Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,468 Points 4k badge 2x thumb
I suggest Option #4 --> "Display Rules"...as in rules that determine how your data is displayed to users. Conditions determine what data is displayed to users (I agree with Mike on that point), and logic seems too technical to me (Skuid is for regular people to build apps, not developers).

As part of these "Display Rules" ;) could we also have access to design variants in a future release? For example, if checkbox = TRUE, display component with red background.


Photo of John Dahlberg

John Dahlberg, Champion

  • 4,316 Points 4k badge 2x thumb
1 works for me, but I could go with Conlan's recommendation as well.  

This did trigger a related feature that would be very helpful to add, which is to have rendering and enable logic connect more intelligently to the data in a model.  Currently you can check the first row of a model, but it would be helpful to evaluate if any rows contains a value.  This would allow for a control table to drive what users have access to in the UI.  Then you can just add or remove rows to the control table to map the features you want to enable for users.
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,468 Points 4k badge 2x thumb
Winner winner, chicken dinner...


Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,828 Points 20k badge 2x thumb
Chicken dinner indeed!