Cartodb: UI to check all fields on JOIN analysis

[jsanz]

Maybe this could be generic and applied to any case where using checkboxes to select fields list but it's a very common scenario to have a table with a normalized field so you want all the fields from the origin table and just a few from the join table.

The UI to select fields is quite small, using the keyboard to select fields is not easy and the scroll can easily jump more than one visual page so it's hard to quickly select all fields.

[xavijam]

Let's summon @saleiva here.

[saleiva]

a button for selecting ALL / NONE was originally designed on the first version of this component by it never got implemented. All yours @xavijam

[zingbot]

+1 on this. Just struggled with selecting 30 checkboxes:)

[jsanz]

The predictive analysis really needs this select all/none UI, friends :sweat_smile:

[saleiva]

adding next, since this is the most popular analysis by far

[xavijam]

_plegarias escuchadas_

[xavijam]

For new mates

[rubenmoya]

Should the 'ALL' and 'NONE' buttons de/select everything in the list, or should it be smarter and only select the search items?

Example:

1. User selects absolutely everything (20 items)
2. User types 'vamos', there are 3 items matching
3. User hits 'ALL'

What should be selected then? Just the three matches? Still everything?

Same question but with 'NONE', should it only deselect the search results?

[xavijam]

That's a good one, @saleiva what's your opinion?. IMHO I'd deselect all items, because when you filter by something, rest of items don't matter.

[jsanz]

This could be confusing without changing the label to something like ALL SELECTED but yea, the functionality would be well received, I can tell you.

[zingbot]

Agreed it would be a really well-received option. 'All Filtered' or 'All Visible' could make that clear, too

[nobuti]

In production.

[saleiva]

BOOM!