#522: Implement Bloodhound Relation widget on the ticket page
--------------------------+-----------------------
Reporter: andrej | Owner: matevzb
Type: enhancement | Status: closed
Priority: major | Milestone: Release 6
Component: relations | Version:
Resolution: fixed | Keywords:
--------------------------+-----------------------
Comment (by olemis):
Replying to [comment:6 rjollos]:
> Should the relations widget template (`widget_relations.html`) reside in
`bloodhound_dashboard/bhdashboard/widgets/templates`? I would have guessed
the location for it to be
`bloodhound_relations/bhrelations/widgets/templates` or
`bloodhound_relations/bhrelations/templates` since the corresponding
Python source code is in
`bloodhound_relations/bhrelations/widgets/relations.py`. It seems odd to
have the template and Python source in different packages.
>
The real question is : Will relations template be reused by other
components in Bloodhound core . If the answer is **yes** then it belongs
in dashboard plugin , otherwise better distribute it with relations
plugin.
The short history about this subject is that e.g. grid template is used in
report and query UI besides corresponding widgets . The same happens with
''widget_alert.html'' et al (and the most recent instance that I recall is
items list proposed for #563). Once upon a time it was agreed that shared
assets would be distributed with dashboard plugin , but it's not a
straitjacket. Generic templates can be classified as shared assets.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/522#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
