Am 27.09.2014 00:14, schrieb Cédric Krier: > On 26 Sep 23:32, Albert Cervera i Areny wrote: >> 2014-09-26 20:43 GMT+02:00 Cédric Krier <cedric.kr...@b2ck.com>: >>> On 26 Sep 20:05, Jordi Esteve wrote: >>>> On 26/09/14 19:35, Cédric Krier wrote: >>>>> On 26 Sep 18:41, Jordi Esteve wrote: >>>>>> On 26/09/14 18:08, Albert Cervera i Areny wrote: >>>>>>> 2014-09-26 17:59 GMT+02:00 M. Murray <murr...@moh.gov.jm>: >>>>>>>> Hello Everyone, >>>>>>>> >>>>>>>> I have a question regarding the search query builder in the tree view. It is >>>>>>>> the window that pops up when you click the "Filters" button/label at top >>>>>>>> left. >>>>>>>> >>>>>>>> How can I modify the list of fields that shows in that popup? >>>>>>> Just change the tree view. You can search on all the fields of the >>>>>>> view except those that are not searchable (usually calculated fields) >>>>>>> and the client also adds some special fields such as id, create and >>>>>>> write date and users. >>>>>>> >>>>>>> Note that you can add fields to the view but make them "invisible" so >>>>>>> they're searchable but are not shown to the user. >>>>>> Adding filter fields with a more flexible way than changing the tree view >>>>>> would be a nice feature for Tryton. In my experience, the user wants to >>>>>> search by a lot of criteria, no only by the fields showed in the tree view. >>>>>> This requirement is very common in party and product views. >>>>>> >>>>>> I don't know if other people has this need and if it would be very difficult >>>>>> to implement in the core of Tryton. >>>>> I'm strongly against, it is a wrong user experience to not show proof of >>>>> the result of a search. >>>>> >>>>>> To fill this shortcoming, we have developed the searching module [1]. It >>>>>> allows search records with flexible criteria in any Tryton model, subfield >>>>>> search in m2o-o2m-m2m and store the criteria in a profile to be reused. >>>>>> >>>>>> [1] https://bitbucket.org/zikzakmedia/trytond-searching >>>>> Too bad to not improve the current search syntax because all the >>>>> features you describe already exist expect for the relation field. >>>> >>>> No, it has another more important feature: In the current filter box you can >>>> not search if the fields are not defined in the tree view, this is the main >>>> shortcoming that this module tries to solve. >>> >>> Better to add the field! This is really stupid to over engineer with a >> >> The problem Jordi tries to address is about the fact that he cannot >> know in advance what fields the user wants to use for searching. In >> fact the user doesn't know either until he has the need. >> >> We discussed this in the TUB and I think several people were >> interested in creating a module that allows users to define their own >> tree views. That would solve the search issue too, with the advantage >> that the user can check the result, which I agree is important. > > *No* developement at all is needed. Everything is already in Tryton. > Also it is because of a bad or lack analysis of the needs that nobody > knows what is needed. It is always the wrong answer to say: We don't > know so let the user do the job.
*Yes* - you can't do an analyses how people discovers data. For example the invoice tree: one want to know about the products sold, one about shipment numbers and an other about the amount. A tree view can't be generic: people is scanning data on a screen in different ways because of both personal preconditions - numbers vs. strings as example - and specialized needs to know what the line is about. And in bigger companies staff is changing ... So you can't say it's a wrong answer: I can't do psychological analysis and not for people I don't know. Each module developed in real life is a indicator for a existing problem in one of the companies using tryton. So for me a discussion about treeview could be a topic on Unconferences ...
