[03:01] <holstein> OvenWerk1: you like wisker?
[03:01] <holstein> we could emulate upstream more..
[04:38] <OvenWerk1> Not so sure about wisker. I guess I could try it out, but it seems to be best for some one who has a small well thought out workflow.
[04:39] <OvenWerk1> (just looking at the web page screen shots)
[04:40] <OvenWerk1> The advantage of the formal menu we have now (over the newer search assited menus) in my mind, is that it helps the new person find software they don't know they have.
[04:41] <OvenWerk1> Or don't think they might need... and so would never search for it.
[04:46] <OvenWerk1> ... ok, just installed it. It is sort of KDEish but not as good. It does read all the menu files, but does not follow all the style hints at all.
[04:47] <OvenWerk1> As a result, the custom sub menus are spread all over the place,
[04:48] <holstein> yup
[04:48] <OvenWerk1> wisker does not do all the sub or sub-sub menus we use to make things easier to follow
[04:48] <holstein> im not wilde about it
[04:49] <OvenWerk1> so our audio production menu is a huge list of apps with no rhyme or reason.
[04:51] <OvenWerk1> I think the application finder might be more useful.
[04:57] <OvenWerk1> If I turn show menu hierarchy on it is much better. But you still need to click on the submenu before it shows rather that just hoover over it.
[04:59] <OvenWerk1> Well I can set that too, for the main catagories, but not for the submenus
[05:03] <OvenWerk1> I have KDE on two machines here (for my wife and son) and in both cases we have selected a menu type of classic.
[05:05] <OvenWerk1> So I would guess it is something that could be done, but I think it would slow me down and I would probably on my machine use the standard menu.