Explore >> Select a destination
|
You are here 
|
rolle.design | ||
| | | | |
soatok.blog
|
|
| | | | | Another wave of Twitter users are jettisoning the social media website in favor of alternatives. Some are landing in the Fediverse (Mastodon and other ActivityPub-enabled software). Others are going to BlueSky. Some are just outright abandoning social media entirely, disillusioned by the entire concept. As someone working on design specifications to propose end-to-end encryption for... | |
| | | | |
adriano.fyi
|
|
| | | | | Mastodon While I'm in no way a Mastodon power user, I've really been enjoying the content that I get from my very limited Mastodon feed. I recently stopped consuming news from - hold on let's not call it news. I recently stopped consuming useless information from a site that I won't name. Everyone has those junk, just-for-fun sites they visit to blow off stream. You don't have to be proud of them, and it's fine that you visit them; every part of every day need not be productive. Anyway, I recently stoppe... | |
| | | | |
carlschwan.eu
|
|
| | | | | One design characteristic of our QtWidgets is that they contain a lot of frames and frames inside other frames. This worked well with Oxygen style and its skeuomorphism shadow, less so with Breeze. I first thought this was inheriten with QtWidgets and couldn't be fixed without much effort. But fortunately, after looking a bit into Qt source codes and in particular in the internals of QDockAreaLayout, I discovered that the engine to draw and style the built-in components of QtWidgets: QStyle has a QStyle::PE_IndicatorDockWidgetResizeHandle primitive which allows drawing separators between detachable docks and similarly there is QStyle::CE_Splitter to paint the separator between elements inside a QSplitter. This is huge because this means instead of drawing frames, we can render separator and then get rid of most of our frames in our apps. | |
| | | | |
adriano.fyi
|
|
| | | Fly.io Postgres failover fix (flyctl pg failover) This is a note to myself, meant to be succinct and helpful. I'm sharing it publicly to save others time. Most of the time Fly.io works as I expect it to, but occasionally there are edge cases that lack documentation, public announcements, or both. It's possible that at some point Fly.io announced a breaking change and I missed it, but the behavior I observed deserves more than an announcement or silently released documentation. | ||
