[SLE] Suggestion, SUSE 10.1: Improve the Software Management
Open more than one instance ----------------------------- Currently (tested on gnome), YAST will let you open more than 1 Software Management (SM) windows, even after open second window it's tell you that another windows already open. I think better check first if another instance already open then bring the active instance to the front. (rather than show the second window first and then show an error message). This happen if you do several click on the S/W Management icon. Install from a folder -------------------- there is no feature in SM to open any folder to install file. such feature available on Webmin. currently, we must add each folder manually. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 14 July 2006 05:24, The Nice Spider wrote:
This is not *generically* possible because ... The first problem is that yast uses the same underlying framework for the text and GUI versions. There is no way for a CONSOLE version to be forced to the front like a GUI version can. So if i open a console yast, then bury it somewhere in a Konsole session, and then start a GUI yast, there is no programmatic way to force the console-based yast to the front. The best we can do is say "Hey, it looks like you've got another instance open somewhere." The second problem is that you might not ACTUALLY have a second instance open - this test is done based on a lock file, and it can happen that the lock file is left around after a yast instance dies (is forcefully killed). In that case, there is no instance to force to the front. The third problem is that multiple users can run yast from multiple desktop instances (e.g., my girlfriend and i are always both logged in to KDE on the same machine). There is no way for one user to force the app to the front on the other user's display, nor to "steal" the GUI from one display to another. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Friday 14 July 2006 12:20, stephan beal wrote:
And the fourth problem, of course, is that yast might not be running from a desktop at all. Most server installations don't run X11, and therefore only run the console-based yast. There are probably more reasons, but we'll stop here. ;) -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Friday 14 July 2006 05:24, The Nice Spider wrote:
This is not *generically* possible because ... The first problem is that yast uses the same underlying framework for the text and GUI versions. There is no way for a CONSOLE version to be forced to the front like a GUI version can. So if i open a console yast, then bury it somewhere in a Konsole session, and then start a GUI yast, there is no programmatic way to force the console-based yast to the front. The best we can do is say "Hey, it looks like you've got another instance open somewhere." The second problem is that you might not ACTUALLY have a second instance open - this test is done based on a lock file, and it can happen that the lock file is left around after a yast instance dies (is forcefully killed). In that case, there is no instance to force to the front. The third problem is that multiple users can run yast from multiple desktop instances (e.g., my girlfriend and i are always both logged in to KDE on the same machine). There is no way for one user to force the app to the front on the other user's display, nor to "steal" the GUI from one display to another. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Friday 14 July 2006 12:20, stephan beal wrote:
And the fourth problem, of course, is that yast might not be running from a desktop at all. Most server installations don't run X11, and therefore only run the console-based yast. There are probably more reasons, but we'll stop here. ;) -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
participants (2)
-
stephan beal -
The Nice Spider