ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
lsd|2|2 has quit [Ping timeout: 480 seconds]
lsd|2 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
guru__ has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
JakeSays has joined #wayland
lsd|2|2 has joined #wayland
lsd|2 has quit [Read error: Connection reset by peer]
lsd|2|2 has quit []
garnacho has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
lsd|2 has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Guest9822 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest9863
Calandracas has quit [Remote host closed the connection]
privacy has quit [Remote host closed the connection]
sima has joined #wayland
mxz_ has joined #wayland
tzimmermann has joined #wayland
rasterman has joined #wayland
kts has joined #wayland
kts has quit []
kts has joined #wayland
leon-anavi has joined #wayland
<pq>
Calandracas, libexec_weston is installed in Weston's module directory, which is not part of normal ld search path. I guess you can consider it public with no stable ABI. The lib is not versioned. It is meant for weston plugins (as opposed to libweston plugins).
garnacho has joined #wayland
mvlad has joined #wayland
coldfeet has joined #wayland
coldfeet has quit [Remote host closed the connection]
<DodoGTA>
Why is the Wayland tarball signing key expired? When will emersion make a new one (and re-upload the Wayland release)?
<dwfreed>
renewing a key does not require a reupload of the tarball that was signed
iomari891 has quit [Read error: Connection reset by peer]
<pq>
DodoGTA, it's not expired for me. Did you try refreshing the key?
<DodoGTA>
pq: `gpg --refresh-keys` makes no difference
<pq>
using keys.openpgp.org?
<DodoGTA>
pq: I'm still using keyserver.ubuntu.com (I didn't have any issues with it before)
<dwfreed>
DodoGTA: I just uploaded the new sigs there, so refresh-keys should update your copy now
<dwfreed>
(the good and bad of the protocol being anybody can submit anything)
kts has joined #wayland
iomari891 has joined #wayland
nerdopolis has joined #wayland
fmuellner has joined #wayland
coldfeet has quit [Remote host closed the connection]
mohit81582263 has quit [Quit: mohit81582263]
mohit81582263 has joined #wayland
mohit81582263 has quit []
mohit81582263 has joined #wayland
<emersion>
I'm uploading to keys.openpgp.net and to WKD
iomari891 has quit [Ping timeout: 480 seconds]
<dwfreed>
emersion: keyserver.ubuntu.com is another good place to send keys, as it participates in the old federation, but doesn't have the performance issues that sks-keyserver has (runs hockeypuck instead)
cpli has quit [Remote host closed the connection]
geemili has quit [Remote host closed the connection]
abcdw has quit [Remote host closed the connection]
guacamolie has quit [Remote host closed the connection]
moses has quit [Remote host closed the connection]
kchibisov has quit [Remote host closed the connection]
cat has quit [Write error: connection closed]
mainiomano has quit [Remote host closed the connection]
dorkbutt has quit [Write error: connection closed]
kaathewise has quit [Write error: connection closed]
elibrokeit_ has quit [Remote host closed the connection]
fabiancodes has quit [Remote host closed the connection]
rosefromthedead has quit [Remote host closed the connection]
kennylevinsen has quit [Remote host closed the connection]
leon-p has quit [Remote host closed the connection]
atiltedtree has quit [Remote host closed the connection]
kuruczgy has quit [Remote host closed the connection]
nucfreq has quit [Remote host closed the connection]
ogromny has quit [Remote host closed the connection]
rpigott has quit [Remote host closed the connection]
jonesv has quit [Remote host closed the connection]
c7s has quit [Remote host closed the connection]
novakane has quit [Remote host closed the connection]
pitust has quit [Remote host closed the connection]
sumoon has quit [Remote host closed the connection]
tommybomb has quit [Remote host closed the connection]
dnkl has quit [Remote host closed the connection]
ifreund has quit [Remote host closed the connection]
kindablue has quit [Remote host closed the connection]
staceee has quit [Remote host closed the connection]
tkna has quit [Remote host closed the connection]
raghavgururajan has quit [Remote host closed the connection]
tsujp has quit [Remote host closed the connection]
kaathewise has joined #wayland
cpli has joined #wayland
geemili has joined #wayland
ogromny has joined #wayland
dorkbutt has joined #wayland
moses has joined #wayland
kuruczgy has joined #wayland
jonesv has joined #wayland
rpigott has joined #wayland
kchibisov has joined #wayland
mainiomano has joined #wayland
abcdw has joined #wayland
kindablue has joined #wayland
c7s has joined #wayland
staceee has joined #wayland
pitust has joined #wayland
cyrinux30 has quit []
cyrinux30 has joined #wayland
ifreund has joined #wayland
rosefromthedead has joined #wayland
sumoon has joined #wayland
systwi has quit [Ping timeout: 480 seconds]
elibrokeit_ has joined #wayland
guacamolie has joined #wayland
mripard has joined #wayland
<Calandracas>
pq thanks for the info. it is in fact a weston plugin, not a libweston plugin. I see that there was an issue opened for this topic, but there was no discussion: https://gitlab.freedesktop.org/wayland/weston/-/issues/451
novakane has joined #wayland
kts has quit [Ping timeout: 480 seconds]
dnkl has joined #wayland
systwi has joined #wayland
<pq>
Calandracas, oh, I had forgotten I wrote that issue. Nice that I still agree with myself. :-p
leon-p has joined #wayland
tsujp has joined #wayland
raghavgururajan has joined #wayland
cat has joined #wayland
tommybomb has joined #wayland
<pq>
Calandracas, you're the first one to ask about it, to my memory, so maybe make your case there?
raghavgururajan is now known as Guest9914
nucfreq has joined #wayland
<Calandracas>
yeah will do
atiltedtree has joined #wayland
<Calandracas>
I haven't seen much/any documentation at all about writing weston plugins, so I've been mostly figuring it out as I go :P
<pq>
chicken-and-egg, I guess
fabiancodes has joined #wayland
tkna has joined #wayland
kennylevinsen has joined #wayland
feaneron has joined #wayland
kts has joined #wayland
rgallaispou has joined #wayland
<Calandracas>
pq, added my thoughts to the issue. My main idea would be to modify weston.pc to link against libexec_weston. that pkg-config file already provides access to weston.h, which defines prototypes implemented in libexec_weston
<pq>
Calandracas, that's not even nearly enough, if the intention is to offer a stable, versioned library ABI.
rv1sr has joined #wayland
<pq>
Calandracas, btw. the old way of building weston plugins was to simply let unresolved symbols exist at build time. Those symbols used to be solved by the weston executable, before we wrapped it in a lib. We neglected to consider external plugins when introducing the lib.
KarenTheDorf has quit [Remote host closed the connection]
<pq>
Calandracas, very interesting to hear that you are doing a weston plugin, btw.
rgallaispou has quit [Read error: Connection reset by peer]
<Calandracas>
I want to use the colour managment features of weston, but the desktop-shell is too simplistic
<pq>
ooh, can you tell me more?
rgallaispou has joined #wayland
<Calandracas>
I want to be able to do things like load VCGT, for colour managed workflows. I also want to be able to do customizations not possible with the basic desktop shell. Things like keybindings, and "better" tiling. I figured it was better to use an existing compositor which does a decent job, rather than write a new one :P
eroc1990 has joined #wayland
<Calandracas>
I've only been working on it for 2~3 weeks, and its still largely a refactor (c++) of the default desktop shell. something interesting I have done, is the ability to use lua for handling hooks
<Calandracas>
Also though it would be interesting to use something other than wlroots
<Calandracas>
its just a hobby project, which i will release publicly when its in a better state
<pq>
Calandracas, certainly less work to start from an existing compositor. :-)
<Calandracas>
I origianlly started by writing a new libweston based compositor, but quickly realized simply making it a plugin would be much easier :P
rgallaispou has quit [Read error: Connection reset by peer]
<Calandracas>
I just like C++. Using lambdas to add signal handlers is simply much nicer
<pq>
Calandracas, VCGT would be used by simply loading an ICC profile for the output, but then Weston will also do color management based on it. Do you want to switch output profiles on the fly, or why do your own loading?
<pq>
well, the new color management framework will do that
<pq>
the old cms-static plugin literally loaded only the VCGT into KMS
<Calandracas>
even if it requires std::function and container_of hacks to for capturing lambdas to be possible
zamundaaa[m] has joined #wayland
<zamundaaa[m]>
Calandracas: have you looked at KWin for your needs? The combination of color management, a good shell, some tiling and C++ plugins sounds like an exact match
cmichael has joined #wayland
kts has quit [Ping timeout: 480 seconds]
<pq>
FYI, I'll be removing weston_output::get_gamma at some point as redundant and semantically conflicting with color management.
<pq>
err, set_gamma, of course
<Calandracas>
pq, I'm not super familiar with how colour managment works under the hood. I'm not switching profiles on the fly, simply loading an ICC profile i've created for my display. I've validated with argyllcms that the calibration is acurate and visually comparing it to my colour-checker passport
<pq>
Calandracas, you are following the X11 style of color management. cms-static plugin would do it for you, the little what a compositor needs to do.
<Calandracas>
Does weston apply colour transformations based on the icc profile (not just VCGT) ?
<pq>
Calandracas, in the Wayland style (the experimental color management feature), yes. With cms-static, no.
<pq>
Calandracas, Weston implements an experimental protocol where apps can tell the compositor what ICC profile the window adheres to. Currently only weston-image app does that.
<pq>
We're currently working towards parametric profile support as well in Weston, as that's needed for HDR.
<Calandracas>
hum this looks much better than the X11 style
<pq>
Thank you :-)
<pq>
That's not the usual reaction. :-p
<Calandracas>
i feel like the compositor dealing with this sort of thing is a lot more sane than depending on the applications themselves, most of which dont bother at all
<pq>
totally
kts has joined #wayland
<feaneron>
how's the progress with the protocols, btw?
<pq>
We needed HDR to make it painfully obvious, that leaving most of the apps unmanaged is not an option. :-D
<pq>
feaneron, maybe one big issue left (reference white luminance handling), otherwise still polishing and people doing implementations.
<Calandracas>
zamundaaa[m], I haven't tried kwin since KDE 5, and never used kde standalone. I had issues with occasional visual glitches and general instability. I've since switched to sway and really like it, but I should try kwin again now that KDE 6 is out.
<pq>
That's color-management extension. Color-representation is not as far in implementations AFAIK, but it's also simpler.
<feaneron>
cool cool, so i guess the kernel side bits have reached some sort of consensus then?
<pq>
feaneron, oh, the KMS side has a plan... and probably a long road to get there. Protocol or compositors do not depend on it, they can use GPU too.
<feaneron>
eh. i thought the color pipeline / color ops in kms was kind of a requirement for this
<Calandracas>
Luckily I personally don't need HDR. I only do photo editing, and most of my paid work will only ever be displayed on regular uncalibrated screens :P
<pq>
feaneron, that KMS stuff is required for off-loading some color operations to KMS, but compositors must be able to do the same on the GPU anyway, so it's not a show-stopper.
<Calandracas>
I'm also fortuneate to have a monitor with 99% DCI-P3 with Delta E < 2 even without VCGT loading
<feaneron>
well, it's great to hear that it's progressed, kudos for everyone involved