NAME

Curses::Widgets -- Curses-based widgets and functions

Doc/Module Version info

$Id: Widgets.pod,v 0.9 1999/11/17 02:40:02 corliss Exp corliss $

SYNOPSIS

use Curses::Widgets;

--or--

use Curses::Widgets qw( :standard );	# same as above
use Curses::Widgets qw( :functions );	# just functions
use Curses::Widgets qw( :all );	 	# everything

REQUIREMENTS

Requires the Curses module, Curses or nCurses libraries. You must still 'use Curses;' in your script as well.

DESCRIPTION

This module provides a standard library of functions and widgets for use in creating Curses-based interfaces. Should work reliably with both Curses and nCurses libraries.

Current widgets include:

Text field (txt_field)
List box (list_box)
Button sets (buttons)
Calendar (calendar)
Message box (msg_box)
Input box (input_box)

Extra functions include:

select_colour
line_split
grab_key

Note that all of the widgets strictly use named parameters, while the functions use unamed arguments. All of them either return values, or modify references that were passed as arguments.

EXPORTED

Default

  • txt_field

  • buttons

  • list_box

  • calendar

  • msb_box

  • input_box

  • select_colour

OK

  • line_split

  • grab_key

WIDGETS

Text field

The text field widget creates a derived window (which uses coordinates relative to the passed window) with a border surrounding the text. When used interactively, it handles its own input, passing back only the keys it doesn't know how to handle, as well as the final content string.

The widget provides an arrow superimposed on the border to indicate whether there is content that can be scrolled to in that direction. The arrow only appears when the content exceeds the display area.

Currently, this widget will handle any normal characters to be inserted into the content string, and the following keys:

Key		Curses Constant
-------------------------------
backspace	KEY_BACKSPACE
left arrow	KEY_LEFT
right arrow	KEY_RIGHT
up arrow	KEY_UP
down arrow	KEY_DOWN
page up		KEY_PPAGE
home		KEY_HOME
end		KEY_END

All parameters are passed as named parameters:

Parameter	Commments
-----------------------------------
window		object handle to parent
		window for the widget
ypos		integer, optional,
		default is 1
xpos		integer, optional,
		default is 1
lines		integer, optional,
		default is 1
cols		integer, optional,
		default is $COLS - 2
content		string, optional,
		default is "\n"
pos		integer, optional
		default is 0
border		named colour, optional
		default is 'red'
function	reference, optional
draw_only	integer, optional
		default is 0
l_limit		integer, optional
c_limit		integer, optional
title		string, optional
regex		string, optional,
		default is "\t"

'window' is a object handle to a predefined window or subwindow. A quick tip for debugging: if either 'xpos', 'ypos', 'lines', or 'cols' cause any portion of the window to extend passed the boundaries of the parent window, the module will print an error message to STDERR, and immediately exit the routine--no attempt will be made to draw or activate the widget.

'pos' refers to the cursor position for use in interactive mode, so that input can be inserted or appended to the content string. This is ignored if passed in conjunction with the draw_only parameter. Valid settings are 0 - length($string), or -1 to place the cursor at the end of the string.

'function' is a scalar reference to a subroutine that can be called by the widget when it times out, waiting for input. For this to work, it assumes a halfdelay(10) has been called, or on some other interval.

'l_limit' and 'c_limit' are completely optional, and can be used together, if desired. Both are integers, and can limit the content in the text field. Which ever limit is hit first will be honoured.

'title' is an optional string that will be superimposed over the top-left border in reverse video.

'regex' is a string of all the characters that you wish to use to shift focus off the text field, and return the contents. By default, the tab character is used ("\t"). This string is interpolated inside of character class brackets, so don't include regex specific punctuation. If you wish both new lines and tabs to shift focus, you would use "\t\n".

The memory allocated for the window is released when the widget routine exits.

B<Example (non-Interactive)>

txt_field( 'window'	=> $window,
	   'ypos'	=> 2,
	   'xpos'	=> $COLS - 5,
	   'lines'	=> $LINES - 10,
	   'cols'	=> $COLS - 10,
	   'content'	=> $note,
	   'border'	=> 'red',
	   'draw_only'	=> 1);

B<(Interactive)>

($key, $rtrnd_note) = txt_field( 'window'	=> $window,
				 'ypos'		=> 2,
				 'xpos'		=> $COLS - 5,
				 'lines'	=> $LINES - 10,
				 'cols'		=> $COLS - 10,
				 'content'	=> $note,
				 'border'	=> 'green',
				 'pos'		=> length($note),
				 'function'	=> \&clock);

