08:37 <emersion> pq, does it really make sense to license EDIDs?

08:37 <pq> I have no idea, but they did so.

08:38 <pq> I don't know who own the EDID data. Probably the manufacturer? But everyone seems to assume that whoever extracts it, can license it. I did so too.

08:41 <pq> I suppose the easiest way is to just respect whatever license the project set up from where the data is taken.

08:41 <emersion> alright

08:41 <pq> that should raise the least amount of questions, to us at least

14:32 <soerenm> Hi, is there a way to get an issue posted on weston gitlab #625 looked at quicker? Should I contract somebody? I'd really appreciate your help.

14:39 <pq> soerenm, I took a quick peek, and didn't see anything I could comment about. It didn't look like Cr was waiting for any frame callback or such, if I read it right.

14:42 <soerenm> pq, thanks for looking at it, what could be the issue then? maybe in the graphics driver or chromium? The problem is I don't really have a clue how to debug/pin point the problem.

14:45 <ManMower> soerenm: I guess I'd try running a different app such as weston-simple-damage after the freeze has occurred. if it shows up and updates, then the drm driver likely hasn't fallen down a hole and stopped page flipping.

14:47 <ManMower> I'd also expect it to be simple to reproduce your problem without your protocol patch in place? it would be good to remove that from consideration entirely as a first step.

14:50 <soerenm> Restarting the only app that is running chromium also fixes the freezes but i though that triggers a reset or something. Will try it without my patch. The weird thing is that it does not reliably occur and not on every hardware.

23:16 <avnt> So, I have a general wayland question, I'm writing some software, and, ideally, I'd like to implement something similar to suckless's tabbed program for it, (for those not familiar, it uses provides a tab bar for xembed aware programs, so tabbing code is seperate from the application itself), but on wayland, I know that the xdg-foreign protocol exists (though it's currently in a unstable state), but I'd

23:16 <avnt> like to know the feasiable usage of it, like what compisitors support it, etc. Or would I be better off implementing such a thing as a seperate compositor meant to be nested in another wayland display?

23:34 <danieldg> avnt: xdg-foreign is more for dialogs than for actual embedding

23:35 <danieldg> but I'm not sure what xembed is anyway

23:35 <avnt> danieldg: yeah, looking at the API it seems like any actual embedding would be hacky at best

23:37 <danieldg> using a compositor that supports tabbed windows might be a better solution if you want tabs

23:41 <avnt> I already am one, it's more about development principles, I was planning on not implementing tabs as part of the base program, but having it be a seperate program entirely, but I guess I'll have to implement it more traditionally

23:43 <danieldg> you could have the compositor expose an api sufficient to create tabs with foreign toplevels (position them, hide them, draw a titlebar with your own surface)

23:45 <avnt> That's kind of what I thought, might just fork cage to do that tbh, it'd be a lot more flexible than the xembed-based tabbed too since it'd just be a compositor

23:47 <danieldg> I think river might be a better starting point? Assuming it's the one with a split window-layout engine

23:52 <avnt> danieldg: that might work, I'll have to see, but thanks for the suggestion