Groups (provided-by) selection is not sticky across "pages"

[kltm]

This is a new issue now that we have groups.

Essentially, as managers are local to a particular page (or even widget) right now in Noctua, groups selected one place may not be remembered somewhere else. For example, from the graph editor to a workbench.

There are two way to really approach this.

The first way would be to tie the groups back to barista, essentially having an API where a user agent could update what groups a particular token should inject. This might make app writing easier in some cases, but would cause issues with scripting and some kinds of clients (dead simple ones would be very hard to create). I don't like this, and dismissed something similar when first looking at groups.

More reasonable would be that the app/client remembers state if that's desired. Something like current groups could be passed as a session cookie, and then be used to move the widget off of its defaults. This does bring something like session into the system (bleh), but it's realistically either that or URL/POST/form stuff, which may be even more opaque.

The workaround for now is that users can set their "default" group by just having it first in their list. People probably won't change so often, so that might buy us a bit of time.

[kltm]

Thinking about this a bit more, one way to approach this would be to eat our own dog food and use the "generalized" mechanism from #316 and #283 to move in and out of workbenches and across pages. An advantage with that is that external clients and workbenches would function largely the same way.

[vanaukenk]

@kltm - I think this is fixed. Can we close?

[kltm]

I don't think this is technically fixed, at least generally. That said, I think it probably works as desired in most clients at this point, so might be safe to close out until (or if) there are complaints.