Perhaps cherrypy._cputil.get_object_trail() is what you are looking for.

On 2/17/06, Randall <[EMAIL PROTECTED]> wrote:
>
> I'm not following this.  What I was looking for in the first case is
> something like this:
>
> url = tg.requested_url
> url_parts = url.split('/')
> # construct the navigation bar from url_parts
>
> # but that won't work with restful style access, so what I really want
> to do is know where I am on the controller hiearchy.  So I might have
> controllers RootController -> EfileController -> UploadController
> linked.  If UploadController is currently being accessed, I'd like to
> know that and (by introspection) produce a navigation menu with a link
> for each controller.  In this case, it would look like this:
>
> home > efile > upload
>
> Each item in the "breadcrumb" navigation list would reference a
> controller.  I'd like to do this without having to seperately define a
> navigation list.  One thought that did occur to me is that I could
> inspect all controllers on startup to build a hierarchy list.  Then
> when I figure out which controller is being accessed, I can reference
> this list to build the menu.  Where is a good place to store this list
> so that I can reference it later?
>
> The actual navigation links will be constructed in the master.kid
> template.  So if I can figure out how to determine which controller is
> being called from the template, I think I can do this.  Is it possible
> to know which controller is being called from a template?  I say I'm
> doing this in a template.  I may actually put this code in a module and
> call it from the template to create the menu.
>
>
>
>


--
cheers
    elvelind grandin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to