Levanslokks pretty neat
Levans* looks pretty neat
Levans(and it's in Rust :D)
LevansCould be a fun project to make a greeter for it using Smithay :-°
xa0Hey all. Is fireplace useable still? I'm very pleased with this non-wlroots ecosystem
xa0I think I'll be betting on you guys
xa0Yeah, I saw that too
drakulix > <@frony0:matrix.org> Hey all. Is fireplace useable still? I'm very pleased with this non-wlroots ecosystem
No really at this point. The codebase is outdated and won't be continued until smithay is in a state, I would consider for daily use.
drakulixBut it is getting there
xa0I'd help if I could, I really want to use wayland, but I refuse to use anything sircmpwn has made. So that's upsetting
xa0Theres no tiling wms around yet that aren't wlroots spawn
ifreund on Freenodethat seems like a rather extreem standpoint
xa0(my limitation is mostly time and energy)
xa0It seems extreme to some. To me and others, it makes perfect sense
ifreund on Freenodewell, rootston is deprecated, we have tinywl now :D
Levansoh well, looks like I'm not very up to date
xa0To be fair, I don't exactly need much, I basically only ever have emacs and firefox opwn
xa0Maybe anvil's enough…
Levansanvil is not tiling though, and its window management is very minimal
LevansYeah, ostly our focus for now is to get all the heavy plumbing of the graphical pipeline stable in Smithay, before turning to more higher-level functions like window management and such.
LevansThough if you're interested in helping with bringing some more window management in anvil... ;)
xa0Fair enough, though!
kchibisov on Freenodefor an object.
kchibisov on FreenodeThe 0 ID is reserved to represent a null or non-existant object.
kchibisov on FreenodeSo in theory when it comes to summoning dead proxies it could use id 0?
Levans... Maybe ? Though I don't think that'd change anything for wayland-client users, given the Proxy is dead anyway.
Levans(the notion of "dead Proxy" of wayland-client is something that has no equivalent in libwayland-client, btw)
kchibisov on FreenodeI know, but how it handles collision and id reuse?
LevansThere is no collision. A dead
Proxyis just a rust object representing a wayland object that once existed but no longer exists. You cannot do anything with it.
LevansIf you try to make a request from it, wayland-client will just swallow it into the void, and send nothing to the server.
kchibisov on FreenodeI mean after you've summoned dead proxy.
LevansThe dead proxy does not prevent at all its ID to be reused by the protocol later
kchibisov on Freenodeyeah, so what will happen here? Like I have dead proxy leaving in id map, and then I get new object with the same id as that dead proxy.
kchibisov on Freenodeit should replace the dead proxy, right?
LevansThe dead proxy is not in the ID map. That's its whole point.
kchibisov on FreenodeOh, so it'll just go to the void, I see.
LevansNot completely sure what you mean by "it" in this sentence, though
LevansIt gives you access to a
surfaceAttributesstruct, that contains the whole state that has been commited by the client