Free menu software for linux

k-menu is a SuperKaramba theme that emulates KDE kicker.

AI::Menu is a Perl object that generates Tree::Nary objects from directed graphs or a description of the function set.

The algorithm is not very efficient (approximately O(F^6), F being the number of functions). It is also not quite as intelligent as it should be. You should cache the results instead of repeatedly calculating them.

As the algorithm is optimized or more efficient algorithms are found, they will be incorporated. The interface for generating the trees should not change too much. The resulting object might become a Tree::Nary object encased in an AI::Menu object.

SYNOPSIS

use AI::Menu;

my $factory = new AI::Menu::Factory;

my $menu = $factory->generate($hash_of_functions);
my $menu = $factory->generate($hash_of_functions, $hash_of_categories);
my $menu = $factory->generate($graph);

METHODS

All of the following methods (except generate) are available in the new function when creating the AI::Menu::Factory object.

generate

This function does some housekeeping before calling a configurable module to generate the tree.

If called with a single hash reference, the hash is assumed to be a list of functions mapping to array references containing a list of categories. It is further assumed that the sets of function names and category names are disjoint. A closure is created for the leaf_q function which returns true if its argument is a key in the hash reference. The complete graph is created from this single hash reference: if a category can reach another category through a function, then an edge is inserted between the two categories. This edge is bidirectional.

If called with two hash references, the first hash is treated as before, but the second hash reference is considered a mapping of categories to categories. This second hash is used instead of automatically generating the information from the first hash.

If called with a single object that is not a hash reference, then the argument is considered a graph object (usually of Graph::Directed). The leaf_q function will need to be defined.

leaf_q

This function returns true if the argument represents a function (leaf in the graph). It returns false if the argument represents a category. This may be set either when the AI::Menu::Factory object is created or through a method call. The method call with no argument returns the current function.

maker

This is the package used to create the menu from the graph. The following call is made:

my $menu = $self -> {maker} -> new(
width => $self->{width},
weight_f => $self -> {weight_f},
leaf_q => $leafq,
);

return $menu -> generate_tree($g, $optscore);

The $optscore value is the score for the optimum tree. Once a tree is found with this score, searching should stop.

new

Creates an AI::Menu::Factory object. Optional arguments are key/value pairs taken from this list of methods except for generate and new.

weight_f

This function is used to calculate the edge weights in the graph. It is called with four arguments: the object generating the tree, the graph object, the originating vertex, the destination vertex. The function should return undef for an infinite weight.

width

This is the desired number of children per node. The optimal number (and default) is three.

DOM Menu allows developers to add dynamic, hierarchical popup menus on their web pages. The direction of the menu can either be horizontal or vertical and the menu can open (or popout) in either direction. It has both screen edge detection and < select > element detection (for browsers that cannot hide these form elements).
The styles for the menu items are contr olled almost entirely through CSS and the menus are created/hidden using the DOM (Document Object M odel).
Menu configuration is done using a custom Hash() class and is very portable from a PHP type array structure. The menus attempt to follow the look and feel of well known GUI toolkit menus.
Version restrictions:
- cannot use opposite direction to open
- opera 7 having difficulty with table (need to work around)
Enhancements:
- added support for IE 5.0
- fixed problem when submenu was deactivated and parent would highlight
- added a converter from phplayersmenu

Cabextract menu is just a little service menu that I put together for extracting MS .cab files.

It creates a directory with the same base name in the same directory as the .cab file and extracts to it. To use it, you have to have cabextract installed (and can be found here http://www.kyz.uklinux.net/cabextract.php.

Menu Buddy plugin currently comprises a couple of Python scripts for creating GNOME panel menus from a directory hierarchy of music files.
These menus can be used to play or enqueue songs in XMMS, as well as pause or skip XMMS.
These scripts are not terribly powerful yet, but there is potential for a signficantly more flexible system of menu-creation that allows automatic construction of many different kinds of menus based on directory hierarchies.
menu_buddy is a small script for scanning a hierarchy of music files and creating a set of Gnome menus that can direct xmms to play those files. Instead of going through the command line or whatever, menu_buddy lets you play/enqueue files in xmms straight from your menu. I find this pretty convenient.
The command line for menu_buddy is as follows:
menu_buddy < source dir > < dest dir >
where:
< source dir >: The top of a hierarchy of directories containing the files
< dest dir >: The top of a directory to write the menu files into
menu_buddy works with the assumption that you have your music stored under one main music directory, using some meaningful hierarchy, and that theres only music stored down there. menu_buddy doesnt do any sort of file-type checking and assumes that everything under is fair game for playing in xmms.
What menu_buddy does it this: it constructs a menu hierarchy that directly matches the hierarchy under such that any directory or tree thereof can be played or enqueued in xmms. Likewise, at the top of the menu structure, it creates menu option which allow you to pause, start, or skip forward/backward in xmms. The interaction with xmms is purely in terms of command line options that you can pass to xmms...there is no special linking or whatever.
So, for example, lets assume you have all of your music in under the directory "/music", with top-level folders for different genres (i.e. /music/rock, /music/polka, etc.). Inside each genre, you have your files sorted first by artist, then by album (i.e. /music/rock/faith_no_more/the_real_thing, /music/polka/the_polka_kings/greatest_hits). The organization you have is really unimportant, but bear with me here.
Further, lets assume that your system lets you create new gnome menus by putting menu files in ~/.gnome/apps (this is how things work on my system, but honestly Ive done next to zero research into this topic...it may vary (wildly) on your system, so I suggest you figure it out for yourself). Then, the following command will create a new menu hierarchy in your "favorites" menu called "Muzik" which allows you play/enqueue your music:
menu_buddy /music ~/.gnome/apps/Muzik
Thats it. It may take a few seconds to churn through your music files, depending on other system load and how much music you have. You need to be able, of course, to write to the output directory you specify, but since it will typically be in your home directory this should not be a problem.
Enhancements:
- added GPL stuff to source files

encFS service menu one little KDE service menu for encFS directory.

Installation:

ungzip and copy in ~/.kde/share/apps/konqueror/servicemenus

Usage:

Click on encFS directory and click on mount.

For unmounting, click on origin directory and click on umount, this unmount and remove destination directory.

READ THIS PLEASE:

This script create a directory in your home with name encFS_$DIR. For to mount correctly, this directory must not exist.

K Menu Gnome project is a K Menu with Gnome folder and extra icons for KDE 3.2 or later.

If you install both KDE and Gnome then K Menu will become a mess with overpopulated submenus. Some distributions try to solve this by hiding many Gnome apps in KDE and most KDE apps in Gnome. I do not like that. I want to access Gnome apps in KDE and KDE apps in Gnome. So this is my attempt to both maintain desktop interoperability and unmess the menus.

Why should one install both KDE and Gnome at all? You might share your machine with somebody who prefers the other desktop, or you might be a desktop junky like I am.

K Menu Gnome does not integrate well with the menus of heavily customized distributions such as Mandriva, SUSE, or UHU-Linux.