Hi Julien, everyone! I suggest we move forward in this project. First things first, we need to integrate bootstrap into the framework. So I think the following steps are to be done next:
1- copy the resources to the images component (CSS, JS, and Fonts) and include them in the base CommonScreens.xml 2- Repeat step 1 above to SASS (thank god Bootstrap move away from LESS) 3- Ensure that our jQuery dependencies are adequately met We can then have a few test screens to make sure everything is working more or less! Julien, can we proceed with the above suggested? Do we need to open the JIRA first, and who should do that? Taher Alkhateeb. On Fri, Oct 24, 2014 at 9:07 AM, Adrian Crum < adrian.c...@sandglass-software.com> wrote: > It is important to understand the screen widget architecture: > > Widget Models -> Renderer -> FreeMarker Macros -> HTML + CSS (or CSV, > or...) > > The Widget Models and Renderer are output agnostic - they don't "know" > what type of output is being generated. So those artifacts do not need to > be changed to support Bootstrap. > > The only things that need to be changed to support Bootstrap are the > FreeMarker macros - so that they output Bootstrap HTML + CSS instead of the > current OFBiz-specific HTML + CSS. > > You can still use the visual themes functionality, but they will be > different themes - since the HTML being styled is completely different. > > Adrian Crum > Sandglass Software > www.sandglass-software.com > > On 10/23/2014 10:29 PM, Florient wrote: > >> Hi Julien, Adrian, Community, >> >> Le 23/10/2014 08:46, Adrian Crum a écrit : >> >>> On 10/23/2014 7:12 AM, Julien NICOLAS wrote: >>> >>>> For this point I suggest to work on this way : Create tool to delegate >>>> HTML widget structure (and other structure) into theme framework. >>>> To be clear, I suggest to not integrate bootstrap only but modify the >>>> framework to allow any other HTML/CSS frameworks integration without >>>> modifying the OFBiz framework. >>>> But we'll do it for bootstrap first. >>>> >>> >>> >>> You don't need to modify the framework. The screen widgets allow you >>> to substitute alternate macros for the rendering engine. See >>> widget.properties. >>> >>> >>> Adrian Crum >>> >> >> correct me if I'm wrong, >> but if we use widget's properties, we will not be able to provide a >> hot-swap between them, except by creating new output type. >> It sounds like duplicate each actual view-map definition using 'screen' >> type to the new one, as the CSV rendering. >> or am I missing the way that widget allow us to substitute macros >> rendering ? >> >> Regards, >> Florient. >> >> >> >> >>
