hmmm... well ideally plugins and core would only load their assets when necessary. For instance, in core, we only load jQuery UI if we have some jQuery UI thing. There are many other places where we could pull more code out to be on-demand.
you mean ideally but not on reality, right? 😄
my idea was for example to enable plugins like...
-people viewing this topic, reactions, polls, etc only on desktop
The initial issue I have is it appears the proposition is swap next page button for top/bottom scroll, which breaks the logic of pagination navigation.
Perhaps another equally noble approach is merely a tweak on the current implementation, that would be to put the pagination nav bar on it's own floating menu that is always on top at the bottom of the screen.
In fact there is a very compelling argument which I have been thinking about a lot the last couple of weeks, that suggestion the bottom of the screen, especially for mobile devices, could be better utilised, rather than clustering everything to the top.
Typically our hand held devices finds more often our hands at the bottom area of the device, not usually the top.
So our fingers are already positional close to that area, meaning single hand operation/interaction with the UI is more comfortable.
Also anytime elements want to push the primary content off-side in real pixel terms or purely visual balance ratios, should be very carefully considered.
As plugin I'd like to be able to either get a list of activated plugins (maybe also version) or to send a request whether there is an activated plugin of given name (If you're aware of security issues 😛 )
I think you can call Plugins.isActive to see if a specific plugin is activated. Otherwise you can query db.getSetMembers('plugins:active', callback) for the actual list