cck fields should use views operators in views hooks for consistency

Views defines a certain number of operators, including and/or/nor, or/nor, equal to/not equal to, greater/equal/less than, yes/no, and like. If I expose e.g. a node title filter and a special cck text filter, they have different fitering options: node title has contains/starts/ends/not/= (through the "like" operator handler), while my cck text field has =/!=/like. This is confusing to users, since both are text fields.

CCK fields should find a way to use the default views operator handlers, depending on the widget they are using.
Moreover, views operators have a way to deal with empty search fields, while cck custom operators don't, it seems (see this other issue)

Opinions?