Closed nathanhornby closed 9 years ago
Isn't that more a feature the applied interface should take care of?
But I thought the field options panel was provided by the field itself, or can the UI inject its own settings? Because in which case yes, I suppose that would make more sense.
On 20 Aug 2014, at 17:20, Nils Hörrmann notifications@github.com wrote:
Isn't that more a feature the applied interface should take care of?
— Reply to this email directly or view it on GitHub.
Well, it cannot add settings but an extension can add multiple interfaces (think of the selector that provides a sortable and an unsortable variant).
Ah, so the currently suggested method would be to have them show up in the 'Association Interface' select as, for example:
Etc?
Might that not be a tad cumbersome?
Maybe it's an issue best left to when there's something that requires it - I just wondered if it might be the kind of thing that would be at the field level. Even for the Selector I'd like to be able to order the entries, but it's for a very particular circumstance and I can live without it.
On 20 Aug 2014, at 17:32, Nils Hörrmann notifications@github.com wrote:
Well, it cannot add settings but an extension can add multiple interfaces (think of the selector that provides a sortable and an unsortable variant).
— Reply to this email directly or view it on GitHub.
Might that not be a tad cumbersome?
Well that depends on how many options you need. The good thing about the interface is that they can be applied to any associative field.
Well at a minimum it would be the same number as on the data source select, doubled to account for ascending and descending. So a small section could have 15-20 options, id say in that format it'd be a little cumbersome. And that's ignoring other sort order properties, like random.
Unless of course it's possible to create a kind of 'Association Field: Sorting' extension that could add in a data source like Sorting section (Sort by and Sort order)?
That's really all I see the field needing.
On 20 Aug 2014, at 17:52, Nils Hörrmann notifications@github.com wrote:
Might that not be a tad cumbersome?
Well that depends on how many options you need. The good thing about the interface is that they can be applied to any associative field.
— Reply to this email directly or view it on GitHub.
This might be a pipe-dream, but is there any likelihood of including an 'order by' option for the field, like we have in data sources (for example)?
I tend to make heavy use of the Order Entries extension, so would like to order by that field. But naturally you might sometimes wish to order by a date field, ID, name, all sorts. But I'm not sure how feasible this is.
The current UI option (selectable) is naturally more focussed on search, but there may be some UI's that aren't, and so order might become quite important for the display of the associated entries.