Options specific to RAD containers.
Options specific to RAD containers.
A map of RAD components to combine under common control in a container. Each entry is a key (which will be the ID of the element) and a RAD component (typically a report).
{:a SalesReport
:b OtherReport
:c Statistic}
Note that you can use the same component class more than once, which can allow for simultaneous (but perhaps differently shaped) views of the same data.
A map of RAD components to combine under common control in a container. Each entry is a key (which will be the ID of the element) and a RAD component (typically a report). ``` {:a SalesReport :b OtherReport :c Statistic} ``` Note that you can use the same component class more than once, which can allow for simultaneous (but perhaps differently shaped) views of the same data.
A vector of vectors of IDs (or description maps) of components in the container.
Each inner vector will allocate a grid row.
co/children {:a ReportA
:b WidgetA
:c WidgetB}
co/layout [[:a]
[:b :c]]
The layout
values can be maps instead of keywords, in which case the :id
key will designate which child the
layout parameters go with. Your UI render plugin can then define any number of additional things you can decorate
the entry with. For example, the grid system might allow for component sizing:
co/layout [[{:id :a :width 3}]
[{:id :b :width 2} {:id :c :width 1}]]
This is optional. The default is to simply place the reports one after another, top to bottom on the screen.
Additional layout configuration may be available in your container renderer.
A vector of vectors of IDs (or description maps) of components in the container. Each inner vector will allocate a grid row. ``` co/children {:a ReportA :b WidgetA :c WidgetB} co/layout [[:a] [:b :c]] ``` The `layout` values can be maps instead of keywords, in which case the `:id` key will designate which child the layout parameters go with. Your UI render plugin can then define any number of additional things you can decorate the entry with. For example, the grid system might allow for component sizing: ``` co/layout [[{:id :a :width 3}] [{:id :b :width 2} {:id :c :width 1}]] ``` This is optional. The default is to simply place the reports one after another, top to bottom on the screen. Additional layout configuration may be available in your container renderer.
A keyword (hint) of what layout style to use. Support relies on the underlying rendering plugin.
A keyword (hint) of what layout style to use. Support relies on the underlying rendering plugin.
A string that will be used as this container's path element in the routing tree. Must be unique among siblings. If you do not define this option, then the container will not behave properly as a route target in dynamic routing.
A string that will be used as this container's path element in the routing tree. Must be unique among siblings. If you do not define this option, then the container will not behave properly as a route target in dynamic routing.
A string of (fn [this] element-or-string)
that will be used as this container's title.
A string of `(fn [this] element-or-string)` that will be used as this container's title.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close