Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

selection tab title is misleading ? #115

Open
landryb opened this issue Apr 9, 2021 · 3 comments
Open

selection tab title is misleading ? #115

landryb opened this issue Apr 9, 2021 · 3 comments

Comments

@landryb
Copy link
Member

landryb commented Apr 9, 2021

when testing, @stous found it confusing that a graphical (point/line/polygon) selection tab title was 'Selection', since no entries are actually selected in the list. (shows 2 objets (0 sélectionnés))

adding to this, in the preferences tab, there are 'default' (translated as 'Liste') and 'selected' (translated as 'Sélection', cf https://github.com/georchestra/mapstore2-cadastrapp/blob/master/assets/translations/data.fr-FR.json#L84) - i'm not sure 'Selection X' is the best word to use .. should we reuse Liste there ? 'Résultat de recherche' is too large. Or it should be 'Point X'/'Line X'/'Polygon X' (with translations !) so that the user knows which tab matches a 'graphical selection' ?

this is discussed a bit in #93, and that also shows that 'Selection' isnt a translated string, which might be an issue too (in french it would be Sélection or something better) ? the various strings in

function getTitle(searchType, rawParams) {
switch (searchType) {
case SEARCH_TYPES.REFERENCE:
return rawParams?.commune?.label;
case SEARCH_TYPES.ADDRESS:
return rawParams?.commune?.label;
case SEARCH_TYPES.LOT:
return "Lot";
case SEARCH_TYPES.ID:
return "Id(s)";
case SEARCH_TYPES.OWNER_ID:
return rawParams?.commune?.label;
case SEARCH_TYPES.COMPTE_COMMUNAL:
return rawParams?.comptecommunal;
case SEARCH_TYPES.OWNER_LOT:
return "By file";
default:
return null;
}
}
arent translated either, and i havent found where 'Selection' comes from.

@MaelREBOUX @catmorales i'm sure you'll have ideas on this.....

@MaelREBOUX
Copy link
Member

Hummm.... not easy.

Let's see :

  • the Selection 1 and Selection 2 tbas ar created by clicking on the map
  • the Bruz (350047) is created by searching by plot
  • the Lot is created by typing a plot id

image

I suggest we could manage only 2 kinds of events : Selection / Search ?
Numbered as said in #93

@landryb
Copy link
Member Author

landryb commented May 5, 2021

but 'selection' is misleading here i think since there's a "second selection" to do in the list, so it should rather be 'point/line X' ?

@MaelREBOUX
Copy link
Member

it should rather be 'point/line X'

No because your list selection could be done by the 3 geometric methods. I think dicriminate by selection / search method + numbered tabs is an acceptable way. Not ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants