Interesting! But I’m not quite sure if I understand it correctly. Should this section be able to display pages as well as files? And not only children, but everything possible via query? Something like a combination of rasteiner’s “pagesdisplay-section” and sylvainjule’s “pagetable”?
That sounds very useful, but it could possibly be that I have a slightly different focus in mind, namely database-like applications.
In my eyes, the section shows its strengths where you work with many data sets (subpages) that tend to be complex. In such cases, simple and fast data handling would be a real advantage. This would definitely include an add button. I can also imagine an explicit delete button per row (or batch processing via checkbox) as well as handles for manual sorting.
So I imagine an extended kind of data processing that is achieved by means of a specific representation. For such a section, a name like “display” would probably fall short, because it would not describe the functional benefit that the section would offer. Rather something like “datatable”, similar to “pagetable” by sylvainjule.
The search function of the original pagetable field is also really useful, again especially in database-like applications with many child pages acting as datasets. The same goes for the sorting function based on the column headers.
Having the options dialogue available per row would certainly be good. And by min/max limit, do you mean pagination of the list? That too, yes.