https://blogs.kde.org/2024/09/12/plasma-wayland-protocols-1.14.0/
Plasma Wayland Protocls 1.14.0 is now available for packaging.
This adds features needed for the Plasma 6.2 beta.
*URL:* https://download.kde.org/stable/plasma-wayland-protocols/
*SHA256
Hi,
In 5.27.0 wayland-protocols becomes an optional dependency for
plasma-workspace because it was added after the hard freeze date. But
enabling wayland-protocols build dependency can make XEmbed on Wayland
work properly.
See also:
https://invent.kde.org/plasma/plasma-workspace
On Wed, Sep 1, 2021 at 10:28 AM Ben Cooksley wrote:
>
> On Wed, Sep 1, 2021 at 9:56 AM David Edmundson
> wrote:
>>
>> Bumping this thread to say, this (a bump of plasma-wayland-protocols)
>> has just happened again and I imagine we have two more landing this
>&g
On Wed, Sep 1, 2021 at 9:56 AM David Edmundson
wrote:
> Bumping this thread to say, this (a bump of plasma-wayland-protocols)
> has just happened again and I imagine we have two more landing this
> week.
>
> This probably will result in broken CI for a few days, which is far
&g
implementations makes for a much easier integration.
I'll be happy to press the right buttons if someone tells me they'd
merged to the protocols repository.
Aleix
On Tue, Aug 31, 2021 at 11:56 PM David Edmundson
wrote:
>
> Bumping this thread to say, this (a bump of plasma-wayland-proto
Bumping this thread to say, this (a bump of plasma-wayland-protocols)
has just happened again and I imagine we have two more landing this
week.
This probably will result in broken CI for a few days, which is far
from ideal, but it's why we have our feature freeze early.
David
ning stable version of
> > plasma, it may cause issues on developer machines.
> >
> > If you experience startup issues with plasma on wayland, in
> particular
> > plasma not starting at all, please recompile the following projects:
> >
> > * pl
recompile the following projects:
* plasma-wayland-protocols
* kwayland
* kwayland-server
* kwin
* plasma-workspace
I'm afraid the CI system may disagree with you regarding the impact on
stable branches, please see
https://build.kde.org/view/Failing/job/Plasma/job/kwayland/
recompile the following projects:
* plasma-wayland-protocols
* kwayland
* kwayland-server
* kwin
* plasma-workspace
I'm afraid the CI system may disagree with you regarding the impact on
stable branches, please see
https://build.kde.org/view/Failing/job/Plasma/job/kwayland/
ange won't affect users running stable version of
> plasma, it may cause issues on developer machines.
>
> If you experience startup issues with plasma on wayland, in particular
> plasma not starting at all, please recompile the following projects:
>
> * plasma-wayland-protocol
hines.
If you experience startup issues with plasma on wayland, in particular
plasma not starting at all, please recompile the following projects:
* plasma-wayland-protocols
* kwayland
* kwayland-server
* kwin
* plasma-workspace
Sorry for the inconvenience,
Vlad
mfg Tobias
On Mon, 5 Apr 2021 at 20:38, Vlad Zahorodnii wrote:
Hi,
The v1.2.0 release of plasma-wayland-protocols has wrong project version
in CMakeLists.txt, which causes packaging issues in KWayland 5.81.
v1.2.1 patch release fixes that problem.
Source can be found here:
https://download
> The v1.2.0 release of plasma-wayland-protocols has wrong project version
> in CMakeLists.txt, which causes packaging issues in KWayland 5.81.
> v1.2.1 patch release fixes that problem.
>
> Source can be found here:
> https://download.kde.org/stable/plasma-wayland-protocols/plasma-w
Hi,
The v1.2.0 release of plasma-wayland-protocols has wrong project version
in CMakeLists.txt, which causes packaging issues in KWayland 5.81.
v1.2.1 patch release fixes that problem.
Source can be found here:
https://download.kde.org/stable/plasma-wayland-protocols/plasma-wayland-protocols
adding Wayland protocol implementation public interfaces in
the cases that will be shared among several users.
This then includes 2 new repositories:
kdesupport/plasma-wayland-protocols
kde/workspace/kwayland-server
The first should be released independently whenever we have a new
protocol, the
2014-08-20 8:14 GMT+02:00 Martin Gräßlin :
>
> at least KWin internal they will still have a winId - at least as long as
> Toplevel has not been refactored. I don't know how it looks on the outside
> world, or what Qt provides when accessing QWindow::winId() on platform
> wayland.
Basically the pl
On Wednesday 20 August 2014 21:10:58 Eike Hein wrote:
> Hi,
>
> to start another subtopic: Do we have startup notifications
> on our radar?
>
> http://standards.freedesktop.org/startup-notification-spec/startup-notificat
> ion-latest.txt
> http://www.freedesktop.org/wiki/Software/startup-notifica
On Thursday 21 August 2014 23:48:38 Ivan Čukić wrote:
> Ok, SLC BOF scheduled for 10th Sept, 10:30-12:30. Part for wayland and
> internals talk, part for UI and other things.
>
> > like to know internals of the windowing system
>
> IDs are not really internals - we need to be able to identify win
Ok, SLC BOF scheduled for 10th Sept, 10:30-12:30. Part for wayland and
internals talk, part for UI and other things.
> like to know internals of the windowing system
IDs are not really internals - we need to be able to identify windows
outside of kwin (task manager, slc, ... any client of a publi
On Wednesday 20 August 2014 21:10:58 Eike Hein wrote:
> Hi,
>
> to start another subtopic: Do we have startup notifications
> on our radar?
>
> http://standards.freedesktop.org/startup-notification-spec/startup-notificat
> ion-latest.txt
> http://www.freedesktop.org/wiki/Software/startup-notifica
Hi,
to start another subtopic: Do we have startup notifications
on our radar?
http://standards.freedesktop.org/startup-notification-spec/startup-notification-latest.txt
http://www.freedesktop.org/wiki/Software/startup-notification/
KDE has an implementation of this that is used by libtaskmanag
On Wednesday 20 August 2014 16:41:23 Ivan Čukić wrote:
> > Personally I don't understand why kamd needs to know the internal Id of a
> > window. Is this really needed or could it solved differently (e.g. using
> > additional interface/requests which kwin then forwards to kamd)? If not
> > it's abou
> Personally I don't understand why kamd needs to know the internal Id of a
> window. Is this really needed or could it solved differently (e.g. using
> additional interface/requests which kwin then forwards to kamd)? If not it's
> about time that we express the need for a global id in the xdg_she
On Wednesday 20 August 2014 10:26:22 Marco Martin wrote:
> On Wednesday 20 August 2014, Ivan Čukić wrote:
> > So, either the window needs to know its id, or it needs to be able to
> > resolve the id through kwin and kwin passes the info to kamd, or
> > something.
>
> so, in a nutter-shell, QWindow
> so, in a nutter-shell,
:)
> QWindow::winId to be the same as the id that KWin
> would store internally i guess
Yes, that would be perfect.
--
Cheerio,
Ivan
KDE, ivan.cukic at kde.org, http://ivan.fomentgroup.org/
gpg key id: 850B6F76, keyserver.pgp.com
__
On Wednesday 20 August 2014, Ivan Čukić wrote:
> So, either the window needs to know its id, or it needs to be able to
> resolve the id through kwin and kwin passes the info to kamd, or
> something.
so, in a nutter-shell, QWindow::winId to be the same as the id that KWin would
store internally i
> > I'm not familiar with kactivities but a grep for winId reveals that it
> > is used by ResourceInstancePrivate::registerResourceEvent, but I don't
> > understand what does it need to communicate to the compositor.
I don't know whether this should be communicated to the compositor or what,
jus
On Tuesday 19 August 2014 17:00:48 you wrote:
> 2014-08-18 9:37 GMT+02:00 Ivan Čukić :
> > On Monday 18 August 2014 09:22:03 Martin Gräßlin wrote:
> >> On Monday 18 August 2014 09:02:07 Pier Luigi wrote:
> >> > > Activities should probably be also exposed to the kf5_window
> >> > > interface?
> >>
2014-08-18 9:37 GMT+02:00 Ivan Čukić :
> On Monday 18 August 2014 09:22:03 Martin Gräßlin wrote:
>> On Monday 18 August 2014 09:02:07 Pier Luigi wrote:
>> > > Activities should probably be also exposed to the kf5_window interface?
>> >
>> > What do you need for activities?
>>
>> @Ivan: that falls i
2014-08-15 10:45 GMT+02:00 Marco Martin :
> On Friday 15 August 2014, Martin Gräßlin wrote:
>
>> > [1] https://github.com/plfiorini/protocols
>> > [2]
>> > http://lists.freedesktop.org/archives/wayland-devel/2014-July/016056.html
>>
>> after going through all interfaces I think we can kill the wind
On Tuesday 19 August 2014 11:05:58 Martin Gräßlin wrote:
> On Tuesday 19 August 2014 10:59:09 Pier Luigi Fiorini wrote:
> > On Friday 15 August 2014 10:42:28 Marco Martin wrote:
> > > On Friday 15 August 2014, Martin Gräßlin wrote:
> > > > another general note: I'm not sure about exposing "kf5" in
On Tuesday 19 August 2014 11:23:11 you wrote:
> On Tuesday 19 August 2014 11:03:48 Martin Gräßlin wrote:
> > On Tuesday 19 August 2014 10:51:43 Pier Luigi Fiorini wrote:
> > > *) ksmserver is a Wayland client that binds kf5_shell
> > > *) ksmserver is asked to lock (via loginctl, plasmoid or contex
On Tuesday 19 August 2014 11:03:48 Martin Gräßlin wrote:
> On Tuesday 19 August 2014 10:51:43 Pier Luigi Fiorini wrote:
> >
> > *) ksmserver is a Wayland client that binds kf5_shell
> > *) ksmserver is asked to lock (via loginctl, plasmoid or context menu)
> > *) ksmserver calls the kf5_shell.lock
On Friday 15 August 2014 07:51:09 Martin Gräßlin wrote:
> dashboard_surface is something I would move from the windoweffects.xml to
> the shell.xml. It's more a side-effect that it ended in window effects.
Done
___
Plasma-devel mailing list
Plasma-devel
On Tuesday 19 August 2014 10:59:09 Pier Luigi Fiorini wrote:
> On Friday 15 August 2014 10:42:28 Marco Martin wrote:
> > On Friday 15 August 2014, Martin Gräßlin wrote:
> > > another general note: I'm not sure about exposing "kf5" in the interface
> > > names. It has nothing to do with frameworks a
On Tuesday 19 August 2014 10:51:43 Pier Luigi Fiorini wrote:
> On Monday 18 August 2014 18:22:42 Martin Gräßlin wrote:
> > On Monday 18 August 2014 17:48:03 Pier Luigi wrote:
> > > 2014-08-15 7:35 GMT+02:00 Martin Gräßlin :
> > > > * concerning the lock/unlock: I would like to have the lock way bet
On Friday 15 August 2014 10:42:28 Marco Martin wrote:
> On Friday 15 August 2014, Martin Gräßlin wrote:
> > another general note: I'm not sure about exposing "kf5" in the interface
> > names. It has nothing to do with frameworks and I don't expect the
> > interface name to change once we introduce
On Monday 18 August 2014 18:22:42 Martin Gräßlin wrote:
> On Monday 18 August 2014 17:48:03 Pier Luigi wrote:
> > 2014-08-15 7:35 GMT+02:00 Martin Gräßlin :
> > > * concerning the lock/unlock: I would like to have the lock way better
> > > integrated in KWin. That is KWin should be responsible for
On Monday 18 August 2014 17:48:03 Pier Luigi wrote:
> 2014-08-15 7:35 GMT+02:00 Martin Gräßlin :
> > On Thursday 14 August 2014 21:05:01 Marco Martin wrote:
> >> On Thursday 14 August 2014, Pier Luigi wrote:
> >> > Hi,
> >> >
> >> > Just
2014-08-18 17:48 GMT+02:00 Pier Luigi :
> 2014-08-15 7:35 GMT+02:00 Martin Gräßlin :
>> some more thoughts:
>> * set_overlay_role: should we make the name more explicit:
>> set_on_screen_display_role?
>
> I like set_overlay_role (well the overlay enum value for
> set_surface_role now), less verbose
2014-08-15 7:35 GMT+02:00 Martin Gräßlin :
> On Thursday 14 August 2014 21:05:01 Marco Martin wrote:
>> On Thursday 14 August 2014, Pier Luigi wrote:
>> > Hi,
>> >
>> > Just pushed some initial draft of the Wayland protocols on Github [1]
>> >
On Monday 18 August 2014 17:21:55 Pier Luigi wrote:
> 2014-08-15 7:25 GMT+02:00 Martin Gräßlin :
> > On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
> >> Hi,
> >>
> >> Just pushed some initial draft of the Wayland protocols on Github [1]
> >>
2014-08-15 7:25 GMT+02:00 Martin Gräßlin :
> On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
>> Hi,
>>
>> Just pushed some initial draft of the Wayland protocols on Github [1]
>>
>> I need people with knowledge of KF5 and plasmashell to comment it and
>>
On Monday 18 August 2014 09:22:03 Martin Gräßlin wrote:
> On Monday 18 August 2014 09:02:07 Pier Luigi wrote:
> > > Activities should probably be also exposed to the kf5_window interface?
> >
> > What do you need for activities?
>
> @Ivan: that falls into your domain - what do you want?
Apart fr
On Monday 18 August 2014 09:02:07 Pier Luigi wrote:
> > Activities should probably be also exposed to the kf5_window interface?
>
> What do you need for activities?
@Ivan: that falls into your domain - what do you want?
Cheers
Martin
signature.asc
Description: This is a digitally signed messa
2014-08-15 7:49 GMT+02:00 Martin Gräßlin :
> On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
>> Hi,
>>
>> Just pushed some initial draft of the Wayland protocols on Github [1]
>>
>> I need people with knowledge of KF5 and plasmashell to comment it and
>>
2014-08-15 7:47 GMT+02:00 Martin Gräßlin :
> On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
>> Hi,
>>
>> Just pushed some initial draft of the Wayland protocols on Github [1]
>>
>> I need people with knowledge of KF5 and plasmashell to comment it and
>>
On Friday 15 August 2014 10:45:17 Marco Martin wrote:
> On Friday 15 August 2014, Martin Gräßlin wrote:
> > > [1] https://github.com/plfiorini/protocols
> > > [2]
> > > http://lists.freedesktop.org/archives/wayland-devel/2014-July/016056.htm
> > > l
> >
> > after going through all interfaces I thi
On Friday 15 August 2014, Martin Gräßlin wrote:
> > [1] https://github.com/plfiorini/protocols
> > [2]
> > http://lists.freedesktop.org/archives/wayland-devel/2014-July/016056.html
>
> after going through all interfaces I think we can kill the windoweffects
> interface. On X11 those were grouped
On Friday 15 August 2014, Martin Gräßlin wrote:
> another general note: I'm not sure about exposing "kf5" in the interface
> names. It has nothing to do with frameworks and I don't expect the
> interface name to change once we introduce kf6.
>
> I'm unsure what a good name could be, though. Maybe
On Friday 15 August 2014, Martin Gräßlin wrote:
> panel.xml: I think we need a property for:
> * auto-hide
> * always visible
> * windows can cover
> * window go below
>
> For the auto-hide panel we also need a trigger mechanism: the panel needs
> to know when the screen edge is approached. On X11
2014-08-14 21:05 GMT+02:00 Marco Martin :
> On Thursday 14 August 2014, Pier Luigi wrote:
>> Hi,
>>
>> Just pushed some initial draft of the Wayland protocols on Github [1]
>>
>> I need people with knowledge of KF5 and plasmashell to comment it and
>> su
On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
> Hi,
>
> Just pushed some initial draft of the Wayland protocols on Github [1]
>
> I need people with knowledge of KF5 and plasmashell to comment it and
> suggest improvements.
>
> As we are speaking of protocols, p
Martin GräßlinOn Friday 15 August 2014 07:47:27 wrote:
> On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
> > Hi,
> >
> > Just pushed some initial draft of the Wayland protocols on Github [1]
> >
> > I need people with knowledge of KF5 and plasmash
Martin GräßlinOn Friday 15 August 2014 07:35:51 wrote:
> On Thursday 14 August 2014 21:05:01 Marco Martin wrote:
> > On Thursday 14 August 2014, Pier Luigi wrote:
> > > Hi,
> > >
> > > Just pushed some initial draft of the Wayland protocols on Github [1]
>
On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
> Hi,
>
> Just pushed some initial draft of the Wayland protocols on Github [1]
>
> I need people with knowledge of KF5 and plasmashell to comment it and
> suggest improvements.
>
> As we are speaking of protocols, p
On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
> Hi,
>
> Just pushed some initial draft of the Wayland protocols on Github [1]
>
> I need people with knowledge of KF5 and plasmashell to comment it and
> suggest improvements.
>
> As we are speaking of protocols, p
On Thursday 14 August 2014 21:05:01 Marco Martin wrote:
> On Thursday 14 August 2014, Pier Luigi wrote:
> > Hi,
> >
> > Just pushed some initial draft of the Wayland protocols on Github [1]
> >
> > I need people with knowledge of KF5 and plasmashell to commen
On Thursday 14 August 2014 19:21:54 Pier Luigi wrote:
> Hi,
>
> Just pushed some initial draft of the Wayland protocols on Github [1]
>
> I need people with knowledge of KF5 and plasmashell to comment it and
> suggest improvements.
>
> As we are speaking of protocols, p
On Thursday 14 August 2014, Pier Luigi wrote:
> Hi,
>
> Just pushed some initial draft of the Wayland protocols on Github [1]
>
> I need people with knowledge of KF5 and plasmashell to comment it and
> suggest improvements.
just some quick comments after taking a qui
2014-08-14 19:21 GMT+02:00 Pier Luigi :
>
> Just pushed some initial draft of the Wayland protocols on Github [1]
>
> I need people with knowledge of KF5 and plasmashell to comment it and
> suggest improvements.
Hi folks,
It's me again... Protocols are now availabl
Hi,
Just pushed some initial draft of the Wayland protocols on Github [1]
I need people with knowledge of KF5 and plasmashell to comment it and
suggest improvements.
As we are speaking of protocols, please take a look at xdg-shell.
It's going to become stable soon [2] please point out
62 matches
Mail list logo
