Julian Egelstaff

Important element: asking user when/where/how entries are created in the form ("how are new X created?") to get context for screen creation, subform element creation, etc. And further details could...

Can we have options for 'standard' or 'demo' applications? So people could just turn on an inventory system? Can we store the settings in a 'code as config' sort of...

In conjunction with the “reorder elements from the form screen" pull requests https://github.com/jegelstaff/formulize/pull/50 https://github.com/jegelstaff/formulize/pull/81 this could be quite powerful. No need to go to the backend for reordering. But the...

Related to issue https://github.com/jegelstaff/formulize/issues/445

This is the stub of an important idea.

** Logic interpretations in code... Display together is not in the UI and logic is removed from the system. Screen admin UI updated to show the system wide relationship as...

Lower priority

Interesting. This may be a side effect of some other changes. There were some issues where nonexistent elements would find their way into the rendering process, and by ignoring elements...

We need two broad additions to the way this works: 1. We need a way of flipping 'Formulize Awareness' on and off. This would enable injection of permission filters, scoping,...

Also critically, we need an option to retrieve data from the form plus its close relations, ie: one hop away in a relationship, like how getData does now. ``` $form->plus($relationship)->query()...