Skip to content
This repository was archived by the owner on Oct 15, 2025. It is now read-only.

Conversation

@BlueManCZ
Copy link

This is a rewrite of the old and abandoned Spotify extension.

Spotify plugin allows user to search and play tracks, add them to the queue and select a client.

@ManuelSchneid3r ManuelSchneid3r force-pushed the main branch 2 times, most recently from dc00273 to 807adc4 Compare November 18, 2024 13:22
@martinengelke
Copy link

Maybe we could be more general and also include e.g. Soundcloud (I like independent music), so it could be preferable a music player extension? At least for macOS it could just work with the built-in player, which is most of the time fine enough for me.

@BlueManCZ
Copy link
Author

That's an interesting idea. I was considering controlling other platforms as well (e.g., Tidal, Roon). However, if you scroll through the code, you'll notice that much of it (spotifyApiClient.cpp, configwidget.ui) is highly platform-specific, which limits what we can do. While it might be possible to generalize this into an overgrown plugin with different APIs for various services, it would be much easier to handle this as separate plugins, allowing users to choose the ones they want to use.

it could just work with the built-in player

I don't think the built-in SoundCloud player allows programmatic searching for tracks, which is the main goal of this extension. Implementing SoundCloud's /tracks API endpoint would likely be required to achieve this.

@martinengelke
Copy link

just an idea... :)
did not deep into it enough, I thought the API Requests could look or processed quite similarly and we can built a basic music player, capable of more then one music service?

@BlueManCZ BlueManCZ mentioned this pull request Nov 28, 2024
@ManuelSchneid3r ManuelSchneid3r force-pushed the main branch 4 times, most recently from 8409da8 to f539cc8 Compare March 5, 2025 12:58
@ManuelSchneid3r
Copy link
Member

hey @BlueManCZ i restructured the repository such that each plugin is in its own repo. id be glad to finally test your plugin without having to touch my permanently dirty working directory

@BlueManCZ
Copy link
Author

Right, I see. So what would be the next step? Should I create a repository for the plugin myself, or will you create an empty one so I can make a PR there?

@ManuelSchneid3r
Copy link
Member

Should I create a repository for the plugin myself,

yes, create a public repo in your account that i can add as a submodule here

@BlueManCZ
Copy link
Author

Sure, created the repo here: https://github.com/BlueManCZ/albert-plugin-spotify

@ManuelSchneid3r
Copy link
Member

closing this to finally archive this repo. Id be glad if you want to join here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants