=== duflu_ is now known as duflu === chihchun_afk is now known as chihchun === Trevinho_ is now known as Trevinho [09:16] duflu: why is render_surfaces a bad example? [09:17] anpok: Because it's a mashup of server and client. A dinosaur left from before we had working servers+clients [09:17] where is the client code? [09:18] the part that creates its own surfaces using the mir server api? [09:21] anpok: Sorry, I'm confusing it with something else. Other good reasons to throw away render_surfaces are (1) It sets surface rotation, which eventually will be dropped as a feature in favor of animations; and (2) It uses the buffer initialization hack (which I think nothing else does). So it's a very bad example, and therefore should not be touched other than to make it less bad :) [09:22] anpok: P.S. I won't see your messages unless you prefix "duflu:" [09:23] see as in hilights? [09:23] anpok: I mean on other desktops [09:23] duflu: or did you set font to background color [09:23] ah [09:23] anpok: Also render_surfaces is not a server. It doesn't support clients [09:23] It's also not a client... [09:25] So put simply, something that's neither a working server or a client is not good to put forward as an example of anything [09:25] hm it can open a socket file.. [09:26] but havent checked what happens with its clients.. [09:28] Nothing, it seems(!?) [09:28] anpok: Not surprising since render_surfaces was written before we had server/shell interfaces [09:28] Well, in a different forme [09:28] -e [09:32] bbl === marlinc_ is now known as Marlinc === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk