Closed meshy closed 10 years ago
I'm leaning toward url_tree
at the moment...
maybe dynamic_urls
?
Describe the functionality. One sentence.
Wow this is really hard.
A tree of urls with dynamic, customisable nodes at every branch and leaf.
Guess that means I should go for url_tree
...
A tree of urls with dynamic, customisable nodes at every branch and leaf.
This is a terrible description.
Thanks, @mattack108 that helped me focus
Indeed, terrible description ;-)
.
burls
?
In case the ref is needed http://dictionary.reference.com/browse/burl
hahaha :D
Core words:
url
route
node
Possible suffixes
_hierarchy
(eg url_hierarchy
)_tree
(eg url_tree
)s
(eg urls
)Possible prefixes
dynamic_
(eg dynamic_urls
)polymorphic_
(eg polymorphic_urls
)Perhaps some combination of the above?
(django-)polymorphic-url-tree
sounds like a package all of its own!
Any other suggestions?
If it makes sense to you, please merge
I'm not sure about this...starting to think that nodes
or url_nodes
would make more sense.
routes
does have a nice ring to it.
EDIT: Route
might be good for the model name too.
Right, I'm going to go with the name "routes". Closing this PR in favour of the branch I'm working on now.
Now in #40
"nav_tree" is starting to get on my nerves. Any suggestions?