Explore >> Select a destination
|
You are here 
|
www.thepollyproject.org | ||
| | | | |
nathan.torkington.com
|
|
| | | | | ||
| | | | |
sintraworks.github.io
|
|
| | | | | Recently I started studying Ray Wenderlich's tutorial book RxSwift. Early on, the book suggests using Rx as an alternative to delegates and their associated protocols. I though, great, but, for the task at hand, that's a rather heavy handed solution. (Yes, I know it is just an example designed to teach me the basics.) So I tried to imagine how I could achieve something similar to the functionality they built for their initial examples, without the overhead of importing a big library like RxSwift. | |
| | | | |
gabevenberg.com
|
|
| | | | | The other day, I stumbled upon RMK, a keyboard firmware written in Rust. Given that my Ferris Sweep has a Ferris the crab logo on the silkscreen, it felt only fitting that I flash it with RMK. Since I first built it, my Ferris Sweep has been running QMK, a very mature C-based keyboard firmware. QMK is a great project, and doing basic keymaps for an already-supported keyboard is straightforward and well-documented. However if you are designing your own keyboard, or want to use certain advanced QMK features, you wont be able to use QMKs JSON-based 'data driven' features. Instead, you will have to use its C macro based configuration, which can be daunting and may require understanding QMKs complex build system. | |
| | | | |
damienbod.com
|
|
| | | The article looks at managing user delegated access tokens for a downstream API in an ASP.NET Core web application. There are many ways of implementing this, all with advantages and disadvantages. The tokens are requested from an OpenID Connect server using the recommended standards. In this blog, the UI access token from the application authentication... | ||
