df354fc0d4
Right now the indicator itself tracks all devices and connections, creates and destroys the corresponding menu items, matches them to a section and updates the connection/device arrays that are attached to the section. Sounds messy? It is slightly less effective to connect multiple handlers to the same NMClient, but let's assume that devices and connections aren't added/removed at 60 frames/s, and we can add some readabilty by moving the code into different classes that only have to care about the bits that are relevant to them. The VPN section is a good starting point, because its handling is already quite different from device sections. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2407> |
||
---|---|---|
.. | ||
accessibility.js | ||
autoRotate.js | ||
bluetooth.js | ||
brightness.js | ||
darkMode.js | ||
dwellClick.js | ||
keyboard.js | ||
location.js | ||
network.js | ||
nightLight.js | ||
powerProfiles.js | ||
remoteAccess.js | ||
rfkill.js | ||
system.js | ||
thunderbolt.js | ||
volume.js |