On Tuesday, 8 May 2012 17:50:31 UTC+2, Cédric Krier wrote: > > I don't think the "huge white square" is the right place to put > information about the current record in form view because it is the same > white square displayed in the list view. So it is bad to have different > meaning for the same widget. >
What about left to the huge white square then? In between the huge white square and the form menu icon? > Yes, it could be good for completness to be able to diplay icons in > form. And icon is just a selection field, so why not having a widget > icon for such fields. > A widget or maybe have an icon property defineable for records (then display it in tree/form/any other view) > For me, the color should be removed because it can not be managed > correctly with the theme of the client. You can have wrong combination > that makes text unreadable. Indeed I think colored icons could be a good > replacement and if there is a widget for the form view, than we have a > global solution. > A global solution is clearly the way to go, I also think it's wrong to define colors separately in tree views. But I think the "manageabilty" of colors in respect to the theme of some users is a non-issue if well thought. First of all Tryton is a professional software used in a professional environment, therefore few people customize their theme. BUT that's not a valid reason to ignore those few people (I'm one of them). That is why I suggested the tagging system and the ability to customize the way tags (or however you want to call them) are rendered on a per-user basis inside the preferences for those who do customize their themes and who might run across incompatible renderings. Plus, so far the colors that have been used are "pure basic" colors (blue, grey, red, ...) which are not really used in themes, so even if incompatibilities might occur it's still probably a very rare exception. Also, using a cutomizable tagging system (system-wide AND user-defineable) would let companies decide the way they want things displayed (opposed to the current color system in tree-view, ie: the sys-admin wants draft account moves to be listed in grey instead of red because it's the way their old accounting software used to do it and people are used to it). Should colors be the default way to highlight records? Probably not, but on 5 people taking part to this current thread, 2 have been asked by clients to use colors, so I think banning colors all together is not the way to go either. -- [email protected] mailing list
