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.
