[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: Application for Forking UKUI-KWin from KWin
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2023-08-02 20:11:03
Message-ID: CACcA1RppiKSMQ8YrDf2iDbqcoYjjH_guq1CLxqTunGg7Be4Shw () mail ! gmail ! com
[Download RAW message or body]

Hi Mouse Zhang,
It would be useful if you can make sure that when you move to Wayland,
you can move back to upstream KWin, would that be something you'd
consider?

If you outline what's necessary there for you, maybe we can work it
out to make sure you have all the features you need.

Simultaneous X11 and Wayland should be supported through Xwayland.

FWIW, I think the dependencies problem is mostly because of the
obsession some distributions have to split every package as much as
possible, but otherwise the stuff you get shouldn't be that big a
problem.

Best,
Aleix

On Mon, Jul 31, 2023 at 5:01 AM MouseZhang <sendbypython@foxmail.com> wrote:
> 
> Hi David:
> 
> Tablet Mode:
> 
> In the UKUI desktop environment, besides manually switching,
> the switching between PC and tablet mode can also be triggered
> by listening to keyboard plug-and-unplug events. Some components
> also respond to these plug-and-unplug signals to transition between PC
> and tablet mode. Furthermore, there is a window called "blur background,"
> which appears underneath the active window (more precisely,
> under all windows of the active window's process), regardless of
> whether the window can be maximized or has child windows. Similar to the image \
> below: 
> 
> Virtual Keyboard:
> 
> Now, the virtual keyboard works well on X11, there are terrible bugs on wayland,
> but we will support wayland in the future.
> 
> On x11, it will be covered by popup window:
> 
> 
> Dependencies:
> 
> I removed all debian package which name contains "plasma", then "sudo apt install \
> kwin-x11 kwin-wayland". Plasma-workspace and plasma-workspace-wayland and …will \
> be installed. This is one of the reasons why we want to fork the ukui-kwin.
> 
> 
> Wayland is the future, but currently, it's not stable enough, and we will do our \
> best to address its shortcomings. Our users, on the other hand, prefer to use a \
> more stable desktop environment and some applications that are only supported on \
> X11. Hence, we need to support both X11 and Wayland simultaneously. 
> Best regards,
> 
> Mouse Zhang
> 
> 
> > On Jul 28, 2023, at 16:01, David Edmundson <david@davidedmundson.co.uk> wrote:
> > 
> > Hello,
> > 
> > You don't need to apply to fork, it's open source you entitled to just
> > go ahead and do so.
> > Please send us a link to your repository so we can keep up-to-date
> > with each others work.
> > 
> > But to address your individual points:
> > 
> > - 1. Tablet Mode Support: We have incorporated support for the UKUI
> > tablet mode, which differs from the existing tablet mode mechanism in
> > KWin.
> > 
> > Can you expand on what's different. I think we can improve on our
> > tablet mode, so if you have ideas I'm interested in hearing them.
> > 
> > - 2. Virtual Keyboard
> > On wayland or X?
> > 
> > - 3. Custom Protocols: To fulfill the application requirements in the
> > UKUI environment, we have added or modified certain protocols, such as
> > the blur effect with gradual intensity changes.
> > If you do use custom protocols can you ensure they have a separate
> > interface name so we don't get any runtime collisions in applications.
> > 
> > - 6. Dependency Management:
> > Out of curiosity which dependencies were the most problematic? There
> > has been a move in kwin to remove some parts.
> > 
> > - 7. X11 Support: We require continued support for X11 and plan to
> > develop new features to ensure flexibility and compatibility of UKUI
> > across various systems.
> > 
> > There are lots of issues on Wayland, but long term it is the path
> > we'll all end up on. I suggest trying to fight upstream for whatever
> > needs fixing now, so that it can get fixed in the long term.
> > 
> > Good luck with your project, please do keep in contact, potentially we
> > can end up back in sync one day.
> > 
> > David
> 


[prev in list] [next in list] [prev in thread] [next in thread]