I think ths discussion is flawed because everything concentrates in the UI which is not a real issue. The real question is, is YaST a monouser application or a server service? that is the real difference that has made it a challenge. Do you keep YaST running listening for connections? or you do dirty hacks to launch the service and the browser at the same time (remember the web-updater local version crap) ? When you ignore the model, then issues start to show up. IMHO, if you turn it into a webmin-like stuff, then the web interface has lot of value. But just to replace the local toolkit in a monouser application like YaST behaves now, it is just waste of time and resources. Perhaps you can provide a good experience if YaST would handle the browser itself. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org