Hello, On Dec 2 14:43 Ancor Gonzalez Sosa wrote (excerpt):
This reads: ---------------------------------------------------------------------- 3) The most common approach in YaST interfaces is allowing the user to configure everything in the UI without the changes taking effect immediately. When the user clicks the "ok" button, all the changes are applied to the system and the YaST interface is closed. Although that's the usual YaST behavior, it's not mandatory to stick to that approach. ---------------------------------------------------------------------- Personally I am against this usual YaST behavior. The usual YaST behavior is no real (i.e. no bidirectional) communication between user and system. The dialogs might look as if there is such a communication but actually it happens only between the user and the GUI but not between the user and the system simply because nothing is done regarding the system until the whole module is finishing and then it is too late for a bidirectional communication. A consequence is that when something goes wrong while the module is finishing (i.e. while changes are applied to the system), there can be only unfriendly error messages because the user can no longer do anything at this stage. See https://en.opensuse.org/Archive:YaST_Printer_redesign therein in particular the sections - Transaction Semantics For Each "One Setup" - "Just In Time" Configuration - Different Workflow What Actually Happens Kind Regards Johannes Meixner -- SUSE LINUX GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 21284 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org