Sure. There may not be a need for a "project" dir when you have only
one project running. It is cleaner to simply have /admin/blog/entry/add
or even /admin/entry/add. Also, you may want your model to technically
describe the object accurately, but present it to the user in a more
readable way, or
oggie rob wrote:
> Would it be possible to override the url location within the
> modules/classes? My only concern is that sometimes the project, module
> and/or class name are not an appropriate part of a URL, and would be
> nice to easily override. (This of course assumes that URLs are part of
>
Would it be possible to override the url location within the
modules/classes? My only concern is that sometimes the project, module
and/or class name are not an appropriate part of a URL, and would be
nice to easily override. (This of course assumes that URLs are part of
the UI, which I feel is tr
On 12/14/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Or maybe get rid of the "models" cruft:
>
> /admin/myproject/blog/entry/add/
+1
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
"Adrian Holovaty" <[EMAIL PROTECTED]> wrote
in message
news:[EMAIL PROTECTED]
>Or substitute slashes for dots:
>
> /admin/myproject/blog/models/entry/add/
I like this better. Slashes are better than dots.
Thanks,
Eugene
I think Cherry is more instance-y, Quixote was more package-based but
with v.2 is now more explicit with "Directory" classes that define
traversals. I think. I don't use either in real life.
Just thought I'd mention them as references that might be applicable --
even if they're too much for this
ToddG wrote:
> I don't know if there's a mathematical formula for this, but it's
> looking like all ideas are approaching an object traversal/resolution
> scenario like in: Zope, Quixote, CherryPy, etc. Perhaps one of those
> can offer some direction.
>
>
I think most of those work on an instan
I don't know if there's a mathematical formula for this, but it's
looking like all ideas are approaching an object traversal/resolution
scenario like in: Zope, Quixote, CherryPy, etc. Perhaps one of those
can offer some direction.
On Dec 14, 2005, at 9:15 PM, Adrian Holovaty wrote:
Or maybe get rid of the "models" cruft:
/admin/myproject/blog/entry/add/
This one's my favorite.
Double points if /admin/myproject/ shows a list of models under
myproject (and /myproject/blog/ shows all the ones under
myproject.blo
Adrian Holovaty wrote:
> In the magic-removal branch (see
> http://code.djangoproject.com/wiki/RemovingTheMagic), we're removing
> the magic model modules, which means the concept of "module_name" goes
> away. This creates a bunch of interesting new issues, because some
> parts in Django use modul
On 12/15/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Or maybe get rid of the "models" cruft:
>
> /admin/myproject/blog/entry/add/
+1 for being the most readable and less cumbersome.
--
Jeroen Ruigrok van der Werven
On 15 Dec 2005, at 3:59, Adrian Holovaty wrote:
Clearly we would want to avoid that. Before importing, it could check
that the module is in INSTALLED_APPS.
By going with /admin/project/app/model/add/ stick with more normal
looking urls, you can do the checking at quite a fine-grained level
On 12/14/05, Ian Holsman <[EMAIL PROTECTED]> wrote:
> my other concern with putting the python path into the URL is would it
> allow nasty thing
> like
> admin/init.me.and.i.format.your.hard_disk/
> ?
> and other weird easter eggs which a unsuspecting admin doesn't realize
> is on his machine?
Cl
On 12/15/05, Afternoon <[EMAIL PROTECTED]> wrote:
>
>
> On 15 Dec 2005, at 3:15, Adrian Holovaty wrote:
>
> > /admin/myproject/blog/entry/add/
>
> +1, most readable, most compact, most guessable.
>
> > The problem with "/admin/myproject.blog.models.entry/", though, is I'm
> > not sure it's pos
my 2c's
add the model name as a parameter to the view so that the developer
can stick the admin screens directly into their application
ie
/forum/ calls my view
/forum/add would call the admin add view with myproject.model.forum as
a parmeter
and so on.
but to answer your specific question I wo
On 15 Dec 2005, at 3:15, Adrian Holovaty wrote:
/admin/myproject/blog/entry/add/
+1, most readable, most compact, most guessable.
The problem with "/admin/myproject.blog.models.entry/", though, is I'm
not sure it's possible to get the Python path *to* an object. For
example, given a mo
16 matches
Mail list logo
