scope: is pugl only for plugins? #3
Description
Most of us are using pugl for plugins. Precious few toolkits are appropriate for this task, so we of course want to maintain suitability for that use case. Scope issues like DnD become less important if we all agree on this over-arching concept of whether we want to add features that make pugl more useful for desktop applications as well as plugins. I think the primary trade-off is API simplicity vs full feature set (aka bloat?).
I personally think we'd be ok adding features to make pugl more powerful even if they aren't typically used in plugins. We do need to take it feature by feature for certain, but I like the creed that iff its more than a one-off use case and non-trivial to implement separately then it should be added.