mastodon.green is one of the many independent Mastodon servers you can use to participate in the fediverse.
Plant trees while you use Mastodon. A server originally for people in the EU, but now open for anyone in the world

Administered by:

Server stats:

1.2K
active users

#tray

0 posts0 participants0 posts today

This afternoon I was getting #takeout at a #drivethrough. I was asked if I wanted a #bag for my order and declined.

At the window. after paying, I was given my meal on a #TRAY. A metal (or plastic colored to look like metal) tray , I kid you not.

And before anyone tells me I sound like #HankHill #Yellingatclouds, I KNOW I sound like Hank Hill (or #GrandpaSimpson). But I can't be the only one who sees a flaw in ditching paper bags, only to replace them with plastic or metal trays.

Can I?

This is now kind of a dev microblog concerning #Xmoji. I'm kind of stalled, now that version 0.7 seems reasonably stable and portable (I see there's a #nix pkg, unfortunately outdated, and a #NetBSD #pkgsrc port, I will deliver #FreeBSD *soon*).

It misses a few convenience features my previous #qXmoji had: save/restore the window size, optionally enforce a single instance, offer a #tray icon. I'll add all of that, seems straight-forward, for the tray icon I'll only implement the old #X11 spec based on #Xembed and if some desktop environment insists on only supporting the newer standard based on #dbus, well, screw that. Too much complexity, sorry.

The real issue is #localization (#l10n), specifically "just" translations. I still have no good concept for that. With #Qt, it was a no-brainer to also use Qt's mechanism. Without a toolkit, obvious choices would be either #POSIX message catalogs, or #GNU #gettext. The latter is much more convenient, but pulls in extra deps (with #GPL/#LGPL foo). Both have in common that they only operate on char* ... 8bit encodings. I have many of my texts stored as char32_t (#Unicode UCS-4 or #UTF32, difference doesn't matter much here). I could redesign that to base everything on #UTF8, but I'm a bit reluctant ... why add more runtime conversions?

I seriously think about coming up with my own tooling. But then, how far should I jump? Should I really try to parse my own source (using LLVM's #libclang for example)? Or should I hardcode tables with identifiers for all translatable texts?

I'll sleep on that a few more nights I guess....

#xcb #development thoughts:

One of the features I'd like to add to #Xmoji is a "system #tray icon". I know these aren't "en vogue" any more, but I like the concept a lot for an application you'll typically leave running and only use from time to time, which is likely a usage pattern for an "#emoji #keyboard".

So, I found a spec based on #XEMBED, X selections and client messages (therefore, pure X inter-client communication), I think I can implement that! 👍
specifications.freedesktop.org

Digging deeper, I found there's a successor called #SNI and the spec above is considered "legacy" (after only 20 years, hehe) 🤨. SNI is based on #dbus. Oh damn ... it's not that I particularly hate dbus, it probably makes a lot of sense for complex desktop environments, but I really want to keep #Xmoji "plain #X11". I'll just use the old spec. At least I found #KDE seems to have a compatibility service: xembed-sni-proxy. No idea about Gnome. But then, screw it.

specifications.freedesktop.orgSystem Tray Protocol Specification1 Overview # The system tray is an application running on a given X screen that can display small icons provided by running applications. Windows XP calls this feature the notification area. [1] Inspired by KDE, this specification uses the term system tray. From a UI standpoint, the system tray is n…

Just launched a delightful new design: a tray with an enchanting engraved labyrinth pattern!

Dive into the maze of details here: printables.com/model/775239

Crafted to cater to all, these trays range in sizes from a cozy 100mm up to a generous 350mm, complemented by three choices of side thickness to ensure there's a perfect match for both small and large printers alike.

Dive into this labyrinthine adventure and let your prints take you on a journey!

Just can't decide if this new design should hit the spotlight: it's a plate/tray, but with a twist! I've crafted it with patterned ribs that form a fully functional labyrinth.

Size: About 140x140mm, printed on Prusa XL using a 0.4mm nozzle, and the 3DJake ecoPLA Ultra-Satin Purple gives it that perfect finish.

What do you think? It is worth to generate and publish models files for it?

#TIL: Apparently there is a maximum of 10 issues that a single pull request can reference on #GitHub.

@purejava easily exceeds this limit with his PR, adding #appindicator support to @cryptomator, solving plenty of issues caused by the dreadful #AWT #tray icons.

It took some time and effort but we're finally there. We are so grateful for this contribution and I am sure, our #linux users will be as well! Thank you! 💚

github.com/cryptomator/cryptom