thx for working on this!
I have a general question regarding how this proposal overlaps or complements the one at LiveData for Cristal . The later also tackles batch updates and since we want the LiveData component to be the same for Cristal and XS, we need proposals that are compatible and work the same.
Could you check this out with @tkrieck ?
I think we need consistency in term of L&F between a LD with an Action column (as we have now) and this batch action proposal. To reconcile both, I’m proposing that:
- We allow a config option for LDs, to say that a LD has actions for it (like Edit, Delete, etc)
- We have another config option for LDs, to say whether multiple selections are allowed or not.
If we have actions = true but multiple = false, we still display checkboxes on the left (but not the global checkbox to select all), and only allow the user to select a single row.
Technically we could imagine preserving backward compatibility, when an _actions column is defined, don’t display a new column but display the actions in the L&F defined in this proposal, for consistency.
So this means a single click on it selects ONLY the visible LD rows, and there’s some text displayed with a link to allow selecting ALL rows:
The table needs to be a LD for scalability.
General important remark re the move and delete proposed UIs: I’d like to have consistency between the single item delete or move UI and the batch deleteor move UI. Basically they need to be the same UI for me (with possibly some inir differences but at 90+% the same).
Could you update the proposal to have this consistency?
Thanks a lot!