On 08/05/12 09:56 -0700, Emma wrote: > > > 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?
It is the same issue. This place is shared between form and list. > > 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. So then we must define a global schema for the colors that will be customizable on the client side with preferences. I propose to use the color names: https://en.wikipedia.org/wiki/ANSI_escape_code#Colors Than we could have a configuration object that will give coloring rules to Model using a rule system and those rules will be push to the client via the fields_view_get. This make the colorization just a configuration job. But we still need to find a way to display this color to the form view. I thought (but not sure it is good) to put it in a border of the form. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgprxHtR7RMZ0.pgp
Description: PGP signature
