Morten Nilsen wrote: > Massimo Maiurana wrote: >> Christopher Michael, il 22/07/2007 07:17, scrisse: >> >>>> and what will you put in applications.menu? as we don't provide the apps - >>>> how >>>> can we provide an applications.menu with any meaningful content? >>>> >>> Well, we used to provide a .order file that had some standard >>> things...xterm, xmms, etc, etc...my thoughts were along those lines. >> also, if I'm not wrong, other environments usually put every kind of >> application in their menus, not only applications directly provided >> with the environment itself (i.e. gnome includes kde apps and >> viceversa), so I agree with dh on this, e17 should install an >> applications.menu file including all sort of applications, so every >> user starting e17 has got something he could eventually edit to >> include/remove what he wants instead of an empty menu. > > In my opinion, e should auto-populate the(/a?) menu with every > application available.. > > They do show up in the menu editor, all sorted out into categories. > > It does not appear like it would be a huge pain to get such a menu set up. > > It just seems wrong - from a usability standpoint - to require the user > to update menus when a new application is installed that just happens to > not be in a menu file, but installed its desktop-file in a reasonable > location.. >
The whole point with the fd.o menu stuff is so that the distro should take care of the menu, and not all wm writers. Sebastian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
