Am Donnerstag, 23. Januar 2014, 20:06:09 schrieb Guillem Barba Domingo: > El 23/01/2014 16:52, "Sergi Almacellas Abellana" <[email protected]> va
... > >>> > 1) flexible adding and removing of columns: > >>> > Similar as in some office programs (LO), right click on the header > > line to change the columns displayed. That would give the user the option > to add columns he needs and remove those that are not of interest > > +1 we was talking about this feature few days ago. Good, seems that most participants in the discussion see this requirement > >>> How do you prevent to bloat the system by adding a too big column. > >>> Tryton is modular and adding new column to a view is extremly easy for > >>> any developer. > > Yes, but when you have several users this kind of customizations are.very > usual and it's expensive for customer if each one requires to be done for > us (developers of external company). This answeres the question raised about examples for 'dual customization': Sales, purchase, finance, all have different requirements on search and filter patterns. > So, the goal of this feature is double: > a) allow to have different fields of the same list per each user. It's > tipical for party list: the fields that are important for the accountant > are diferent than the important fields for salesman. > b) allow the user to be more independent from provider for little > customizations. Exactly right: Flexibility means, that a user can configure it to his needs, not that you need a developer to do it (and it is easy for him) > Something to discuss is if this customizations are saved in the server, > related to the user, or in the client side. I vote for the server side, to make it independent from the frontend or PC in use. > >> I think it should be ok to be able to hide / show columns as long as the > >> developper added them in the view. > > I think it's enought and it prevents to add some functional field that > could generate performance issues. > > > I have seen some users that make the width of some columns 0 pixels. As > > tryton remembers the column width for each users you get the same result as > if you hide it. > > > So a developer can add all the needed columns and the users can resize > > the columns they don't need to size 0 (hiding it). > > If the column is hidden it is not reached by the client => less data to > compute, to send to client and to manage for it. Yep, thats better than setting the width to Zero. > >>> > 2) Re-sorting of column-order > >>> > ..either by drag N'drop, or by sorting in the menu selection und 1) > >>> > >>> How do you store it. Why do you need it? > >> > >> +1, do not see the use > > Same reasons that show/hide columns. Different users/roles need different > data available quickly: if you have a list with lots of columns could be > fields that you need to scroll to be shown => not quickly available > > >>> > 3) Apply 'Auto-Filter' > >>> > Instead of having a filter bar above the column headers, have a > > filter field under each column header with a similar functionality as you > know it from the Spreadsheet-Autofilter. > > >>> How do you express 'OR' ? > >>> The current search bar is very flexible and also smart, your proposal is > >>> inferior. > >> > >> Maybe using both options would be possible . I agree with you Cedric > > that the > > >> search bar is very flexible, but Axel has a point. Sometimes, a simpler > > / quicker > > >> way is good :) > > > > IMHO the save search feature is enough for this part. You create all the > > filters you want, save them and apply them whenever you want. Isn't this > feature enough for your use case? > > I think it is an UX improvement but for me not very important as you have > alternative solutions (search form + save filter) I think the autofilter is more intuitive for the 'normal' user. Best/Axel
signature.asc
Description: This is a digitally signed message part.
