...
- What if a Fluid component is using a particular framework in its implementation, what are the consequences for an integrator?
- An integrator is using an existing framework, what happens if the Fluid component is using the same or different framework?
- In the case of the same framework, the component may be using a custom build or custom framework styles (over-ridden in css file) - what happens in this framework-framework interaction?
To explore answers to these questions, the following 4 use cases are possible:
- Integrator is not using any framework but chooses to use our component.
- Integrator adopts and uses the framework used by our component.
- Integrator is using the same framework as our component, but with different customizations (essentially two versions of the same framework exists on the same page).
- Integrator is using a different framework than the one used by our component.
To attempt to figure out the consequences of use cases 3 and 4, a custom version of Foundation was created that is scoped to a unique classname called ".inf-foundation". The idea is to mimic the scenario where our component, contained in an element with the classname "inf-infusion", is being added to an existing application . one with Bootstrap, and another with Foundation.
- Namespaced to
.inf-foundation, headings pink: app-pink.css (customized Foundation with pink header text colour) - Namespaced to
.inf-foundation, headings blue: app-blue.css (customized Foundation with blue header text colour)