On Thursday, February 5, 2015 at 12:35:35 PM UTC-5, Leonel Câmara wrote: > > It also depends on how you choose to look at it. From my point of view the > message for a label for a field *is* part of the model. The only > difference is that you aren't putting it in a database (which you certainly > could). The view should only be concerned with how to display the label not > with the contents. > > So from my POV there is no breakage of MVC whatsoever with labels in > fields. >
Yes, good point. One might say that display related code specific to a given model is properly part of that model, whereas more general display related code (e.g., formstyles) belongs in a separate layer. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-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.
