| Include Page |
|---|
| Infusion14:sneak peek warningInfusion14: |
|---|
| sneak peek warning |
|---|
|
| Div |
|---|
|
| Panel |
|---|
| borderColor | #ccc |
|---|
| bgColor | #fff |
|---|
| title | On This Page |
|---|
| borderStyle | solid |
|---|
|
| Table of Contents |
|---|
| minLevel | 2 |
|---|
maxLevel | 5| Wiki Markup |
|---|
{div:class=floatRight}
{panel:title= On This Page| borderStyle=solid| borderColor=#ccc| bgColor=#fff}
{toc:minLevel=2|maxLevel=5}
{panel}
{div} |
| Excerpt |
|---|
Components or functions in general may have different requirements depending on the context in which they are operating. For example, a subcomponent might operate differently when running on a production server versus when testing locally off the file system, and differently still when operating in the context of automated tests. In a more fine-grained way, a component may behave differently when operating in a browser with different capabilities, or on behalf of a user who has expressed particular needs or preferences. |
...
If an array of context names is provided, they are conceptually ANDed. The IoC system will attempt to find registered demands that most closely match the context parameter. So, for example:
| Code Block |
|---|
| javascript | javascript |
|---|
| bgColor | white |
|---|
| borderStyle | none |
|---|
| javascript |
|---|
|
fluid.demands("subcomp", "comp2", demandspec1);
fluid.demands("subcomp", ["comp2", "testEnv"], demandspec2);
|
...