https://bugzilla.novell.com/show_bug.cgi?id=751665 https://bugzilla.novell.com/show_bug.cgi?id=751665#c0 Summary: Our Interface with the KDE Windowing Manager is Creating More and More Prevalent Dialogue Box Windows-CUA Limitations Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: PC OS/Version: openSUSE 12.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Board AssignedTo: board@opensuse.org ReportedBy: scott@aphofis.com QAContact: board@opensuse.org Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Why is this important and what is this about....Please be patient and I will explain. Microsoft Windows follow a convention known as CUA...CUA convention has a huge number of incidentals like CTRL+Click and SHFT+Clik, Minimising and Maximising, the Change in Focus, CRTL+A, CTRL+C, CRTL+X, CTRL+V etc. All these rules or conventions have been set in concrete since MS Windows 2.x and for convention we keep most of them for obvious reasons. What makes our Windowing Manager stand so tall and apart from Windoze is our Linux Kernel and true Multitasking...MS will never have a fast interface until they change their base O/S and limitations of executing code in the first 640K of base RAM. MS has to have an XML Memory Juggler throwing processed events up past the 1 GIG of RAM. The juggler has to work hard throwing up stored results above 640K and drag them back of their result if further needed in the processing of more lines of code....If your interested in how to demo this on even a MS Windows 7 system and seeing the GUI failing on BOOT with the blue screen of death saying 'Out Of Memory'...email me please. What we are starting to do more and more in the development of OUR KDE Windowing Manager is creating more and more dialogue boxes! Dialogue boxes are the heart of why MS is such a poor performer. A dialogue box is part of the Windowing Manager that when it appears on the screen, it hold total focus and wont let the focus be changed unless you either satisfy or close the dialogue box. The convention of a Dialogue box is becoming more widely created here and there and we must get rid of this ridiculous convention. MS Windows can multi-task only until a Dialogue Box appears - It has to have an end to the dependant and subsequent subordinate windows that emerge as we go about using the PC application. So far we have not created such horrors but they are creping in more and more and if we want to maintain our ability to truly multitasking in our Windowing Manager; we need to be aware, identify and get rid of these Dialogue box conventions and types I'll attach a small example in which you can see three passive windows in background and a Dialogue box holding complete focus. In the example you cant go back to the focus of a background window, say to copy some text, as the dialogue box will never let go of its focus. Its not until you either close or satisfy the dialogue box in focus can you put any parent window into focus! We need to nip this in the bud and stop creating Dialogue boxes which is the singular frustration of ANY MS Windoze user but for obvious reasons MS cannot remove the concept of a dialogue box lest they run the chance of uncontrollable parent and subordinate windows...you get the picture. We need to stay apart from some CUA conventions and to date they are few dialogue boxes in our current releases but they are on the rise. Can you please discuss this with KDE developers so we can remain different, remain fast as lightning and without stupid restrictions for the user but ones needed by their others O/S. If we identify this issue and nip it in the bud right now we can stop the possibility of having to change a huge amount of code in the KDE Windows Manager and Maintain our Superiority. I am sorry to be so long winded, and I thank you for reading this and I hope we will continue to prevail with the most sophisticated and superior Windowing Manager bar none. I am happy for you to change, modify reclassification and priority...:-) Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. Actual Results: See text and screen shot Expected Results: We need to always be better than anything else and with our Kernel we can! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.