From: Chad Perrin Date: 2005-12-23T10:16:27+09:00 Subject: Re: Ruby version of UMENU On Fri, Dec 23, 2005 at 06:51:00AM +0900, Gregory Brown wrote: > On 12/22/05, Steve Litt wrote: > > > From what I read about Highline, Highline and UMENU are totally > > different tools that can't really be compared. Indeed, I could > > easily forsee several Highline-enabled apps called from a UMENU > > menu system. My "short answer" would have been another perspective on the above paragraph: "What are the advantages of using an orange crate over an apple?" Yes, it's true you can't eat an orange crate, but but it sure does make it easy to carry oranges around. Unless I'm way out in left field, my impression is that UMENU is basically a replacement for something like the K menu in KDE, or the Start menu in Windows, but designed to be used with window managers for X when the user doesn't like to use his/her mouse for choosing applications from a menu. I don't see how that makes UMENU and Highline comparable at all. Please let me know if I misunderstood the purpose of UMENU, Steve. > > Yeah, I kind of misjudged the purpose of UMENU when I read through the source. > It does look pretty neat, and would probably be a great wrapper for > HIghLine applications, though building menus is easy enough to do in > pure ruby using our system :) > > I do like the fact that you support a sort of intermediate > configuration setup for menus so an admin or power user can build > them. That's very cool. . . . and I still don't think you understand UMENU's purpose. That, or I don't. -- Chad Perrin [ CCD CopyWrite | http://ccd.apotheon.org ] unix virus: If you're using a unixlike OS, please forward this to 20 others and erase your system partition.