On Sat, 2008-05-24 at 16:21 -0700, Mike Orr wrote:
But then that gets into the issue of the site template. If the inner
app should be shown within the global header and sidebar, then you'd
have to inherit the site template -- which doesn't work well across
apps, plus you'd have to know
On Sun, May 25, 2008 at 11:49 AM, Cliff Wells [EMAIL PROTECTED] wrote:
On Sat, 2008-05-24 at 16:21 -0700, Mike Orr wrote:
But then that gets into the issue of the site template. If the inner
app should be shown within the global header and sidebar, then you'd
have to inherit the site
On Sun, 2008-05-25 at 15:27 -0700, Mike Orr wrote:
On Sun, May 25, 2008 at 11:49 AM, Cliff Wells [EMAIL PROTECTED] wrote:
On Sat, 2008-05-24 at 16:21 -0700, Mike Orr wrote:
But then that gets into the issue of the site template. If the inner
app should be shown within the global
Hello all,
I am new to the Python web-programming world and trying to decide on
frameworks. I was really impressed with Django, but ran into some
problems with IIS hosting. Since Pylons had really nice install
instructions for IIS, I started to take a look and I like the
philosophy. The WSGI
On Sat, May 24, 2008 at 6:37 AM, rcs_comp [EMAIL PROTECTED] wrote:
Hello all,
I am new to the Python web-programming world and trying to decide on
frameworks. I was really impressed with Django, but ran into some
problems with IIS hosting. Since Pylons had really nice install
instructions
Previously rcs_comp wrote:
However, I have run across a show stopper for me with Pylons unless I
have missed something in the documentation. Does Pylons support some
kind of module/plugin architecture that will allow me to develop plug-
in functionality across Pylons projects? What would be
how is this essentially different from tosco widgets? or just making a
python module that you put someplace in your python path for your pylons
app to find?
Jose
Wichert Akkerman wrote:
Previously rcs_comp wrote:
However, I have run across a show stopper for me with Pylons unless I
have
Previously Jose Galvez wrote:
how is this essentially different from tosco widgets? or just making a
python module that you put someplace in your python path for your pylons
app to find?
Because your add-ons may want to do things like add a new controller,
replace a template, etc.
Wichert.
On Sat, May 24, 2008 at 6:37 AM, rcs_comp [EMAIL PROTECTED] wrote:
Hello all,
I am new to the Python web-programming world and trying to decide on
frameworks. I was really impressed with Django, but ran into some
problems with IIS hosting. Since Pylons had really nice install
I *really* like how the modular approach can compartmentalize the
necessary templates and controllers.
I intensely dislike how the modular approach compartmentalizes the
routing and model. If something is affecting the routing model,
IMHO, it's not a plugin - its a standalone app.
At
I thought a bit more about nesting apps. The controller would be set up as:
from myinnerapp.config.middleware import make_app
OuterController = make_app(config[global_conf], full_stack=False,
**config[app_conf])
This would push another config onto of pylons.config, but since
Thank you all for your comments. Its clear though, for me, that
Pylons will not work for my projects. The need to develop components
that fit easily and natively into the larger application is a must.
Its disappointing though, b/c I was really liking the philosophy
behind Pylons. Keep up the
On May 24, 2008, at 6:37 AM, rcs_comp wrote:
For example, I would like to have a news, blog, and calendar
module that I can plug into different applications. The goal is to
have everything for the module contained in one subdirectory including
any configuration, routing, templates,
On May 24, 9:13 pm, Philip Jenvey [EMAIL PROTECTED] wrote:
If these are in fact separate applications, you can make each one its
own Pylons app. Then you might also have a common package of code
shared between all three (this would be a separate egg).
Then at deployment time you can combine
14 matches
Mail list logo
