Re: [tryton-dev] Colors of fields

[Albert Cervera i Areny]

2015-07-06 23:36 GMT+02:00 Cédric Krier cedric.kr...@b2ck.com:
 On 2015-07-04 08:58, Cédric Krier wrote:
 Hi,

 For now, we put a blue color on entries when they are required (and
 switch to red when validated as empty).
 I think it is a bad practice for 2 reasons:

 - the colors are not custumizable and so they could not work on some
   thèmes.

 - it is doesn't help the accessibility [1] as this information is
   only based on color.

 So I was thinking instead about adding a * on the labels of the
 required fields. This still stay quite visual (but not too much) and
 readable for accessibility.

 Indeed the '*' solution is not so beautiful.

 So I worked on an other proposal:

 - make label bold for required field
 - have a better 'invalid form' message that describe the problem

 So here is a screenshot of such invalid form with missing required field
 and wrong value because of domain.
 I think it is really an improvement because now we explain to the user
 what is wrong and experienced user can still anticipate required fields.


I agree it is a very good improvement.

 --
 Cédric Krier - B2CK SPRL
 Email/Jabber: cedric.kr...@b2ck.com
 Tel: +32 472 54 46 59
 Website: http://www.b2ck.com/



-- 
Albert Cervera i Areny
Tel. 93 553 18 03
@albertnan
www.NaN-tic.com

Re: [tryton-dev] Colors of fields

[Jean Cavallo]

2015-07-04 8:58 GMT+02:00 Cédric Krier cedric.kr...@b2ck.com:

 - the colors are not custumizable and so they could not work on some
   thèmes.


Wouldn't it be better to make it configurable someway ?

Our user will really feel the loss of colors as a loss of functionality of
the
client.

2015-07-04 10:49 GMT+02:00 Jordi Esteve jest...@zikzakmedia.com:

 The blue color and switching to red if the field is not filled is
 intuitive and clear for most people, the asterisk is not intuitive (needs a
 previous explanation), so I suggest adding a * without removing current
 behaviour.


Agreed

Jean Cavallo
*Coopengo*

Re: [tryton-dev] Colors of fields and feedback for current interface

[Jean Cavallo]

2015-07-05 9:41 GMT+02:00 Cédric Krier cedric.kr...@b2ck.com:

 I think the info which currently just says 'Invalid form' will need to
 be improved to give the name of the field with error and also I think we
 can give a explaination for:

 - required is simple: Field is required
 - domain invalid: Field must follow: domain parsed
   (only if we can parse it otherwise: Field is not valid for domain)


Love this !

Jean Cavallo
*Coopengo*