-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow static contribution of status bar items #167874
Comments
Other options for the LiveShare team to consider:
|
I would suggest something even simpler which is a just a menu identifier for the status bar. So, LS would contribute an ordinary command and place it into that special menu. That's similar to the |
We have extension samples which are * activated for the same reason https://github.com/microsoft/vscode-extension-samples/blob/76c78944b51a35bf30a248fe45fe99684f9e26dc/basic-multi-root-sample/package.json#L20 |
View container in the activity bar will be visible only if there are active views in it. I suspect in this case there are no active views in this view container. When the extension got activated, views in this view containers are also enabled by some when contexts set on these views. I also assume these views are contributed the same extension and has when contexts. |
Revisiting this item. As per @sandy081's comment we were able to get the Live Share icon to show up in the activity bar pre- activation which is great! We're also able to add the Share & Join options to the remote indicator menu pre-activation. Those are still quite hidden though. Looking at telemetry, approx. 42% of our collaboration sessions are initiated via the Are you open to allowing static contribution of status bar items (pre-activation)? If this isn't desirable for all extensions perhaps for approved extensions only? |
@jramsay is LS's status bar contribution in any way dynamic or always the same label, icon, command etc? I am asking because I wonder if it's enough to have a status bar menu to which commands can be registered (analog to other menus) or if we need the full deal with a dedicated contribution point, an activation event etc pp |
@jrieken: it is dynamic in that the I think as long as we can keep the current behavior where the |
We would also find it useful to have the ability to contribute static statusbar items without needing to have the extension active on startup |
@a-stewart can you share more about your use-case for this API? |
Hi, Sorry for not replying to this - I missed the comment notification. The proposed API looks ideal - one thing I would ask though is if it would be possible to add a when clause to the status bar item to configure when it is shown. I guess something to consider would be how this interacts with |
git graph extension also face the same issue: mhutchie/vscode-git-graph#377 |
Problem
The LiveShare extension is currently
*
activated. I believe the main reason for this is so they can contribute aLive Share
button in the status barThis is currently only possible to do in code
Proposal
Add a new contribution point that lets extensions contribute a static item (potentially with a
when
clause) to the status bar. Clicking on this item should trigger a command, which can then activate the full extension/cc @isidorn @bamurtaugh @jramsay @joyceerhl
The text was updated successfully, but these errors were encountered: