Well, I used Cook for personal uses to answer professional customers needs.
So I started to develop this functionality. Even Imports.
But both of them are not ready at all. Totally in standby for the moment.
It is not a question of simply enable or not.
I mean, it is not locked for a commercial strategy.
All functionalities present are all we have.
I will even propose some complex functionalities in beta, in order to let you enjoying before the final stability (Files and Images are coming soon, in beta)
Export is much more easy than import.
If you want to do this,
Create a new layout in the Builder. ('export' for example)
You can even use filters.
Compose the export layout adding all the joined datas. (It will create the SQL call)
Then, when you develop inside, don't show it.
In the view file, instead of displaying : parent:display()
Try to make a dump of you $items var, and you will find your beatifull array with all datas you need.
So.
In the helper maybe, create a function that convert such array in CSV.
You can, then, output the file with a application/force-download mime header, it will download it.
Maybe you can furnish to your function an added array to labelise the column, and to dispatch the fields
-> label
-> order
-> presence or not in export (because all columns of main table are selected in default query)
If you want to optimize the query for big table, you can also create, in the model, a new query profile.
If you write well, your export functionality will even be reusable for any export you want.
Really easy. Cook does 80% of the job. (even more)
Cannot help you more.
