In the beginning, the display of lists was hard coded. In the second version, it was still hard coded, but it was now encapsulated in the "smart dumb function" displayEntries.
Then we realized that we kept using the same options in the function, to customize the behaviour in certain ways. What if we had admin controls for those options, then we wouldn't need to write code the used the function, we could manage entire applications through config only. This insight created "Screens" in Formulize.
After many, many years, we keep seeing the same kind of patterns in how screens are used to make lists. So why don't we make more screen types, different types of lists, to package up standard use cases. Such as lists with editable elements. Lists that are purely display oriented. Lists that are for reporting/data browsing. Lists that are for approval of items, with a custom button, etc.
And let's allow any type to be edited with an "advanced" interface that provides all the features, perhaps that's a toggle. Or perhaps it's a conversion from one screen type to an Advanced screen type. There's a UX / conceptual issue to consider, about whether people think of the advanced as a type, or as just more options for any type.
In the beginning, the display of lists was hard coded. In the second version, it was still hard coded, but it was now encapsulated in the "smart dumb function" displayEntries.
Then we realized that we kept using the same options in the function, to customize the behaviour in certain ways. What if we had admin controls for those options, then we wouldn't need to write code the used the function, we could manage entire applications through config only. This insight created "Screens" in Formulize.
After many, many years, we keep seeing the same kind of patterns in how screens are used to make lists. So why don't we make more screen types, different types of lists, to package up standard use cases. Such as lists with editable elements. Lists that are purely display oriented. Lists that are for reporting/data browsing. Lists that are for approval of items, with a custom button, etc.
And let's allow any type to be edited with an "advanced" interface that provides all the features, perhaps that's a toggle. Or perhaps it's a conversion from one screen type to an Advanced screen type. There's a UX / conceptual issue to consider, about whether people think of the advanced as a type, or as just more options for any type.