Free run dialog box software for linux

Though similar in style to CDK, Dialog is different, being a script-interpreter which provides a set of curses widgets. Widgets are objects whose appearance and behavior can be customized. There is a much-reduced variation of dialog, called lxdialog, which is used in Linux kernel configuration.
Dialog allows you to present a variety of questions or display messages using dialog boxes from a shell script. Several types of dialog boxes are implemented including: calendar, checklist, file-selection, gauge, info, input, menu, message, radiolist, tailbox, text, time, yes/no.
Enhancements:
- change license to LGPL.
- change naming convention in dlg_colors.h to make it easier to read, and incidentally remove the last chunk of code preventing relicense.
- add --passwordform (request by Reznic Valery).
- modify pause.c, msgbox.c to work with --help-button.
- modify formbox.c, inputbox.c, textbox.c, yesno.c to work with extra button (adapted from Reznic Valery patch).
- modify dlg_exit_label(), dlg_yes_labels() and dlg_ok_label() to allow help-button (prompted by Reznic Valery patch).
- add zh_CN.po file from http://www.iro.umontreal.ca/translation/maint/dialog/
- provide alternate interfaces for dialog_checklist(), dialog_menu() and dialog_form(): dlg_checklist(), dlg_menu() and dlg_form() (discussion with Michael Gebetsroither).
- add/use dlg_result_key() to allow binding function keys to the buttons.
- implement user-definable key bindings in the rc-file.
- modify inline cases for KEY_xxx values to use binding tables in new module dlg_keys.c
- add several DIALOG_STATE items to the rc file: aspect, separate_widget, tab_len and visit_links
- add a tab-adjustment to dlg_print_text() to improve solution from 2005/10/30, e.g., in the samples/form* scripts.
- fix an off-by-one which made mouse-selection not work for menu items past the first page (GenToo #112024, patch by Harald van Dijk).

Gtkdialog is a small utility for fast and easy GUI building.
It can be used to create dialog boxes for almost any interpreted and compiled programs which is a very attractive feature since the developer does not have to learn various GUI languages for the miscellaneous programming languages.
Enhancements:
- This version contains some minor bugfixes and enhancements.

run in xterm is an servcie menu which adds "run in xterm" & "run in xterm as root" to action menu on binary files, scripts etc.

It has 2 languages: english and polish.

Installation:

copy/save this file in
~/.kde/share/apps/konqueror/servicemenus

KMilo - Compact Dialog is a KDE patch that makes the default sound dialog look a bit less huge and BLUE.

Tested with 3.5.5 and 3.5.6

Open Beat Box (OBB) is an open-source beat box ( a virtual drum machine ).
We are still in an early stage of development but we aim full drum machine functionalities.
Main features:
- Highly customizable graphical interface, including bitmap skins and variable shape widgets.
- Floating tools : realy interesting with multi-screen.
- Skin aware help system that update the images acording to the skin you curently use.
- Plug-in architecture for sound effects.
- Portability : Windows, Mac, Unix
- Cross-platform file compatiblitily.
- Real-time preview and offline rendering for realy complex effect that cant be added real-time on your machine
- Distributed rendering over multiple computers.
- Customizable sound sample packages.
- Customizable keyboard shortcuts.
- Matel Power glove input driver.
Enhancements:
- Code major restructuration
- More performance
- Added XML Skins
- Gui enhancements (drop shadow on labels, centered spinbox label, mousescroll on slidebars)

dialog-mp3-list generates an organized list of your CDs and directories of MP3s. It shows a numbered list of MP3s with information on their encoding speed and track lengths. It uses Dialog/XDialog and Latex to create lists in .tex, .ps, and .pdf formats.

You can modify the source file .tex and then you can compile it with the commands:

latex lista-mp3-albuns.tex
dvips lista-mp3-albuns.dvi -o
ps2pdf lista-mp3-albuns.ps

Gtk2::Ex::Dialogs is a Perl module with useful tools for Gnome2/Gtk2 Perl GUI design.

SYNOPSIS

use Gtk2::Ex::Dialogs ( destroy_with_parent => TRUE,
modal => TRUE,
no_separator => FALSE );

# do some stuff like creating your apps main $window then,
# to ensure that all messages use the right parent, set it:
Gtk2::Ex::Dialogs->set_parent_window( $window );

# now popup a new dialog
my $r = ask Gtk2::Ex::Dialogs::Question ( "Is Perl only hackers glue?" );
if ( $r ) {
# end-user thinks so
} else {
# end-user does not think so
}

# now popup a new dialog ( blocking the main loop if there is one )
new_and_run
Gtk2::Ex::Dialogs::Message ( title => "Dialog Title",
text => "This is a simple message" );

# now popup a new dialog ( blocking the main loop if there is one )
new_and_run
Gtk2::Ex::Dialogs::ErrorMsg ( "Simple error message." );

This module provides the Gtk2::Ex::Dialogs::Message, Gtk2::Ex::Dialogs::ErrorMsg and Gtk2::Ex::Dialogs::Question classes to the main application while setting the initial defaults to those specified upon using Gtk2::Ex::Dialogs.

IPC::Run::Simple is a simple system() wrapper.

SYNOPSIS

# Run a command and check whether it failed
use IPC::Run::Simple;
run("echo Hello, O Cruel World")
or die "Command failed";

# Describe the failure
use IPC::Run::Simple qw($ERR);
run("echo Hello, O Cruel World")
or die "Command failed: $ERR";

# Use the :all tag instead of explicitly requesting $ERR
use IPC::Run::Simple qw(:all);
run("echo Hello, O Cruel World")
or die "Command failed: $ERR";

# Die with error message if command does not return 0
use IPC::Run::Simple qw(:Fatal);
run("echo Hello, O Cruel World");

# Allow other exit values without dying
use IPC::Run::Simple qw(:Fatal);
run(command => [ "echo", "Hello, O Cruel World!" ],
allowed => [ 1, 2, 5 ]);

This module is intended to be a very simple, straightforward wrapper around the system() call to make it behave more like other builtins.

run() will return a true value if the command was executed and return a successful status code, and false otherwise. The reason for the failure will be stored in the $IPC::Run::Simple::ERR variable (which is just $ERR if you import either $ERR or :all). The description of the reason was pulled almost directly from the system() documentation.
Optionally, you can import the :Fatal tag, which will cause run() to die() with an appropriate message if the command fails for any reason.

If you wish to allow nonzero exit values but still want to trap unexpected errors, you may use an expanded call syntax. Call run() with a set of key=>value pairs. The two implemented keys are command (an array reference containing the command to run) and allowed (an array reference of exit values that are allowed without causing run() to return false or throw an exception.)