I'm also interested in the patterns used by other developers to
section their application into distinct packages. Recently i have been
working with drupal and magento, and I must say i really appreciate
how these project separate functionality into packages. For a large
project this really is a must have, not only for reuse but also
maintainability and developer sanity. Keep it small, keep it simple.

So how does pyramids help in this respect? I don't see how the object
dispatch mechanism really makes a difference here (been there done
that with cherrypy & turbogears). The primary issues is how one wire's
together the different api's. Eg. a mini-app requires a user model
which has a permissions attribute. How does this mini-app publish this
requirement? And how can I wire up an app that supplies this api up
with this mini-app?

Secondly, how can i hook up parts of one mini-app into an another app.
For example, an e-commerce site might have 'productpage' showing
product details. This would be part of the catalog app. Yet i would
also like to show a mini/cart in the template. This mini-cart is part
of the shoppingcart app. I don't want shoppingcart logic in my
productpage controller, so how do i integrate these apps. Django´s
signals seems an interesting solution yet also obscure. I got a gut
feeling the problem can be simply solved with plain polymorphism and
ducktyping. We don´t need to create a new dispatch mechanism, it´s
already build into the language.

Honestly, I have been fighting with these issues in various MVC
frameworks for years and haven't found a satisfactory pattern.
Currently i'm trying to grok how magento does this with the Zend
framework. At the moment it still seems overly complex to me, to much
configuration. But that might be naivety on my side. I´m really
looking forward how other developers are handling this.

On 10 jan, 08:37, Marius Gedminas <[email protected]> wrote:
> ...
> I get the impression that the answer is "want modular applications?
> Switch to Pyramid."
> ...

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
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