Porting SpotOn to Safari. #16
Unanswered
SenpaiHunters
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, sadly, there Is not many people who will see this nor be able to help, but I'll place it here.
I am looking to port SpotOn (and subsequently all SpotOn extensions) to Safari.
However, I can't as I use Chrome APIs but as porting to safari it would require changing, for example,
when porting the SpotOn extension:
• The SpotOn extension uses the
chrome.storage
API to store and retrieve user preferences. This API is not available in Safari, so you will need to find an alternative way to store preferences, such as using thelocalStorage
API.• The SpotOn extension uses the
chrome.runtime
API to communicate between the background script and the content script. This API is not available in Safari, so you will need to use a different method to communicate between the scripts, such as the safari.extension
API.• The SpotOn extension uses the
chrome.tabs
API to interact with the current tab. This API is not available in Safari, so you will need to use the safari.application.activeBrowserWindow.activeTab
property to interact with the current tab.• The SpotOn extension modifies the DOM of the Spotify web player to add custom functionality. You will need to modify the code to work with the structure of the DOM in the Safari version of the web player.
• The SpotOn extension uses some third-party libraries, such as jQuery and Bootstrap. You will need to include these libraries in the Safari extension project and modify the code to work with them.
These are just some of the issues I faced, so I have just blankly said it would be supported, although, WebOS apps like Orion would allow Chrome Extensions, which Is what I use to test SpotOn on WebOS.
All the code needed is on my GitHub, if you would like to transfer it over, let me know!
Beta Was this translation helpful? Give feedback.
All reactions