You can click on the Google or Yahoo buttons to sign-in with these identity providers,
or you just type your identity uri and click on the little login button.
similar as onerowtable, but displaying buttons below
we decided that cw should not be cluttered with such generic-but-not-so-reusable code
some discussion before rejecting it would be greatly appreciated.
please provide use cases and screenshots
there is nice ascii art in the patch describing it.
I've a use case in client project, and it seems worth having it in cw.
Please keep it in the client cube. Not worth it imho.
esp. because of the:
+ def _render_buttons(self, w, form):
+ super(TwoRowsTableFormRenderer, self)._render_buttons(w, form)
imo this is an implementation detail we don't care much about.
And this is a "very base" renderer to me.
If there is a consensus we should not have such collection in cw, then ok to drop it.
Well, I don't know this "we". I do care very much about it.
I suspect be don't need new formrenderers in cw, but less.
The very base ones.
New fancy renderers belongs to cubes.
Ticket #2528129 - latest update on 2012/12/17, created on 2012/11/30 by Sylvain Thenault