Re: Application, tempaltetags and namespace

[Mathieu Leduc-Hamel]

Cool, than from what i see it seems the namespacing will be more and
more implemented in Django in the future.

But as a good practice, it would be cool if it's finally happen to
force any templatetags to be used with namespace ? Cause if people can
use the old way to do things, we'll still have the same problem
related to conflicting names no?

On Mon, Sep 27, 2010 at 10:56 AM, Iván Raskovsky  wrote:
> On Mon, Sep 27, 2010 at 3:14 AM, Russell Keith-Magee
>  wrote:
>> On Mon, Sep 27, 2010 at 1:43 PM, Mathieu Leduc-Hamel  
>> wrote:
>>> Hi all,
>>>
>>> I'm curious to know if it's planned in the future to force the use of
>>> the complete name of the applications and the templatestags. I'll
>>> explain myself.
>> There are two tickets related to this problem:
>>
>> #2539: Namespacing for template tags
>> #12772: Loading by fully qualified path name
>>
>> Template tag namespacing has been accepted as an idea; it's just
>> waiting on a trunk-ready patch.
>>
>> Loading by fully qualified path is currently marked DDN; On principle,
>> the idea seems sound to me, but it requires more thought in terms of
>> how the new loading scheme will interact with existing code.
>
> I've proposed a solution[1] some time ago, where I also gathered all
> the discussions on the topic I could find. Sadly I got no feedback.
>    Iván
>
> [1] 
> http://groups.google.com/group/django-developers/browse_thread/thread/da9ed3a3116c546a/88d0d780a5e9d09f?lnk=gst=namespaces#88d0d780a5e9d09f
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
>
>



-- 
Mathieu Leduc-Hamel

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Application, tempaltetags and namespace

[Iván Raskovsky]

On Mon, Sep 27, 2010 at 3:14 AM, Russell Keith-Magee
 wrote:
> On Mon, Sep 27, 2010 at 1:43 PM, Mathieu Leduc-Hamel  
> wrote:
>> Hi all,
>>
>> I'm curious to know if it's planned in the future to force the use of
>> the complete name of the applications and the templatestags. I'll
>> explain myself.
> There are two tickets related to this problem:
>
> #2539: Namespacing for template tags
> #12772: Loading by fully qualified path name
>
> Template tag namespacing has been accepted as an idea; it's just
> waiting on a trunk-ready patch.
>
> Loading by fully qualified path is currently marked DDN; On principle,
> the idea seems sound to me, but it requires more thought in terms of
> how the new loading scheme will interact with existing code.

I've proposed a solution[1] some time ago, where I also gathered all
the discussions on the topic I could find. Sadly I got no feedback.
Iván

[1] 
http://groups.google.com/group/django-developers/browse_thread/thread/da9ed3a3116c546a/88d0d780a5e9d09f?lnk=gst=namespaces#88d0d780a5e9d09f

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Application, tempaltetags and namespace

[Eric Holscher]

Cody Soyland has also done some work on this in a reusable app, which might
be useful as a starting point:

http://github.com/codysoyland/django-smart-load-tag

Cheers,
Eric

-- 
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholscher.com

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Application, tempaltetags and namespace

[Russell Keith-Magee]

On Mon, Sep 27, 2010 at 1:43 PM, Mathieu Leduc-Hamel  wrote:
> Hi all,
>
> I'm curious to know if it's planned in the future to force the use of
> the complete name of the applications and the templatestags. I'll
> explain myself.
>
> Imagine you have an application called
>
> hello.world
>
> with the following structure:
>
> hello.world/
>  setup.py
>  hello/
>    world/
>     ...
>
> If you have an application called common and a templatags named
> featured_product, there's no way to it seems to force django to refer
> only to the complete name like that:
>
> hello.world.common
>
> and
>
> hello.world.common.featured_products
>
> it caused sometime some problems related to conflicting names and more
> than that, it means we are not completely explicit but magic.
>
> What do you think ?

There are two tickets related to this problem:

#2539: Namespacing for template tags
#12772: Loading by fully qualified path name

Template tag namespacing has been accepted as an idea; it's just
waiting on a trunk-ready patch.

Loading by fully qualified path is currently marked DDN; On principle,
the idea seems sound to me, but it requires more thought in terms of
how the new loading scheme will interact with existing code.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Application, tempaltetags and namespace

[Mathieu Leduc-Hamel]

Hi all,

I'm curious to know if it's planned in the future to force the use of
the complete name of the applications and the templatestags. I'll
explain myself.

Imagine you have an application called

hello.world

with the following structure:

hello.world/
  setup.py
  hello/
world/
 ...

If you have an application called common and a templatags named
featured_product, there's no way to it seems to force django to refer
only to the complete name like that:

hello.world.common

and

hello.world.common.featured_products

it caused sometime some problems related to conflicting names and more
than that, it means we are not completely explicit but magic.

What do you think ?

-- 
Mathieu Leduc-Hamel

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.