=== duflu_ is now known as duflu | ||
=== chihchun_afk is now known as chihchun | ||
=== Trevinho_ is now known as Trevinho | ||
anpok | duflu: why is render_surfaces a bad example? | 09:16 |
---|---|---|
duflu | anpok: Because it's a mashup of server and client. A dinosaur left from before we had working servers+clients | 09:17 |
anpok | where is the client code? | 09:17 |
anpok | the part that creates its own surfaces using the mir server api? | 09:18 |
duflu | 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:21 |
duflu | anpok: P.S. I won't see your messages unless you prefix "duflu:" | 09:22 |
anpok | see as in hilights? | 09:23 |
duflu | anpok: I mean on other desktops | 09:23 |
anpok | duflu: or did you set font to background color | 09:23 |
anpok | ah | 09:23 |
duflu | anpok: Also render_surfaces is not a server. It doesn't support clients | 09:23 |
duflu | It's also not a client... | 09:23 |
duflu | 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 |
anpok | hm it can open a socket file.. | 09:25 |
anpok | but havent checked what happens with its clients.. | 09:26 |
duflu | Nothing, it seems(!?) | 09:28 |
duflu | anpok: Not surprising since render_surfaces was written before we had server/shell interfaces | 09:28 |
duflu | Well, in a different forme | 09:28 |
duflu | -e | 09:28 |
anpok | bbl | 09:32 |
=== 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 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!