On 1/21/07, Ksenia [EMAIL PROTECTED] wrote:
Hi,
I am playing with Pylons several weeks now and it's been a big joy to
use. Everything just fits together and I think because of Pylons I
finally start to get what MVC is all about and see the advantage of
clear separation.
The piece that I am not sure where it should go, are widgets. The DRY
is great, boring error handling is great, but: AFAIK the validation
belons to the Model, but the UI belongs in the View, and the gluing
of M with V belongs to Controller. So the widgets go right through all
of the layers... Ok, I can live with that :) But than there is not
anymore only one way to do it. Where ends widget and starts the page
template? Is it just form rendering? No, grid with records can also be
a widget or should I just render it in the template file? Should I
only make into a widget something that I want to reuse? I saw the
thread about portlet-style site
(http://groups.google.com/group/pylons-discuss/browse_frm/thread/2a52b3a490f5d211).
Wow, I can even use subrequests. Than I don't need widgets at all - I
can just collect all those /doc/view/123, /news/latest, /user/list,
/user/view/myid into one page. But on the other hand, I can make all of
them into child_widgets and create one big page widget to display
them...
I wonder what other think about widgets in relation to MVC in general
and Pylons in particular :)
Before we get too carried away, perhaps you'll enjoy this:
http://jjinux.blogspot.com/2005/04/mvc-cargo-cult.html
Happy Hacking!
-jj
--
http://jjinux.blogspot.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~--~~~~--~~--~--~---
