jasbu.blogg.se

Of the views as tabs in Chrome, except we show more than one at a Work on their features without fear of breaking someone else's view,Įach view is sandboxed in their own "browser" (I guess you can think For all of our feature teams to be able to Important for another change in our desktop client.Ī lot of our desktop UI these days is actually using Chromium Embeddedįramework (CEF), which basically means our views are powered by Returns player state) and JSON for passing data around. Some obviousīenefits are versioned interfaces (example: GET sp://player/v1/main Payloads, allowing for a much more flexible architecture. Of the client communicate with a module using arbitrary paths and It works in a way not too dissimilar from HTTP. We call the interface layer to these modules "Cosmos", and That their logic could theoretically be implemented in other These modules are still C++ but are self-contained enough This has meant breaking outĬertain features, such as playback control, into their own separate Getting a richer feature set, we need to ensure that "core" doesn'tīecome "a little bit of everything". Spotify becomes available on more and more platforms as well as Post gotten condensed, with functionality split out into modules. The core of all our clients is C++, but that core has since Rasmus's