List box

The list box widget creates a derived window that holds a scrollable list of items, surounded by a border. When called interactively, it handles it's own input for navigation. Any keys not used for navigation are returned, as well as the currently selected item.

Key		Curses Constant
-------------------------------
up arrow	KEY_UP
down arrow	KEY_DOWN

The widget provides an arrow superimposed on the border to indicate whether there is content that can be scrolled to in that direction. The arrow only appears when the content exceeds the display area.

All parameters are passed as named parameters:

Parameter	Commments
-----------------------------------
window		object handle to parent
		window for the widget
ypos		integer, optional,
		default is 1
xpos		integer, optional,
		default is 1
lines		integer, optional,
		default is 1
cols		integer, optional,
		default is $COLS - 2
list		reference, optional
border		named colour, optional
		default is 'red'
selected	integer, optional,
		default is 1
function	reference, optional
draw_only	integer, optional
		default is 0
title		string, optional

All previously described parameters maintain their same use and warnings.

'list' is a hash reference, and a numeric sort is done on the keys, while the associated values are what are actually displayed. The keys must be a sequential sequence of numbers. It doesn't care what number you start with, but it must be sequential.

B<Example (non-Interactive)>

list_box( 'window'	=> $main,
	  'ypos'	=> 2,
	  'lines'	=> 10,
	  'cols'	=> 25,
	  'list'	=> \%list,
	  'border'	=> 'red',
	  'selected'	=> 1,
	  'draw_only'	=> 1);

b<(Interactive)>

($input, $selected) = list_box( 'window'	=> $main,
				'ypos'		=> 2,
				'xpos'		=> 5,
				'lines'		=> 10,
				'cols'		=> 25,
				'list'		=> \%list,
				'border'	=> 'green',
				'selected'	=> $last,
				'function'	=> \&clock);

Button set

The button bar creates a derived window as well, printing the passed buttons, and handles the key strokes to navigate amongst them, while passing any other keystrokes and the currently selected button. The button set can be rendered either vertically or horizontally, and the keystrokes that can be used for navigation depend upon that.

Key		Curses Constant
-------------------------------
left arrow	KEY_LEFT
right arrow	KEY_RIGHT
up arrow	KEY_UP
down arrow	KEY_DOWN

All parameters are passed as named parameters:

Parameter	Commments
-----------------------------------
window		object handle to parent
		window for the widget
buttons		reference
ypos		integer, optional,
		default is 1
xpos		integer, optional,
		default is 1
active_button	integer, optional
function	reference, optional
vertical	integer, optional
draw_only	integer, optional
		default is 0
spacing		integer, default is 2

Again, all previously described parameters remain the same. Boundary checking is still done for the entire bar, and if it exceeds them it will simply be skipped without drawing, while sending an error message stating as much to STDERR.

'buttons' is an array reference with each element a separate button. 'active_button' is the element's positional reference. 'spacing' is the number of whitespace used to separate the buttons (spaces in horizontal mode, lines in vertical mode).

If 'vertical' is passed with a Perlish true value the button set will be rendered as a vertical set.

B<Example (non-Interactive)>

buttons( 'window'	=> $win_bar,
	 'buttons'	=> \@buttons,
	 'active_button'=> 2,
	 'draw_only'	=> 1);

b<(Interactive)>

($input, $selected) = buttons( 'windows'	=> $win_bar,
			       'buttons'	=> \@buttons,
			       'active_button'	=> $last,
			       'function'	=> \&clock);

Calendar

The calendar widget creates a fully navigable calendar in a derived, bordered window. The calendar controls its own input until it captures a keystroke it doesn't explicitly handle. In that case, it returns the key.

Key		Curses Constant
-------------------------------
left arrow	KEY_LEFT
right arrow	KEY_RIGHT
up arrow	KEY_UP
down arrow	KEY_DOWN
home		KEY_HOME
page up		KEY_PPAGE
page down	KEY_NPAGE

The home key, in this case, moves the selected date to the the current date. The page up and down keys move the calendar from month to month.

All parameters are passed as named parameters:

Parameter	Commments
-----------------------------------
window		object handle to parent
		window for the widget
ypos		integer, optional,
		default is 1
xpos		integer, optional,
		default is 1
date_disp	reference
border		named colour, optional
		default is 'red'
function	reference, optional
draw_only	integer, optional
		default is 0

