Use number fields and lists of values for the parameters of the chartjs and tableToChartJS macros

The chartjs and tableToChartJS macros take the chart type, the source table, a column and sizes in plain text fields of the Edit Macro dialog, so the user has to know the Chart.js identifiers and the ids of the page, and a wrong value draws nothing.

The macros to change, with the file where most of the fix is done:

• chartjs: WebHome.xml.
• tableToChartJS: TableToChartJS.xml.

The main problems:

• The chart type is a short fixed list, which a wiki macro cannot declare, and would gain from a preview of each type.
• The table is the id of a table of the same page, and the data set label a column of that table, so their values depend on the page and on another field.
• The width and height are numbers of pixels declared as strings.

Depends on

Most of these fields cannot be offered before these generic changes, each giving the macro the means to declare the expected value:

• XWIKI-25182, which gives a number input to the parameters of a numeric type.
• XWIKI-25197, which lets a wiki macro parameter declare its minimum and maximum.
• XWIKI-23045, which lets a parameter get its values from a provider, with or without custom values.
• XWIKI-25180, which lets a parameter depend on another one, whose value its list of values follows.

KOs covered

Impact found on macro fluidity

These 6 KOs come from the WYSIWYG usability audit of the macros, under the criterion C4 input-assistance of its usability criteria. The page of each macro, linked in the table, has the full notes and the steps to reproduce. Fixing them means changing the declaration of the parameters in the macro definitions.