Re: wayland in rawhide

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 11, 2015 at 7:58 PM, David Airlie <airlied@xxxxxxxxxx> wrote:
>
>> That's fine.  I don't have a problem adding "GNOME on Xorg" option to
>> the session
>> menu in the interim. I'll do it tomorrow.
>
> This is what the feature page said would happen in the first place. So
> I'm also confused why you didn't just do that.
>
>>
>> I will say you're coming off (to me anyway) as somewhat combative.  We're on
>> the same team here.  Let's keep it constructive and friendly?
>
> Okay, I'll try and be a little less pissed off at disabling features users
> use, that we've spent years implementing in X/GNOME.
>
> The fact you are requesting wayland by default while we still have the following list:
>
> Close all remaining feature parity gaps between the Wayland and the X11 session:
>
>     input methods
>     on-screen keyboard
>     hi-dpi support
>     clipboard proxy for xwayland
>     attached modal dialogs
>     tablet support
>     startup notification
>     touch proxy for xwayland
>     accessibility features
>     output rotation
>
> These are just the missing features (never mind dialog boxes in wierd places bugs)
> and it doesn't even contain the USB output hotplugging, or secondary GPU output use cases.
>
> So maybe I'm getting old, but I thought we were over shoving half-baked onto users now,
> Maybe implement all those features, get them into the non-default wayland session,
> then go lobby for enabling the wayland session by default, otherwise I feel you are
> putting the cart before the horse.

Is the concern mostly about switching to it by default and then
somehow users won't know how to switch back to X to get their missing
features?

I'll admit that given some of the target audience we've pushed for
where they expect things to "just work", that might be a valid
concern.  If they log into an F24 Gnome session and the above things
don't work, they won't view it as "oh Wayland."   They'll view it as
"oh, regression" and likely not look at "X/Gnome" as a choice to fix
all of it.

There is definitely a degree of lower-level understanding required to
get back to a "normal" state in that case.  And it isn't like people
are going to use many of those features in GDM heavily enough that
they'd edit the conf file to switch GDM itself to X.

I have no idea if it's possible to detect usage of the above features
in existing installs and not default to Wayland in that case.  Or if
it's possible to switch to X if a user turns on one of the features on
a new install.

josh
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux