On 8/15/13, Ryan Ollos <[email protected]> wrote: > On Thu, Aug 15, 2013 at 4:42 PM, Olemis Lang <[email protected]> wrote: >> On 8/15/13, Ryan Ollos <[email protected]> wrote: [...] >> > For new developers this will make it more challenging >> > to understand the structure of the project, and in general having >> > dependencies between the plugins will reduce the ability for users to >> > configure their installations by deactivating Components they aren't >> > interested in. >> > >> >> If dashboard is disabled how come components and activity widgets will >> be rendered ? The require the underlying dashboard / widgets >> architecture . That's always been the point . >> ;) >> > > My statement was based on this observation - If I want to disable the > dashboard, I would set bhdashboard.web_ui.* = disabled. Once that change is > made, the relations widget on the ticket page displays: > > Error Dashboard data is missing . Is bhdashboard.web_ui.DashboardModule > component disabled? >
Oh ! Now I c ... That's another subject afaict . In order to support disabling /dashboard without breaking (theme) widgets (IMO) we should split web_ui module component ... or maybe provide widgets logic in api system component . -- Regards, Olemis - @olemislc
