#249: Provide ticket page with breadcrumb
--------------------------+-----------------------
Reporter: gjm | Owner: gjm
Type: enhancement | Status: review
Priority: major | Milestone: Release 4
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-----------------------
Comment (by olemis):
Replying to [comment:6 rjollos]:
> Replying to [comment:5 olemis]:
> > [..] But mainly the goal is to move permission checks out of source
code and include it in the template .
>
> What are the motivations / advantages to performing the permissions
checks in the template rather than the source code?
Well in this case such change will allow us to reuse the same template
(i.e. bhtheme/templates/bh_path_ticket.html ) in another context if
necessary without the need for adding the same data in a different (...
completely unrelated ...) request handler .
That's something happening quite often in ''Trac'' , and is one of the
reasons that make widgets so useful (i.e. ubiquitous access to view + data
for web UI snippets ;)
> Are there some guidelines that are generally followed in the Trac /
Genshi community that motivated your suggested changes?
Some minutes of reasoning ?
;)
Beyond that I'm not aware of any such guidelines ... and if they exist
I've never used any , but I'd like to know of them . D'u have any
reference ?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/249#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
