manage capabilites ui #1862

New Issue

Closed

opened 2013-09-12 14:16:18 +00:00 by j · 2 comments

j commented

2013-09-12 14:16:18 +00:00

Owner

at some point we might want an admin ui to mange capabilities

rlx added the

general

label 2013-09-12 14:16:18 +00:00

rlx added this to the 13.03 milestone 2013-09-12 14:16:18 +00:00

0x2620 was assigned by rlx

2013-09-12 14:16:18 +00:00

rlx added the

normal

enhancement

labels 2013-09-12 14:16:18 +00:00

rlx commented

2013-09-14 08:06:58 +00:00

Owner

This would be the first time we'd be writing to config.*.jsonc -- seems a bit arbitrary to do that for capabilities.

We may want a full-fledged "Configure pan.do/ra" dialog -- this would help find config bugs, and allow a proper implementation of changing UI settings via # URLs. We'd need an abstract description of the config though: names, descriptions, default and allowed values (types, but also ranges, one-or-more-of-many, including configurable many), requires restart, removable ("title" item key isn't), editable (user.ui.videoPoints wouldn't be), etc. for every key/value pair, and forms with tons of / . Doable, but a lot of work...

This would be the first time we'd be writing to config.*.jsonc -- seems a bit arbitrary to do that for capabilities. We may want a full-fledged "Configure pan.do/ra" dialog -- this would help find config bugs, and allow a proper implementation of changing UI settings via # URLs. We'd need an abstract description of the config though: names, descriptions, default and allowed values (types, but also ranges, one-or-more-of-many, including configurable many), requires restart, removable ("title" item key isn't), editable (user.ui.videoPoints wouldn't be), etc. for every key/value pair, and forms with tons of <ArrayInputs> / <ObjectArrayInputs>. Doable, but a lot of work...

rlx commented

2013-09-24 15:40:57 +00:00

Owner

Marking wontfix. For config dialog, see #1883.

rlx added the

wontfix

label 2013-09-24 15:40:57 +00:00

rlx closed this issue

2013-09-24 15:40:57 +00:00