Hi Nicolas,
On Fri, 2007-03-30 at 14:53 +0000, Nicolas E. Lara G. wrote:
> That is true, there are always cases where name will collide but the
> disambiguation allows users a little more flexibility. I'm not saying
> it will avoid all collisions but it is a simple extension that will
> help most users (specially if you've already made your apps and views
> and when writing templates you realize that a name collides with a
> django contrib app, lets say, admin-add). If your names collide you
> have a choice. If, even using the application name, they still collide
> then you change them but it wouldn't hurt to allow users to use names
> like comments or admin-add and, if they include those contrib apps in
> their project, they can disambiguate them .
> Its not a critique of your proposal, I propose the same thing, its an
> extension.
I don't really think this is worth the extra confusion with name
resolution. You need unique names in any case because apps cannot rely
on the user using a particular extension. So the extension should be
just coded into the name itself. Just like with template names and app
names.
You say it wouldn't hurt to allow this, but it does hurt: if two
applications use the name "comments" on their URL and a template refers
to {% url comments %}, there is no guarantees about which URL will be
returned. Prefixing doesn't solve that problem because the template
doesn't know which prefix is being used.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
