Guys, I do agree the way Django handles styling for widgets is a bit unfortunate and can understand your rationales. I just did like to express a point of view from a developer, where some of expectations (declared *Twitter Bootstrap <http://getbootstrap.com/> integration*) hit the harsh reality (partial only). Believed in lifting most from a dull task with layout styling by a ready-made framework.
As Eduardo pointed out, optional passing of custom attributes would greatly improve flexibility and conforming to Bootstrap's sane defaults won't confuse users and simplify work of Mezzanine devs. Now it is a mix of both stylesheets. It is true, dynamic handling of class attributes would add some overhead but I think it would be negligible. I did measured monkey-patched vs original Cartridge's *OrderForm* in production mode with wrk and the difference in rendering times was lesser then 0.5% . In addition, Mezzanine already *does* set widget classes at the runtime in some forms, so the performance reasons are even more questionable. I find the most serious issue with breaking existing compatibility, for already deployed projects. Glad to hear how would be welcomed better standardisation from other devs. Anyway, thanks for the great work and contributions. If you would decide some day it is a good idea, I'm ready to lay a hand at implementation. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
