Patrick Shanahan wrote:
* David C. Rankin <drankinatty@suddenlinkmail.com> [10-29-08 09:36]:
That's one fine customer focused corporate philosophy: "usability issues usually do not qualify for online update"
If you will look back, you will find that it has been this way! IOW, "Not a new policy."
I mean how hard could it be to put kbd shortcuts back in? I'll know after I finish getting smart on YUI;-)
If it is that "easy", you are/will provide the function?
The blogspot link listed in the post explains a little more about the current situation. Even the developers aren't too happy about the current state of the 11.0 ncurses UI. Two questions linger. (1) How or why did it ever get released in the shape it is in anyway?, and (2) since this has obviously been a known issue for quite some time and already fixed for 11.1, why wasn't a fix developed and deployed for 11.0 at the same time? As long as I can remember, at least back to 8.0, the ncurses shortcut keys have always been present and always worked. How does something like that just disappear? Why dwell on the past? There have been a number of yast/zypper updates for 11.0, one as recent as last week. If another is needed, why not have this fix ready to deploy at that time? I get it -- the 11.0 ncurses interface is awkward to use in its current state, but beyond that, it is usable. (with lots of arrow keys and lots of tabs) Ok, that's the decision on the bug -- that's fine. However, the intriguing part about the bug to me was the manner in which the bug was closed -- "RESOLVED". Huh? Really? That's what "RESOLVED" means? To avoid a little bit of intellectual dishonesty, wouldn't "WONTFIX" have been the more appropriate designation for 11.0? Let's see: (a) Problem Reported for 11.0 -- check (b) Problem Validated for 11.0 -- check (c) Solutions Considered -- check (d) Decision made to NOT FIX -- check I understand why Novell wants to focus on 11.1 right now, but why forget all of those users who have installed, or more importantly those who _will_ install, 11.0 in the future. 11.0 is still the "current" release isn't it? It will still be supported for another 18 months or so, right? If the install/configuration tool is one of the main yardsticks by which Linux distributions are measured as you read in nearly every press review, why not make sure the you put your best foot forward? Just seems like a missed opportunity to me. Anyway, this issue is closed. If I can learn enough about YUI with the great start Stefan was kind enough to provide, I'll be happy to submit a patch, that is of course, unless you beat me to it... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org