On 8/15/13, Ryan Ollos <[email protected]> wrote: > On Thu, Aug 15, 2013 at 4:42 PM, Olemis Lang <[email protected]> wrote: [...] >> >> Yes , there is a reason . AFAICR BH templates (e.g. milestones, ...) >> include widgets . >> > > I wasn't clear enough. Yes, I understand that BloodhoundTheme utilizes > widgets.
ok > What was the reason for making the widgets part of > BloodhoundDashboard rather than BloodhoundTheme? Historically the dashboard has been there even before it was decided to build BH theme on top of Bootstrap . Indeed the first layouts implemented in the dashboard were powered by YUI library . > I don't understand the > logic for making BloodhoundDashboard the "core" component. > > Besides , at present dashboard = widgets + layouts + reusability . Therefore it makes sense to develop core widgets + layouts in the dashboard for practical reason i.e. to make them available ootb . It's possible to write other different layouts not related with Bootstrap grid system at all . The same holds for widgets . And all those visual components may be reused all over across dashboards (i.e. inside layouts), Genshi templates , WikiFormatting , ... The scope of the dashboard plugin is too wide , even beyond BH boundaries . It's also a standalone package that has no (strong) coupling with theme customization . The very same nature of this plugin made it more suitable to host shared assets than any other . The initial versions of the theme (and even the subsequent proposals based on Bootstrap) did not rely upon widgets at all . That was an UX enhancement introduced later . The theme is not meant to be reusable . [...] -- Regards, Olemis - @olemislc
