search

matryer / xbar

Put the output from any script or program into your macOS Menu Bar (the BitBar reboot)
https://xbarapp.com
MIT License
17.59k stars 642 forks source link

[FEATURE REQUEST] Include plugins from common plugins folder in /Library/Application Support/xbar/plugins #697

Open MiqViq opened 3 years ago

MiqViq commented 3 years ago

Include plugins from common plugins folder in system level /Library/Application Support/xbar/plugins. This way user plugins and common plugins installed by system admin can all be utilized. For the security of user domain this probably should be enabled by an entry in application prefs, hopefully in standard prefs at co.xbarapp.app.plist. Like an array of plugin folders to scan:

<key>PluginDirsToInclude</key>
<array>
<string>/Library/Application Support/xbar/plugins</string>
</array>
matryer commented 3 years ago

Hey @MiqViq thanks for opening this.

Can you elaborate a little on the use case for this? Is a current workaround to just install the same plugins for each user or doesn't that address the use case?

MiqViq commented 3 years ago

BitBar had a preference key pluginsDirectory that was read by app, I used that as a forced location for plugins. But it would probably be better that user could install their own plugins and there would be a possibility for sysadmins to include their preferred plugin directories. I have a custom plugin that collects various info from the active system...very useful when our users are attaching reports with helpdesk service requests.

dAnjou commented 3 years ago

I guess it's a matter of convenience. Here's my personal situation: I have two user accounts on my machine, a private one and one for work. I use xbar on both and it would be quite convenient to have a common location for plugins that I wanna use with both users. As a developer I can obviously script my way around this, no big deal. So, I guess, it's a question of how convenient it should be for users to manage certain scenarios. Another use case I can come up with is that there's a collection of already installed but disabled plugins, and then user accounts can enable them on demand. I think these kinda use cases come up a lot when you wanna maintain a set of highly customized plugins as opposed to very generic plugins available in the public plugin browser.

shepazon commented 3 years ago

Duplicate of #661?