Actually, the labels are part of the visualization layer. HTML widgets and CSS classes, as well.
By definition, the model doesn't need the label to anything. Take a webservice as an example, doesn't have a form to present. Does the model need it? So, we conclude the label (and other artfacts) don't belong to models, but to the visualization layer. ---- On Thu, 05 Feb 2015 14:35:35 -0300 Leonel Câmara<[email protected]> 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. > > > > > -- > 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. > -- 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.
