Repository navigation
Help Popup module evolution #103
Description
This PR OCA/web#417
propose a way to aggregate help content by model or action
Help popup module
Pros
- several modules can put their doc content on the same object with the same field
- end users can be see contextual doc of several modules
- end users can add/replace some parts of the doc
- documentation can be aggregated for a whole menu (Sales, Accounting ...) and be extended to the whole ERP.
Cons / Todo
- help fields (which store content) are in ir.model and ir.act_window: easy but not fine for security rules ?
- no way to reuse customized parts of doc provided by endusers
- no use of qweb then doc inherits impossible: only add some parts.
- no interaction between modules in knowledge repos and this module (changes approval, etc.)
Reacted by Daniel Reis
Activity
max3903 commentedon Oct 11, 2016
Related issues:
As discussed, I propose:
hbrunn commentedon Mar 28, 2017
I'm busy with
help_popup_document_page, which should do most of the above[ADD] help_popup_document_page
SalahAdDin commentedon Dec 11, 2018
@hbrunn looks great!!!
[ADD] help_popup_document_page
etobella commentedon Jul 15, 2020
Is this still relevant? @bealdav
bealdav commentedon Jul 15, 2020
I never took time to port my initial module. I don't know if it so useful for a large public.
It's the problem with OCA we don't know who use our modules.
github-actions commentedon Aug 14, 2022
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.