
On 8/10/20 3:25 PM, Ancor Gonzalez Sosa wrote:
On 8/10/20 3:03 PM, Stefan Hundhammer wrote:
On 2020-07-24 14:55, Ancor Gonzalez Sosa wrote:
We also discussed the idea of offering a WUI:
- We see real use-cases for it, like: * configuration via a web browser is kind of common/expected for embedded systems, IOT devices, etc. * sysadmins needing to adjust/monitor something when they only have a browser/tablet/phone at hand
Oh, the old WebUI topic; a zombie that has to be slain every couple of years, to be summoned back into this world by somebody who hasn't been part of the previous bloody and messy slaying a few years before... ;-(
Nobody thinks it's realistic to add a web UI to the CURRENT YaST. And nobody dares to even try. The premise of the card/meeting was to think about how the UI of a tool like YaST (not necessarily its current incarnation) could look like.
You don't have to convince anyone that adding web capabilities to libYUI is a crappy idea. I hope everybody agrees there. :-)
We've been trying to add Web UI/API in the past as there was a demand for that. We have already failed, yes, but the request comes over and over again, because it's still valid approach. Some use-cases: - IoT (and RPi) - Windows user re/configuring Linux system - (Far) remote installation/configuration - 1:many management In fact, many new things have some kind of a remote API. Trackers, electric plugs, cars, temperature sensors, vacuum cleaners, ... and they mostly either have web-based one or a phone app or both. The current task was to collect "as much ideas how the perfect next generation YaST could look like" as possible. Obviously we'll think about the current libyui later and maybe ... maybe the solution could be to write a new UI framework. Maybe we find and existent project that can be used and adjusted to our needs. Maybe we'll decide to do libyui refactoring. That's all undecided yet. Hopefully (anything we'll do) we'll use as much upstream as possible. NIH syndrome should not apply here. Thx && Bye Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org