Initial commit of OpenSPARC T2 design and verification files.

[OpenSPARC-T2-DV] / tools / perl-5.8.0 / man / man3 / Tk::UserGuide.3

.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sh \" Subsection heading
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  | will give a
.\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
.\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.tr \(*W-|\(bv\*(Tr
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.if \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.\"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.hy 0
.if n .na
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "USERGUIDE 1"
.TH USERGUIDE 1 "2000-12-30" "perl v5.8.0" "User Contributed Perl Documentation"
.SH "NAME"
perl/Tk \- Writing Tk applications in perl5.
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
This manual page is for beginners.  It assumes you know some perl,
and have got perl+Tk running.
Please run the 'widget' demo before reading this text; it will teach you
the various widget types supported by Tk.
.SH "Some background"
.IX Header "Some background"
Tk \s-1GUI\s0 programming is event\-driven.  (This may already be familiar to you.)
In event-driven programs, the main \s-1GUI\s0 loop is outside of the user program
and inside the \s-1GUI\s0 library.  This loop will watch all events of interest,
and activate the correct handler procedures to handle these events.
Some of these handler procedures may be user\-supplied; others will be part
of the library.
.PP
For a programmer, this means that you're not watching what is happening;
instead, you are requested by the toolkit to perform actions whenever
necessary.
So, you're not watching for 'raise window / close window / redraw window'
requests, but you tell the toolkit which routine will handle such cases,
and the toolkit will call the procedures when required.
.SH "First requirements"
.IX Header "First requirements"
Any perl program that uses Tk needs to include \f(CW\*(C`use Tk\*(C'\fR.
A program should also use \f(CW\*(C`use strict\*(C'\fR and the \fB\-w\fR switch to ensure
the program is working without common errors.
.PP
Any Tk application starts by creating the Tk main window.  You then create
items inside the main window, or create new windows, before starting the
mainloop.
(You can also create more items and windows while you're running.)
The items will be shown on the display after you \f(CW\*(C`pack\*(C'\fR them;
more info on this later.
Then you do a Tk mainloop; this will start the \s-1GUI\s0 and handle all events.
That's your application.
A trivial one-window example is show below:
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 2
\&        use strict;
\&        use Tk;
.Ve
.PP
.Vb 6
\&        my $main = MainWindow->new;
\&        $main->Label(-text => 'Hello, world!')->pack;
\&        $main->Button(-text => 'Quit',
\&                      -command => [$main => 'destroy']
\&                      )->pack;
\&        MainLoop;
.Ve
.PP
Please run this example.  It shows you two items types also shown in the
widget demo; it also shows you how items are created and packed.
Finally, note the typical Tk style using \f(CW\*(C`\-option\*(C'\fR => \f(CW\*(C`value\*(C'\fR pairs.
.SH "Item creation"
.IX Header "Item creation"
Tk windows and widgets are hierarchical, i.e.\ one includes one or more
others.  You create the first Tk window using \f(CW\*(C`MainWindow\->new\*(C'\fR.
This returns a window handle, assigned to \f(CW$main\fR in the example above.
Keep track of the main handle.
.PP
You can use any Tk handle to create sub-items within the window or widget.
This is done by calling the Tk constructor method on the variable.
In the example above, the \f(CW\*(C`Label\*(C'\fR method called from \f(CW$main\fR creates a
label widget inside the main window.  In the constructor call, you can specify
various options; you can later add or change options for any widget
using the \f(CW\*(C`configure\*(C'\fR method, which takes the same parameters as the
constructor.
The one exception to the hierarchical structure is the \f(CW\*(C`Toplevel\*(C'\fR constructor,
which creates a new outermost window.
.PP
After you create any widget, you must render it by calling \f(CW\*(C`pack\*(C'\fR.  (This
is not entirely true; more info later).  If you do not need to refer to
the widget after construction and packing, call \f(CW\*(C`pack\*(C'\fR off the constructor
results, as shown for the label and button in the example above.
Note that the result of the compound call is the result of \f(CW\*(C`pack\*(C'\fR,
which is a valid Tk handle.
.PP
Windows and widgets are deleted by calling \f(CW\*(C`destroy\*(C'\fR on them;
this will delete and un-draw the widget and all its children.
.SH "Standard Tk types"
.IX Header "Standard Tk types"
.IP "Button" 4
.IX Item "Button"
.PD 0
.IP "Radiobutton" 4
.IX Item "Radiobutton"
.IP "Checkbutton" 4
.IX Item "Checkbutton"
.IP "Listbox" 4
.IX Item "Listbox"
.IP "Scrollbar" 4
.IX Item "Scrollbar"
.IP "Entry" 4
.IX Item "Entry"
.IP "Text" 4
.IX Item "Text"
.IP "Canvas" 4
.IX Item "Canvas"
.IP "Frame" 4
.IX Item "Frame"
.IP "Toplevel" 4
.IX Item "Toplevel"
.IP "Scale" 4
.IX Item "Scale"
.IP "Menu" 4
.IX Item "Menu"
.IP "Menubutton" 4
.IX Item "Menubutton"
.PD
.SH "Variables and callback routines"
.IX Header "Variables and callback routines"
Most graphical interfaces are used to set up a set of values and conditions,
and then perform the appropriate action.  The Tk toolkit is different
from your average text-based prompting or menu driven system in that you do
not collect settings yourself, and decide on an action based on an
input code; instead, you leave these
values to your toolkit and only get them when the action is performed.
.PP
So, where a traditional text-based system would look like this:
(yes, this is obviously dumb code)
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 1
\&        use strict;
.Ve
.PP
.Vb 3
\&        print "Please type a font name\en";
\&        my $font = <>; chomp $font;
\&        # Validate font
.Ve
.PP
.Vb 3
\&        print "Please type a file name\en";
\&        my $filename = <>; chomp $filename;
\&        # Validate filename
.Ve
.PP
.Vb 7
\&        print "Type <1> to fax, <2> to print\en";
\&        my $option = <>; chomp $option;
\&        if ($option eq 1) {
\&            print "Faxing $filename in font $font\en";
\&        } elsif ($option eq 2) {
\&            print "Now sending $filename to printer in font $font\en";
\&        }
.Ve
.PP
The (slightly larger) example below shows how to do this is Tk.
Note the use of callbacks.  Note, also, that Tk handles the values, and
the subroutine uses \f(CW\*(C`get\*(C'\fR to get at the values.
If a user changes his mind and wants to change the font again,
the application never notices; it's all handled by Tk.
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 2
\&        use strict;
\&        use Tk;
.Ve
.PP
.Vb 13
\&        my $main = MainWindow->new;
\&        $main->Label(-text => 'Print file')->pack;
\&        my $font = $main->Entry(-width => 10);
\&        $font->pack;
\&        my $filename = $main->Entry(-width => 10);
\&        $filename->pack;
\&        $main->Button(-text => 'Fax',
\&                      -command => sub{do_fax($filename, $font)}
\&                      )->pack;
\&        $main->Button(-text => 'Print',
\&                      -command => sub{do_print($filename, $font)}
\&                      )->pack;
\&        MainLoop;
.Ve
.PP
.Vb 6
\&        sub do_fax {
\&            my ($file, $font) = @_;
\&            my $file_val = $file->get;
\&            my $font_val = $font->get;
\&            print "Now faxing $file_val in $font_val\en";
\&        }
.Ve
.PP
.Vb 6
\&        sub do_print {
\&            my ($file, $font) = @_;
\&            my $file_val = $file->get;
\&            my $font_val = $font->get;
\&            print "Sending file $file_val to printer in $font_val\en";
\&        }
.Ve
.SH "The packer.  Grouping and frames."
.IX Header "The packer.  Grouping and frames."
In the examples above, you must have noticed the pack calls.
This is one of the more complicated parts of Tk.  The basic idea
is that any window or widget should be subject to a Tk widget placement manager;
the \fIpacker\fR is one of the placement managers.
.PP
The actions of the packer are rather simple: when applied
to a widget, the packer positions that widget on the indicated position
within the remaining space in its parent.  By default, the position is
on top; this means the next items will be put below.  You can also
specify the left, right, or bottom positions.  Specify position
using \fB\-side => 'right'\fR.
.PP
Additional packing parameters specify the behavior of the widget when
there is some space left in the frame or when the window size is
increased.  If widgets should maintain a fixed size, specify nothing;
this is the default.  For widgets that you want to fill up the current
horizontal space, specify \fB\-fill => 'x'\fR, \fBy\fR, or \fBboth\fR; for
widgets that should grow, specify \fB\-expand => 1\fR.  These
parameters are not shown in the example below; see the widget demo.
.PP
If you want to group some items within a window that have a different
packing order than others, you can include them in a Frame.  This is a
do-nothing window type that is meant for packing (and to play games
with borders and colors).
.PP
The example below shows the use of pack and frames:
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 2
\&        use strict;
\&        use Tk;
.Ve
.PP
.Vb 5
\&        # Take top, the bottom -> now implicit top is in the middle
\&        my $main = MainWindow->new;
\&        $main->Label(-text => 'At the top (default)')->pack;
\&        $main->Label(-text => 'At the bottom')->pack(-side => 'bottom');
\&        $main->Label(-text => 'The middle remains')->pack;
.Ve
.PP
.Vb 5
\&        # Since left and right are taken, bottom will not work...
\&        my $top1 = $main->Toplevel;
\&        $top1->Label(-text => 'Left')->pack(-side => 'left');
\&        $top1->Label(-text => 'Right')->pack(-side => 'right');
\&        $top1->Label(-text => '?Bottom?')->pack(-side => 'bottom');
.Ve
.PP
.Vb 7
\&        # But when you use frames, things work quite alright
\&        my $top2 = $main->Toplevel;
\&        my $frame = $top2->Frame;
\&        $frame->pack;
\&        $frame->Label(-text => 'Left2')->pack(-side => 'left');
\&        $frame->Label(-text => 'Right2')->pack(-side => 'right');
\&        $top2->Label(-text => 'Bottom2')->pack(-side => 'bottom');
.Ve
.PP
.Vb 1
\&        MainLoop;
.Ve
.SH "More than one window"
.IX Header "More than one window"
Most real applications require more than one window.  As you read before,
you can create more outermost windows by using Toplevel.  Each window
is independent; destroying a toplevel window does not affect the others as
long as they are not a child of the closed toplevel.
Exiting the main window will end the application.
The example below shows a trivial three-window application:
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 2
\&        use strict;
\&        use Tk;
.Ve
.PP
.Vb 7
\&        my $main = MainWindow->new;
\&        fill_window($main, 'Main');
\&        my $top1 = $main->Toplevel;
\&        fill_window($top1, 'First top-level');
\&        my $top2 = $main->Toplevel;
\&        fill_window($top2, 'Second top-level');
\&        MainLoop;
.Ve
.PP
.Vb 10
\&        sub fill_window {
\&            my ($window, $header) = @_;
\&            $window->Label(-text => $header)->pack;
\&            $window->Button(-text => 'close',
\&                            -command => [$window => 'destroy']
\&                            )->pack(-side => 'left');
\&            $window->Button(-text => 'exit',
\&                            -command => [$main => 'destroy']
\&                            )->pack(-side => 'right');
\&        }
.Ve
.SH "More callbacks"
.IX Header "More callbacks"
So far, all callback routines shown called a user procedure.
You can also have a callback routine call another Tk routine.
This is the way that scroll bars are implemented: scroll-bars
can call a Tk item or a user procedure, whenever their position
has changed.  The Tk item that has a scrollbar attached calls the
scrollbar when its size or offset has changed.  In this way,
the items are linked.  You can still ask a scrollbar's position,
or set it by hand \- but the defaults will be taken care of.
.PP
The example below shows a listbox with a scroll bar.  Moving
the scrollbar moves the listbox.  Scanning a listbox (dragging
an item with the left mouse button) moves the scrollbar.
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 2
\&        use strict;
\&        use Tk;
.Ve
.PP
.Vb 14
\&        my $main = MainWindow->new;
\&        my $box = $main->Listbox(-relief => 'sunken',
\&                                 -width => -1, # Shrink to fit
\&                                 -height => 5,
\&                                 -setgrid => 1);
\&        my @items = qw(One Two Three Four Five Six Seven
\&                       Eight Nine Ten Eleven Twelve);
\&        foreach (@items) {
\&           $box->insert('end', $_);
\&        }
\&        my $scroll = $main->Scrollbar(-command => ['yview', $box]);
\&        $box->configure(-yscrollcommand => ['set', $scroll]);
\&        $box->pack(-side => 'left', -fill => 'both', -expand => 1);
\&        $scroll->pack(-side => 'right', -fill => 'y');
.Ve
.PP
.Vb 1
\&        MainLoop;
.Ve
.SH "Canvases and tags"
.IX Header "Canvases and tags"
One of the most powerful window types in Tk is the Canvas window.
In a canvas window, you can draw simple graphics and include
other widgets.  The canvas area may be larger than the visible window,
and may then be scrolled.  Any item you draw on the canvas has its own id,
and may optionally have one or more \fItags\fR.  You may refer to any
item by its id, and may refer to any group of items by a common tag;
you can move, delete, or change groups of items using these tags,
and you can \fIbind\fR actions to tags.  For a properly designed (often
structured) canvas, you can specify powerful actions quite simply.
.PP
In the example below, actions are bound to circles (single click)
and blue items (double\-click); obviously, this can be extended to any
tag or group of tags.
.PP
.Vb 1
\&        #! /usr/bin/perl5 -w
.Ve
.PP
.Vb 2
\&        use strict;
\&        use Tk;
.Ve
.PP
.Vb 4
\&        # Create main window and canvas
\&        my $main = MainWindow->new;
\&        my $canvas = $main->Canvas;
\&        $canvas->pack(-expand => 1, -fill => 'both');
.Ve
.PP
.Vb 5
\&        # Create various items
\&        create_item($canvas, 1, 1, 'circle', 'blue', 'Jane');
\&        create_item($canvas, 4, 4, 'circle', 'red', 'Peter');
\&        create_item($canvas, 4, 1, 'square', 'blue', 'James');
\&        create_item($canvas, 1, 4, 'square', 'red', 'Patricia');
.Ve
.PP
.Vb 5
\&        # Single-clicking with left on a 'circle' item invokes a procedure
\&        $canvas->bind('circle', '<1>' => sub {handle_circle($canvas)});
\&        # Double-clicking with left on a 'blue' item invokes a procedure
\&        $canvas->bind('blue', '<Double-1>' => sub {handle_blue($canvas)});
\&        MainLoop;
.Ve
.PP
.Vb 3
\&        # Create an item; use parameters as tags (this is not a default!)
\&        sub create_item {
\&            my ($can, $x, $y, $form, $color, $name) = @_;
.Ve
.PP
.Vb 10
\&            my $x2 = $x + 1;
\&            my $y2 = $y + 1;
\&            my $kind;
\&            $kind = 'oval' if ($form eq 'circle');
\&            $kind = 'rectangle' if ($form eq 'square');
\&            $can->create(($kind, "$x" . 'c', "$y" . 'c',
\&                          "$x2" . 'c', "$y2" . 'c'),
\&                         -tags => [$form, $color, $name],
\&                         -fill => $color);
\&        }
.Ve
.PP
.Vb 16
\&        # This gets the real name (not current, blue/red, square/circle)
\&        # Note: you'll want to return a list in realistic situations...
\&        sub get_name {
\&            my ($can) = @_;
\&            my $item = $can->find('withtag', 'current');
\&            my @taglist = $can->gettags($item);
\&            my $name;
\&            foreach (@taglist) {
\&                next if ($_ eq 'current');
\&                next if ($_ eq 'red' or $_ eq 'blue');
\&                next if ($_ eq 'square' or $_ eq 'circle');
\&                $name = $_;
\&                last;
\&            }
\&            return $name;
\&        }
.Ve
.PP
.Vb 5
\&        sub handle_circle {
\&            my ($can) = @_;
\&            my $name = get_name($can);
\&            print "Action on circle $name...\en";
\&        }
.Ve
.PP
.Vb 5
\&        sub handle_blue {
\&            my ($can) = @_;
\&            my $name = get_name($can);
\&            print "Action on blue item $name...\en";
\&        }
.Ve