On Fri, 2022-12-09 at 10:21 -0500, Neal Gompa wrote: > On Fri, Dec 9, 2022 at 10:17 AM <mkolman@xxxxxxxxxx> wrote: > > > > On Thu, 2022-12-08 at 15:42 +0000, Gary Buhrmaster wrote: > > > On Thu, Dec 8, 2022 at 12:31 PM Kevin Kofler via devel > > > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > IMHO, the web-based UI is a major mistake and should never be > > > > shipped in > > > > Fedora. > > > > > > As I am sure you are aware, it seems a number of distros > > > are experimenting with their next gen installer. OpenSUSE > > > has their new web based D-installer, > > The OpenSUSE effort is very close on the library/tooling level - > > they > > also use PatternFly/React/Cockkpit to build their Web UI, pretty > > much > > like we do for the Anaconda Web UI. > > > > > and Canonical is > > > writing an installer in flutter. > > > > > > While I have not personally tried them out, so don't have > > > any real opinion in whether they are good approaches, > > > maybe eventually some of the good ideas from all the > > > distros next generations of installer will eventually cross > > > pollinate even though we likely all agree that there will > > > not be one installer to rule them all. > > Agreed! I would hope it could help with say extending PatternFly > > widgets or some Cockpit tooling to better cover some installation > > specific use cases, more people looking into library/tooling bugs > > affecting installers, etc. > > > > What I'd like to see out of this effort is some API documentation of > how the frontend (web UI) and backend (privileged services) interact > so that other frontends for Anaconda could be developed in the > future. > Eliminating desktop frontends entirely is a painful regression. :( Actually the current GTK3 GUI and even the TUI do talk to the backend over DBus. They do talk to the backend directly in a few remaining places (IIRC related to the payload handling code) but this should be also all moved to DBus in the near future. As for reference documentation of the DBus API - that's indeed on our TODO list, and definitely necessary, not just for any alternative UI efforts but also for Anaconda addon authors. > > And this new model would let us have the installer UI operate > unprivileged and use the appropriate mechanisms for privilege > escalation like any other desktop app. We are I would say already half way there, with most of the priviledged actions already taking place in the backend providing a DBus API, which the GUI still running under root mostly due to the few remaining bits of direct interaction and inertia. And some specifics of keyboard layout configuration that Jiri Konecny knows more about than me. Definitely with the Web UI the Web view app does not need to run as root. > > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
