The current configuration dialog is a simple input() which is a glorified column selector. All it effectively does is allow the User to select which columns will be displayed within the Panel and provides example data. This was enough to get it off the ground, but it could be more. The columns are entirely configuration driven; the backing object looks something like this:
Which means any token property can actually be referenced in here (although it's also rather entwined with the Basic properties; we should fix that). In addition, the order of this JSON map defines the order of the columns. The GM may want to add new token properties and/or arrange the columns to suit their needs. Further, they may also want to disable the roll link by unselecting the 'checked' attribute for a column. Super industrious GMs may even decide to roll their own rollers.
For that last GM, we might as well give them a free-form text field with the JSON object and tell them to go nuts. For the other GMs, we could provided an enhanced editor with more configuration ability, defining what order columns are in, allowing them to create (or remove columns), and define if a column is a "checked" (has a roller link).
The current configuration dialog is a simple input() which is a glorified column selector. All it effectively does is allow the User to select which columns will be displayed within the Panel and provides example data. This was enough to get it off the ground, but it could be more. The columns are entirely configuration driven; the backing object looks something like this:
Which means any token property can actually be referenced in here (although it's also rather entwined with the Basic properties; we should fix that). In addition, the order of this JSON map defines the order of the columns. The GM may want to add new token properties and/or arrange the columns to suit their needs. Further, they may also want to disable the roll link by unselecting the 'checked' attribute for a column. Super industrious GMs may even decide to roll their own rollers.
For that last GM, we might as well give them a free-form text field with the JSON object and tell them to go nuts. For the other GMs, we could provided an enhanced editor with more configuration ability, defining what order columns are in, allowing them to create (or remove columns), and define if a column is a "checked" (has a roller link).