'date_disp' is an array reference that holds the desired date to display (in day, month, year format). If date_disp is not passed (or an empty list reference is given instead), it will be initialised with the current date. Should the widget be called in interactive mode, the reference will be modified to display the last date navigated to by the user. The first element, [0], is the day, the second, [1], the month, and the third, [2], the year.

B<Example (non-Interactive)>

calendar( 'window'	=> $main,
	  'date_disp'	=> \@date,
	  'border'	=> 'red',
	  'draw_only'	=> 1);

B<(Interactive)>

$input = calendar( 'window'	=> $main,
		   'date_disp'	=> \@date,
		   'border'	=> 'blue',
		   'function'	=> \&clock);

msg_box

The msg_box displays the passed message in a new window that erases once acknowledged. It automatically scales and centers itself according to the console and the passed message. The 'window' argument is optional, but if passed, it will do a touchwin() and refresh() on it before exiting, restoring whatever content that window had that was obscured by the msb_box.

Parameter	Commments
-----------------------------------
window		object handle to calling
		window for the widget,
		optional
title		string, optional
message		string, optional
border		string, optional
function	reference, optional

All previously described options remain the same. It only responds to the ENTER key, space, O, or o.

B<Example>

msg_box( 'window'	=> $mwh,
	 'title'	=> "Critical Error!",
	 'message'	=> "Now, you've done it!",
	 'border'	=> "red");

Note that there is a minimum needed console size for this to work, which is currently 5 rows by 14 columns. If the console size is at least that size, the message box will render. Also note, though, that both the message and the title may get chomped down to alloted window space, if you pass it more than it can display.

Parameter	Commments
-----------------------------------
window		object handle to calling
		window for the widget,
		optional
title		string, optional
prompt		string, optional
border		string, optional
function	reference, optional

This widget requires a minimum console size for this to work, which is 8 rows by 24 columns. Both the title and the prompt may be chomped to accomodate available screen space.

B<Example>

($field, $button) = input_box( 'window'		=> $mwh,
			       'title'		=> 'Password',
			       'prompt'		=> 'Enter Password:',
			       'border'		=> 'blue');

input_box

The input_box displays a dialog box with a prompt, a one-line input field, and a two buttons, OK and CANCEL. Like the msg_box, this widget automatically scales and centers itself according to the prompt, and the 'window' argument is optional.

Unlike the msg_box, however, this widget returns two values; the first being the value of the text field, the second being a 1 if the OK button was pressed, or a 0 if the CANCEL button was pressed. Hitting ENTER while in the text field is a shortcut for pressing the OK button.

FUNCTIONS

select_colour

Usage: select_colour($window, foreground [, background])

This function sets the character attributes for all subsequent characters to the specified colour, for the specified window. The first two arguments are required, the first being an object handle to the window, and the second a string denoting the desired foreground colour. A background colour can also be given, but if not, it defaults to black.

Valid colours are black, cyan, green, magenta, red, white, blue, and yellow. All attributes stay in effect until another set is declared, or all attributes are reset via attrset(0).

B<Example>

select_colour($main, 'yellow');

line_split (not exported by default)

Usage: line_split(string, line_length)

This function returns the submitted string as a list, each element being a separate line. It accounts for not only column limits, but whitespace as well, splitting a sentence by whitespace, so as to not break words.

B<Example>

@lines = line_split($note, 80);

grab_key (not exported by default)

Usage: grab_key($wh [, \&func_ref])

This function returns the pressed key, calling the passed function reference while waiting.

Only the first argument is mandatory, that being the object handle for the window gathering the key strokes. The function reference passed will be called while waiting for a key to pressed, but only works if you've initialised the console for half-blocking mode. Ie., to call that function every half a second:

halfdelay(5);

HISTORY

See the Changelog for in depth change history. So far, I haven't broken any of the default exported functions, so most scripts should run unmodified.

Significant changes:

Unix cal no longer needed. Cal output is now generated internally, using modified code provided courtesy of Michael E. Schechter, <mschechter@earthlink.net>.

export tags defined. By default, :standard is the set imported, but now :functions and :all are now allowed as well.

init_colours deprecated in favour of automatic allocation of color pairs by the select_colour function. While the memory savings are minor, colour pairs are only allocated as used, and done automatically, so no pre-allocation is necessary.

AUTHOR

All bug reports, gripes, adulations, and comments can be sent to Arthur Corliss, at corliss@odinicfoundation.org.