bolha.us

0 posts0 participants0 posts today

Felix Palmen :freebsd: :c64:<a href="https://fosstodon.org/@peppe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@peppe</a> To be clear about that, I don't question the fact that <a href="https://mastodon.bsd.cafe/tags/X11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#X11</a> is full of old cruft that's mostly useless nowadays. It became more than clear to me while implementing my <a href="https://mastodon.bsd.cafe/tags/xmoji" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xmoji</a> tool, which uses almost exclusively <a href="https://mastodon.bsd.cafe/tags/XRender" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XRender</a> requests for rendering (an *extension* to X11, not part of the core protocol), because X core drawing requests are really designed for 1990es hardware, supporting color palettes with limited entries, but no alpha channel whatsoever. Similar goes for font support in the X11 core protocol, it's useless supporting only bitmap fonts with no antialiasing etc, so I use client-side rasterizing (with freetype) and XRender only for compositing the result. There are more silly examples, like the "Compound Text" encoding monstrosity, because the core design predates Unicode, and so on....In a nutshell, a major rework of what the X core protocol supports would be necessary.But then, you can *still* dislike a suggested solution. I think <a href="https://mastodon.bsd.cafe/tags/wayland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wayland</a> is taking the "simplicity" much too far, so now both compositors and clients (rendering windows) have to do the same stuff over and over again. It's a pointless exercise trying to create a wayland client without huge libraries (such as e.g. cairo for client-side rendering, better yet use a full-blown toolkit like Qt or GTK that already makes use of cairo), while this is perfectly possible for X.

Felix Palmen :freebsd: :c64:Well, I really like <a href="https://mastodon.bsd.cafe/tags/X11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#X11</a> (<a href="https://mastodon.bsd.cafe/tags/Xorg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xorg</a>) ... and my son loves <a href="https://mastodon.bsd.cafe/tags/PeppaPig" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PeppaPig</a>. Which gives me a stupid idea. I could write something called <a href="https://mastodon.bsd.cafe/tags/Xchicken" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xchicken</a>. Make some chicken lay some eggs with mouse clicks on some <a href="https://mastodon.bsd.cafe/tags/XRender" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XRender</a> surface.Rough roadmap: - Draw some chicken and eggs, probably as SVG? - Reuse code from <a href="https://mastodon.bsd.cafe/tags/Xmoji" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xmoji</a>, add special widget supporting some "layered canvas" - Implement game logic - Add sound? (Hm, gotta look into <a href="https://mastodon.bsd.cafe/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a> and maybe <a href="https://mastodon.bsd.cafe/tags/sndio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sndio</a>, cause <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> ... <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> weirdness maybe later) - ....?I'll probably never start though 🙈

Felix Palmen :freebsd: :c64:Here's a poll for <a href="https://mastodon.bsd.cafe/tags/X11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#X11</a> users about multi-screen setups. I'm interested in order to decide whether I should add *full* dpi-awareness to the v1.0 milestone of <a href="https://mastodon.bsd.cafe/tags/Xmoji" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xmoji</a>, after adding basic awareness (check just the "primary" screen on startup). Adding adaption to a different resolution at runtime would require quite some design changes, so I'd like to know whether it's something people need at all.Please boost for a better result, thanks! 😇What describes your <a href="https://mastodon.bsd.cafe/tags/Xorg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xorg</a> setup best?

Recent searches

Search options

Administered by:

Server stats:

#xmoji