For me, there are not much differences between view based approach and
the controller based approach. Of course, functions are first class
objects in Python.

MVC is an abstract concept, a pattern for classifying the data,
actions and presentation/view. Languages and frameworks(framework
developer) gives different shape for implementation of MVC concept.

Your question seems like comparison between Object Oriented vs
Functional approach. We have to see, how best we can add hacks/hooks
into the framework to solve our own problem (not the framework's
problems :-) )

We tried both Django and Struts, none of them solved my problems on my
own way.  With pylons, I have solved my own problem with my own way.
This is what I need from a framework.  (We have developed internal
portal for test case management for HART protocol. First we tried with
Struts 2 and later moved to Django then finally we implemented in
Pylons).






On Jun 14, 1:17 am, "Shannon -jj Behrens" <[EMAIL PROTECTED]> wrote:
> Yes.  You could hack around that, but it'd probably be painful.  What
> I'm saying is that:
>
> a) Using classes is a good idea.
>
> b) Pylons doesn't force you to code a certain way within those
> classes.  You can move as much or as little as you want into the
> models or other libraries.
>
> Best Regards,
> -jj
>
>
>
> On Fri, Jun 13, 2008 at 6:53 AM, askel <[EMAIL PROTECTED]> wrote:
> > -jj,
>
> > Isn't that enforced by Routes that controllers must be classes? I
> > remember some discussion about possibility of using any other
> > dispatching library/method in Pylons. It was something about new WSGI
> > environment key "wsgiorg.routing_args". I might be completely wrong on
> > that though.
>
> > Cheers
> > Alexander
>
> > On Jun 12, 9:59 pm, "Shannon -jj Behrens" <[EMAIL PROTECTED]> wrote:
> >> On Thu, Jun 12, 2008 at 10:05 AM, rcs_comp <[EMAIL PROTECTED]> wrote:
> >> > On Jun 11, 4:10 pm, Karlo Lozovina <[EMAIL PROTECTED]> wrote:
> >> >> What's the practical difference between controller based approach and
> >> >> views based one? Eg. Django views, and controllers in Pylons? It
> >> >> doesn't seem that much different, so why not make all controller
> >> >> actions regular functions, instead of class methods? What's the gain
> >> >> in this controller approach, if any? :)
>
> >> >> Thanks...
>
> >> > I differ a bit from the opinions above.  I like to think of a web
> >> > request as asking "show me something."  Therefore, IMO, it makes sense
> >> > to map a web request to a "view".  The view (a Python class) then
> >> > knows how to use actions (a Python class) to "do something", the
> >> > actions know how to use the model to get work done.  The view then
> >> > renders a response in an appropriate format (HTML, JSON, etc.) using
> >> > any helpers necessary (i.e. "templates").  The view does not have to
> >> > render using a template though.
>
> >> > I had a diagram of this at one point, but can't get the darn thing to
> >> > open right now.  If anyone is interested in seeing a diagram let me
> >> > know and I will try to get it working and post one.
>
> >> What you are describing is closer to the Rails philosophy.  They're
> >> big on pushing stuff into models, even validation.  I've done it that
> >> way, and that works too.
>
> >> I think of it like a pie.  You can slice the pie in many ways.  Slice
> >> it however you like.
>
> >> That's one thing I like about Pylons.  It does make you use a class
> >> with methods, but it doesn't force you too much beyond that.  If you
> >> want to do something strange like put all your logic in models and
> >> then use string interpolation within your controllers you can.
> >> Whatever floats your boat ;)
>
> >> Happy Hacking!
> >> -jj
>
> >> --
> >> I, for one, welcome our new Facebook overlords!http://jjinux.blogspot.com/-
>
> --
> I, for one, welcome our new Facebook overlords!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
-~----------~----~----~----~------~----~------~--~---

Reply via email to