Formulize has never had a strong, separate controller. The "smart dumb functions" like displayForm and displayEntries actually manage a lot of the controller work.
If there were a strong controller, that was designed to receive certain standardized bits of inputs, like active user, form submission, active page, and a certain series of operations possible, like search or next page or save, or a combination of them, etc... is that possible? Would that allow a true "headless" design?
Right now, if you try to use Formulize as a data-store, and write your own front end, you have to write the whole application logic, because it's enmeshed in the interplay between the UI and the displayForm and displayEntries and displayFormPages functions, etc. What would it take to generalize and standardize a controller architecture, as a kind of API, which we could use for our own standard front end, but could then also respond to other front ends and applications?
Formulize has never had a strong, separate controller. The "smart dumb functions" like displayForm and displayEntries actually manage a lot of the controller work.
If there were a strong controller, that was designed to receive certain standardized bits of inputs, like active user, form submission, active page, and a certain series of operations possible, like search or next page or save, or a combination of them, etc... is that possible? Would that allow a true "headless" design?
Right now, if you try to use Formulize as a data-store, and write your own front end, you have to write the whole application logic, because it's enmeshed in the interplay between the UI and the displayForm and displayEntries and displayFormPages functions, etc. What would it take to generalize and standardize a controller architecture, as a kind of API, which we could use for our own standard front end, but could then also respond to other front ends and applications?