On Wed, 2007-02-14 at 17:00 +0100, Frank Tegtmeyer wrote:
> "James Bennett" <[EMAIL PROTECTED]> writes:
>
> > you had two apps named "payment", it wouldn't just affect templates --
>
> Right. Thanks for all the answers.
>
> My next question is about parameters for applications: how does one do
"James Bennett" <[EMAIL PROTECTED]> writes:
> you had two apps named "payment", it wouldn't just affect templates --
Right. Thanks for all the answers.
My next question is about parameters for applications: how does one do
that in Django?
Say I want to have two different photo galleries, both
On 2/14/07, Frank Tegtmeyer <[EMAIL PROTECTED]> wrote:
> except that there is no central registry for application names, right?
> So one could have two applications called "payment" where one would be
> for credit cards, the other for anonymous payment. What if he needs
> both and they are made by
Hi Geert,
> - Non name clash
except that there is no central registry for application names, right?
So one could have two applications called "payment" where one would be
for credit cards, the other for anonymous payment. What if he needs
both and they are made by someone else?
Ok, not very like
Hi Frank,
On 14 Feb 2007, at 11:45, Frank Tegtmeyer wrote:
>
> Hi,
>
> I ave a question about the philosophy behind the template loading
> mechanism (my background is Zope2 with the "local overrides global"
> approach).
> If I understand it right, all the (standard) template loaders form a
> nam
Hi,
I ave a question about the philosophy behind the template loading
mechanism (my background is Zope2 with the "local overrides global"
approach).
If I understand it right, all the (standard) template loaders form a
namespace for templates that is used for all applications within a
site:
app1
6 matches
Mail list logo
