On Tuesday, May 8, 2012 7:43:31 PM UTC+2, Cédric Krier wrote: > > > 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 >
8 colors seems to be quite enough (well, maybe 7 since I'm not sure it would be wise to use "white") and it would only be a slight alteration to the COLOR_SCHEMES defined in tryton.common. While re-working colors, I guess enabling customization of 'required' and 'invalid' colors could be a good idea for the same theme-related reasons. > 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. > That would work. I was thinking about having a _highlight (or something else) property on models that would be a dictionary with 'icons' and 'colors' as keys. The values being a pyson string a bit like field states work but with colors/icons instead of just True/False > 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. > No border for un-colored records and a colored border for colored records. I guess it could work but I'm not sure whether it's good either. Back to the huge white square... The square is shared between views, but would it be a problem to implement the same behaviors in all view types? This area already is partially "record dependent". I mean the record number on the right is updated in both view types. So why not update more than the record number still in both view types? I'm still thinking about an icon to the left of the title and also colors; either coloring of the font or maybe better coloring of the background using the "coupled" color of the record (ie: red font for the record in the list view and light red background for the title area) I think it might be more obvious than just a border. I guess border and title area combined could be good? -- [email protected] mailing list
