← Back to team overview

openerp-community team mailing list archive

Re: Individual column filtering in Odoo


Hello everybody:

My feeling is that Oscar's idea would be really usefull for old and new
Very simple case of use (now testing projects/tasks) on Odoo:
I want to look for tasks of a single project.
I need doing this actions on screen:

1. click on combo
2. click on advanced search
3. look for field project
4. assing value on field
5. If I save filter, value on field is fixed, so
6. if I want to look for another value/project, I need
7. looking for this filter
8. Change value...

On Oscar's aproach (similar to search views on last version) I just need
having project field included on it, so steps are:
1. write project name substring
2. search
3. Needing a new project, type a new name.

That's all

You can see it's much more intuitive usable for end customer be new or old.
For me (sincerelly) we lost a lot of usability with this new "one single
combo" on searching items.

My 2 cents.


2014-06-19 10:49 GMT+02:00 Olivier Dony <odo@xxxxxxxxxxx>:

> On 06/18/2014 07:01 PM, Oscar Alcala wrote:
>>         The odoo team already did some improvements on the search Omnibox:
>>         Inline image 2
>>         This is a great feature, but I still think that can it can get
>> better
>>         it feels really weird clicking on a dropdown and suddenly seeing a
>>         stripe appearing on the top of the list (maybe a search icon on
>> the
>>         header will make it more natural), dont get me wrong, current
>> filtering
>>         works fine and the Odoo team is focused in making thinks simple, a
>>         single search box is a good choice for new users, this is because
>> they
>>         are not familiar with the UI, but what about users that know they
>>         data?, users that already know the UI, these users need to focus
>> on the
>>         data itself, so using live filtering on text boxes on each column
>>         header seems to me like a way to go.
> Like all UX design choices, it is something naturally subjective, so I can
> only give you some hints.
> As you know, the omnisearch allows you to do everything from a single
> place:
> - filter using predefined filters (type the name of that filter)
> - filter using custom filters (type the name of the custom filter)
> - filter on fields that are not visible in the current (list/kanban/graph)
> view
> - filter using smart filters that can execute arbitrary filter
> expressions, search on multiple columns at once, etc.
> - craft complex filters with advanced search expressions (and save them as
> custom filters if needed)
> - automatically combine filters with AND or OR operators as required
> - toggle pre-defined group-by filters for data analysis
> - etc.
> This cannot be accomplished with multiple input fields on top of each
> column, so experienced users will definitely need to continue using the
> omnisearch.
> But, even the basic "Search field for 'foo'" is just as fast with the
> omnisearch. You type "foo" and then use the arrow keys to select
>    "Search Name for: foo"
> or "Search Status for: foo".
> Plus it will try to only auto-complete what makes sense, for example the
> suggestion for "Search Status" will only come up if what you typed matches
> a possible status.
> Based on this, having extra search fields on each column seems like it
> would only clutter the interface without bringing any added value.
> The main reported problem with the v7 omnisearch is that many2one fields
> are autocompleted using an automatic search in the data, which can slow
> down the autocompletion in some cases. So for v8 we'll make that search
> only on-demand, and the initial pop-up for suggestions will come up
> instantly all the time.
> From our R&D point of view it seems better to improve the current
> omnisearch to make it efficient for both new and experienced users than to
> introduce more complexity/clutter in the interface.
>          I know it won't apply for all type of fields (Computed, Property
>> and
>>         Related), but what about having all fields searchable by
>> default?, It
>>         will make the module development process simpler, no need to
>> declare
>>         where I can or cannot search.
> As listed above, a search view involves more than just being able to
> search each field with "field contains foo", so it is a good idea for the
> developer to think about it twice. We could think about pre-populating the
> search view with visible fields, but that would make the search view API
> hybrid and more complicated.
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp

CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono oficina:
(+34) 943 02 69 02
Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone: 677 93
42 59. User/usuario skype: Avanzosc

*El contenido de esta comunicación y de toda su documentación anexa es
confidencial y se dirige exclusivamente a su destinatario. El uso no
autorizado de esta información está prohibido por la legislación vigente.
Si usted no es el destinatario le rogamos nos lo indique, no comunique su
contenido a terceros y proceda a su destrucción. Disculpe las molestias que
le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran
en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse
para ejercer sus derechos de acceso, rectificación, cancelación y oposición
en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -
administracion@xxxxxxxxxxxx <soporte@xxxxxxxxxxxx> *

*Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta
hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu
egiten du bertan eskainitako informazioa baimenik gabe erabiltzea.
Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez,
guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu.
Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak
Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea
eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka
egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio
Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 -
<soporte@xxxxxxxxxxxx> *
*This message and all documents attached to it are confidential and
intended only for the person or entity to which it is addressed. Any use of
this information by unauthorised persons is prohibited under current
legislation. If you received this message by error, please advise us,
destroy it and refrain from communicating its contents to third parties. We
apologise for any inconvenience receiving this email improperly may cause
to you. Your personal data are included in a file owned by Avanzosc, S.L.
If you want to exercise your rights of access, correction, erasure and
objection you can contact the Controller at Julio Urkijo, 32, 20720,
Azkoitia (Gipuzkoa), T: 943 02 69 02 – administracion@xxxxxxxxxxxx

Follow ups