On 12 juin, 04:12, "Shannon -jj Behrens" <[EMAIL PROTECTED]> wrote:
(snip)
> I agree with Ben. Having classes with methods has all sorts of OO
> benefits. Consider, you can implement __getattr__ and do all sorts of
> cool tricks. It's also nice to share a bunch of code and data via
> self. If
> I saw a Java MVC that's totally different. The view knows about the
> model and actively puts things into it and takes things out of it.
> The controller does not know much about the model (if I remember
> right). The database is also distinct from the model; the view talks
> to the database
On Wed, Jun 11, 2008 at 3:14 PM, Ben Bangert <[EMAIL PROTECTED]> wrote:
> On Jun 11, 2008, at 1:10 PM, Karlo Lozovina 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 diff
On Thu, Jun 12, 2008 at 8:44 AM, Alberto Valverde <[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
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
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
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
-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
Al
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 mu
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, i
>
> 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 controll
On Jun 11, 2008, at 7:12 PM, Shannon -jj Behrens wrote:
MVC is a cargo cult ;)
http://jjinux.blogspot.com/2005/04/mvc-cargo-cult.html
Regardless of the original meaning in the context of Smalltalk, the
terminology does have a fairly easy to understand and very common
interpretation (most
On Wed, Jun 11, 2008 at 3:14 PM, Ben Bangert <[EMAIL PROTECTED]> wrote:
> On Jun 11, 2008, at 1:10 PM, Karlo Lozovina 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 diff
On Jun 11, 2008, at 1:10 PM, Karlo Lozovina 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 m
14 matches
Mail list logo
