On Fri, May 1, 2009 at 6:51 PM, Michael Stibane <[email protected]> wrote: > Hi list! > > The old menu w/o menu-cache was by far more reliable - it simply worked. > > That daemonized reading - caching - refreshing - displaying thing is > much too over-engineered for my taste. That's what I understand you did > with the new menu. > > A simple read - display /usr/share/applications every 2 minutes is fine > imho.
Don't jump in a conclusion when you don't really know how it works. The freedesktop.org spec itself is the one that's over-engineered. The menu-cache is a solution to this unfortunate design. Without this daemon, every app requiring the menu needs to load houndreds of files, merges several large and complicated xml files, and then work out a final menu. Besides, each application using the menu needs to monitor all involved files in order to refresh the menu after changes. The number of file monitors required by each application is about 10, With menu-cache, all applications share the same set of resources. And due to the cache, no complicated parsing is needed and every application only need to read ONE file to get the menu. If you think this is overly-engineered, you should use gnome, and see how it works. Quite interesting... ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
