Bug 258846

Summary: No write progress in dns and routing standalone modules
Product: [openSUSE] openSUSE 10.3 Reporter: Katarina Machalkova <kmachalkova>
Component: YaST2Assignee: Katarina Machalkova <kmachalkova>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Minor    
Priority: P5 - None    
Version: Alpha 2plus   
Target Milestone: ---   
Hardware: All   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Possibility of avoiding pop-up in remote admin module

Description Katarina Machalkova 2007-03-29 12:45:16 UTC
In yast2-dns and yast2-routing standalone modules, there is no progress dialog at the end, when the configuration is written back.
So after the user clicks on 'Finish' button, the module hangs for a while, writing the configuration, runing SUSEconfig etc. but the user in front of the screen has no idea of what is going on at the moment.
Comment 1 Martin Schmidkunz 2007-03-30 07:13:42 UTC
In order to have a consistent YaST it is important that all modules behave in the same way.
Most of them present an initializing page and a "writing the configuration" page when the user changes something. Some modules (e.g. Hostnames, Proxy, Remote Administration, DNS, Routing) don't behave in that way.
So to increase consistency and to meet user expectations I would strongly recommend to add a "writing the configuration" page when the configuration is written and not to leave the user with a temporally frozen module.
Comment 2 Katarina Machalkova 2007-04-19 14:44:46 UTC
DNS part is done :-)
Comment 3 Katarina Machalkova 2007-04-20 06:37:34 UTC
Martin, do you think it makes sense to add a progress dialog even if it has a single step? That is the case of Hostnames and Proxy modules.
Comment 4 Martin Schmidkunz 2007-04-20 12:44:33 UTC
For the sake of consistency: yes :-)
BTW: Can we get rid of that "configuration saved" pop-up? It doesn't provide any useful information to the user and IMHO its the only "configuration saved" pop-up in the whole YaST. 
Comment 5 Martin Schmidkunz 2007-04-20 14:44:10 UTC
The only kind of information the user gets is:
* there are apps using at once
* there are apps using after a while
* there are apps not using it at all.

This information is definitly completely useless.  
Comment 7 Katarina Machalkova 2007-04-23 07:22:16 UTC
Well, we can remove it, but what about Remote administration module? - it finishes writing the configuration with a popup as well, telling user to restart display manager so that settings can take effect. 

Shall I remove this popup, too? But how to notify user about the fact that he/she need to do something extra (relogin, restart dm) to apply the settings? I think putting this information into the help text is not a good idea, since users usually read the help text only if nothing else helps ;-)
Comment 8 Martin Schmidkunz 2007-04-25 06:07:32 UTC
Please remove the pop-up in the "Remote Admininstration Module" as well.
I fully agree with you, that putting the information into the help text is not a good idea (personally I think that putting it into the help text as it is now would mean the same as dropping this information at all :-)).

What about putting the information about any extra actions which are required by the user to the end of the main dialog?

Something like:
-------------------------------
<bold>Note:</bold> Any changes will take effect after the next login or after restart of the display manager.   

  
Comment 9 Katarina Machalkova 2007-04-25 09:41:13 UTC
I see. I'm just not sure which 'end of the main dialog' do you mean. Is it the help text to the left of write progress (saving configuration) dialog?
Comment 10 Martin Schmidkunz 2007-04-25 14:47:14 UTC
Created attachment 134326 [details]
Possibility of avoiding pop-up in remote admin module
Comment 11 Katarina Machalkova 2007-05-03 14:20:37 UTC
I did some further investigation into this, as me and Miso did not quite like the possibility of moving information from popup to the label (frankly, it did not look as well as we expected).

According to bug #55458, the popup in remote administration module was originally there because calling 'rcxdm reload' killed the running X session and that's why display manager needed to be restarted manually. 
It no longer does 'rcxdm reload' works well for kdm and xdm. Unfortunately, not for gdm, but for gdm it is enough to run appropriate SuSEconfig module to enable/disable remote administration. 

Conclusion: we can drop the popup completely, without any further changes to UI.
Comment 12 Katarina Machalkova 2007-05-03 14:58:13 UTC
Finally fixed (for the next build - y2-network 2.15.30)