mmo-chart-config

the plots, in the order they are offered

where the values come from

the easings MMO.core.transitions knows

the palettes the server knows (\MMO\core\classes\aDataController::COLORS)

what <mmo-chart> uses when its configuration says nothing

the attributes of a chart this element writes, by option

The chart this element was read from, if any.

Type

?HTMLElement

Take everything a chart shows: its source, its type and its options.

Take the statistics an address counts, if it is the server's statistics route.

Give a chart what is configured here. A chart read from an address keeps its options as attributes, which is what the next read of the address takes them from (and what a dashboard saves).

Whether a list of series holds points ([x, y], {x, y}) rather than values.

One point as the grid edits it.

What the data looks like, whatever its source: what the type and the options are checked against.

Why a plot cannot draw this data.

Work out what the current type and source allow, turn off what they do not, and redraw the preview.

Turn off the comparisons the data cannot make (refresh).

Something was edited: refresh once the burst of events it fires is over.

Everything configured, as a chart takes it: its attributes, and either its configuration (typed values) or the address it reads them from. An option the type does not read, or the source cannot keep, is left out.

The server's statistics route, with every setting in its query.

The series of the statistics that count something: named, and filtered.

Whether a filter keeps everything: no condition, or an empty group.

Pick the source of the values.

Why a source cannot be picked here.

Pick the plot.

Count the entities, or sum one of their fields.

The date the current period is counted from.

Read what the server can count, once.

Count another collection: its fields are not the last one's, so the filters and fields start over.

The schema of the collection counted, which the fields and the filters are picked from.

Add a series to the statistics.

Draw the series of the statistics: a name and a filter each.

Fill the controls the template cannot bind: the lists of the server, the paths, the filters, the grids.

Bind one <mmo-path> or <mmo-filter> to a property of this element, on the collection's schema.

Draw the strips of sources and types once: their state follows the data (updateStrips).

Mark the source and the type picked, and turn off, with their reason, those that cannot be.

List what was turned off or changed, and why.

Draw the grid of values: one row per series, one column per label. Every cell writes to values as it is typed; adding or removing a row or a column redraws it.

Draw the points, one block per series.

How many colours the chart uses: one per label for a pie, one per series otherwise.

The colours of the first count series (or labels), the palette repeated when it is shorter.

Draw one swatch per series (per label for a pie).

Back to the chart's own palette.

Redraw the preview once the edits pause: a chart read from the server is read again each time.

Give the preview what is configured. A chart that read an address is replaced rather than given values, so an answer still on its way cannot overwrite them.

The markup (and the script) that builds the same chart.

A value as javascript, the way a person writes it: a series, a point or a list of labels on one line.

Show the code of what is configured.

Copy the code to the clipboard.

set by itself when the element is too narrow to show the preview beside the form

.narrow