* Cédric Krier: " Re: [tryton-dev] What should be the search on: 1..42" (Thu, 12 Jun 2014 12:38:45 +0200):
> On 12 Jun 12:29, Mathias Behrle wrote: > > * Cédric Krier: " Re: [tryton-dev] What should be the search on: > > 1..42" (Thu, 12 Jun 2014 12:11:13 +0200): > > > > > On 12 Jun 11:59, Mathias Behrle wrote: > > > > * Cédric Krier: " [tryton-dev] What should be the search on: > > > > 1..42" (Thu, 12 Jun 2014 11:06:34 +0200): > > > > > > > > > Hi, > > > > > > > > > > We get some astonishement with the current behavior of the client with > > > > > the range search syntax. > > > > > > > > > > Currently: `Field: 1..42` will become > > > > > > > > > > `[('field', '>=', 1), ('field', '<', 42)]` > > > > > > > > > > But it seems people expect: > > > > > > > > > > `[('field', '>=', 1), ('field', '<=', 42)]` > > > > > > > > > > One point about the current behavior is that you can slide the range > > > > > by the length and it will not contain any duplication. > > > > > > > > > > So what do you think? > > > > > > > > From a user perspective the search imitates 'from 1 to 42', which > > > > includes 42 in the selection. > > > > > > What is the original of 'from 1 to 42'? > > > > Sorry, I don't understand the question. > > You say that the search imitates something which has a specific > behavior. But where does it come from? As Albert says: When you talk to the user about a range, he answers: 'Ah yes, you mean from ... to ...'. And he will expect to see both boundary values included. -- Mathias Behrle MBSolutions Gilgenmatten 10 A D-79114 Freiburg Tel: +49(761)471023 Fax: +49(761)4770816 http://m9s.biz UStIdNr: DE 142009020 PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature