Table layout for sections#80

Great for data-oriented projects. The table of subpages can be searched, sorted and provides very flexible layout options.
https://github.com/sylvainjule/kirby-pagetable

Pagetable doesn’t support file sections and has no plans to do so (see this issue). If this was ever added as a core field, it’d be great if the solution could also support file sections.

I imagine a new seciotn type, e.g. display. And you can define columns (what data to pull in, widht, lavel, how to show…). The cell value could be defined via field name or even more elaborate query (“page.myCustomMethod”). And then you define rows via a query.

That alone would be pretty straightforward. The difficult questions then are: does it have an Add button? Is there then a min/max limit? Doe the rows have options?

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.

@hherold I think your thoughts warant a separate feedback/idea here. You seem to have many more ideas in mind than the plugin already covers. And even the plugin is a combination of various aspects (table layout, query option…)

I think we need to split this up to make it actionable. If not, we might implement one aspect (e.g. table layout) already and then we close this idea and other aspects could get lost.

From your descirption I already see various feature requests:

• table layout for sections
• query option for pages/files section
• section that allows to combine pages and files (or even other records from database)
• search (already has a separate idea https://kirby.nolt.io/14)
• batch actions for sections
• Sorting function based on table column headers

I have change the title of this idea to be more specific and actionable, but also created new ideas for parts of this conversation that won’t be covered by Kirby 3.7.0

https://kirby.nolt.io/436
https://kirby.nolt.io/437
https://kirby.nolt.io/438
https://kirby.nolt.io/439

Feel free to upvote or also create additional ideas if I missed something.

Hi Nico, sorry for the late reply, I am currently involved in a larger project. Thank you for breaking it down into individual aspects. This makes perfect sense and is of course very Kirby-spirit. So great that a lot of this will now be part of 3.7. Kudos, fantastic work!