|
|
|
Chapter 17GUI Interfaces with Perl/Tk
CONTENTS
This chapter introduces you to using the Perl/Tk package to create graphical user interfaces (GUI) with Perl. After reading and working through the examples in this chapter, you should be able to create interactive user interfaces for your Perl scripts with very short design times. Introduction to the Perl/Tk PackageThe set of Tk modules attempts to tie the Tk widget toolkit with Perl 5. The set is referred to as Perl/Tk, pTk, or even ptk. The idea behind the merging of this set is to get the best features of both languages: Perl has very good text handling, regular expression support, dynamic memory, file and pipe I/O, and object-oriented capabilities for processing data; Tk gives you a quick and easy way to create GUI programs. Perl/Tk is most easily used on a UNIX computer platform running the X Window system. Perl/Tk does not require any of the lexical features of the Tcl scripting language. In other words, you do not have to be an expert at Tcl/Tk, but it will be in your best interest to have worked with the Tcl/Tk toolkit on its own to take the most advantage of the Perl/Tk package.This chapter will not make you a Tk expert. I assume you have a rudimentary working knowledge of Tcl/Tk programming. However, if you have never used Tcl/Tk before, now would be a good time to read the sample code for your Tcl/Tk package on your system. Here is a good starting reference book by the author of Tcl himself, Dr. John K. Ousterhout, professor at the University of California at Berkeley: Tcl and the Tk Toolkit, John K. Ousterhout, ISBN 0-201-63337-X, There is one thing to remember when reading his book: You still have to translate the Tcl/Tk scripts to Perl. The pTk library is a version of the Tk 4.0 toolkit. The library allows easier external linking and calling by Perl scripts and can be modularized. A number of composite widget extensions to the language have been written using Perl modules. Note that ptk does not necessarily refer to Perl/Tk, but could be taken to mean portable Tk; that is, portable to another language such as Perl, C, LISP, C++, and so on. It just so happens that our present work concentrates on Perl. About the Authors of the Perl/Tk PackageThe Perl/Tk package is still in beta phase and is being written primarily by Nick Ing-Simmons <Nick.Ing-Simmons@tiuk.ti.com> at Texas Instruments in Northampton, England. Mr. Nick was gracious enough to let us use his examples as the basis for the code samples in this chapter. He asked me to remind you that he is no way liable for how you use his package. He also requests that you give him credit for his authorship when you do use it. With regard to liability, he provides the following comments:
TkPerl was originally the name of a Perl 4 package that Mr. Malcolm Beattie, <mbeattie@sable.ox.ac.uk>, at Oxford University used to mesh the Tk toolkit with Perl. He also authored a Tcl module for Perl 5 with a Tcl::Tk module extension. That module allows the use of Tcl within a Perl script. You still must know both languages to get your widgets to work. I do not cover these libraries here.
A more extensive comparison of the differences between the Tkperl and the Perl/Tk code is given in the Tcl-perl.pod file that is distributed with the latest Perl/Tk package. The FAQs for Perl/Tk did provide some hints about getting the two packages to work together along with some friendly warnings about it not being very easy to do. Where Do I Get and Build Perl/Tk?At the time this book was written, the latest version was Tk-b9.01. You'll need Perl 5.002b1 or later to be able to work with the Tk-b9.01 kit. If you are like me and are skipping chapters while reading a book, don't skip the installation of Perl 5.002. There are some patches to 5.001m, but the 5.002 code will already have these patches in there. You need Perl 5.002, so install it first. You can get the toolkit from any CPAN site. Here are the sites where I found the latest versions:
ftp://ftp.cis.ufl.edu/pub/perl/CPAN/ Several more sites are listed in the FAQ and via the search results in Netscape Navigator. Try to get the package from a site that's geographically nearest you. Building the Perl/Tk package after you get it is going to take some time and effort on your part. If you get any errors, most of them will be due to the use of out-of-date libraries or the wrong version of Perl, or both. Read the following directions carefully before you begin the installation. First, unpack perl/Tk in your home directory. This will be your Tk build directory and will not corrupt any existing Perl 5 tree should something go wrong. Unzip and untar the files in this test directory. Use these commands: gunzip Tk-b9.01.tar.gz Next, create the make files. First, change the directory to the Tk/build directory, and then run the following commands to get to the directory, create the Makefiles, and create the package, respectively: cd Tk-b9.01 After you have built the files, check to see if you had any errors. It's not a good idea to take a coffee break while this builds because some error messages might not be fatal and you may have an incomplete build and not see the error messages fly by. Take note of any missing references to libraries or header files. If there were any errors due to missing make files or references to some header files, check the cc command in the make files for the directory with the offending error. Chances are that you do not have any inclusions of the pTk subdirectory header files. To help this out, try including the $(Inc) variable in the $ccCMD statement in the GNUmakefile file. You may have to do this for all the subdirectories under the Tk directory. Most of the errors I got during the build process were correctable with this inclusion. Now, test the demo programs in the ./Tk/demos directory. Not all of the demos worked on my Linux system. The major complaint concerns CreateArgs() in the Toplevel module causing too many recursive calls. You may fare better. Minor tweaking did not remove this error. Major surgery seemed too daunting a task at this stage. Basically, any demo involving dialog boxes did not work. Do not waste your time trying to get these demos to work. Here is the error message that showed this problem: Deep recursion on subroutine "CreateArgs"
Even with this annoying bug, you should be able to install and
work with the rest of the If you use the most current versions of the C++ compiler and make files, circa 1994 or later, and X11R6, you should have no problems. In case of problems, please consult the FAQ, INSTALL, or README files for your specific system.
Documentation for Perl/TkThe make install execution installs the pod files for you in nroff format. Check the perl5/Tk/ directory for the file UserGuide.pod. This file is editable and readable by humans. pod files have to be interpreted through a reformatting program such as pod2man, pod2html, or pod2latex, all of which should be in your Perl distribution. The following commands provide you with information in HTML files or in man pages: pod2man ~khusain/p5/Tk/UserGuide.pod | nroff -man | more The most visually pleasing of the three methods is the pod2html method: $ pod2html perl5/Tk/Dial.pm The output of this command is as follows (you can use Mosaic or Netscape to view the contents of this file): <!-- $Id$ --> Also in the Tk-b9.01/doc directory are some .ht files which are copyrighted HTML pages of the documentation for the package. Writing Scripts in Perl/TkThe idea behind writing the Perl/Tk script using the modules for the package is to make life easier. The scripts have to include the Tk package with the use Tk; statement. You might want to consider using the warning switch (-w) and, if you are paranoid, use the use strict; statement to do extra syntax checking. Look at the simple "Hello, world" script shown in Listing 17.1. Listing 17.1. A simple "Hello, world" script. 1 #!/usr/bin/perl -w The first line in the file starts Perl with the -w switch for warnings to be issued, if necessary. Line 5 imports the Tk objects into the application. The statement in line 6 creates the main window. The "Hello, world" and Greetings buttons are created in lines 7 and 8. In line 9, the Hello button is added to the main window. In line 10, the Greetings button is pack-ed into the main window on the left side of the Hello button. (I cover pack-ing later throughout this chapter.) Line 11 starts the main user interface loop for this application. The output is shown in Figure 17.1. Figure 17.1 :Sample "Hello, world" application. The MainLoop; statement is the main widget event handler loop and is required in all Perl/Tk scripts. This event handler statement is usually near the end of the main procedure after the widgets have been created and are ready to be displayed. In Listing 17.1, note that the Greet button defines an anonymous function (at line 8) with a call to the exit function. In line 7, the hello world function does not call the exit function.
The objects in this application are added one object at a time
in a hierarchical order. This Please note the use of the => operator, which is simply a synonym for the comma operator. The program in Listing 17.1 could be rewritten as shown in Listings 17.2 and 17.3. Listing 17.2. The "Hello, world" application using commas. 1 #!/usr/bin/perl -w Listing 17.3. The "Hello, world" application using hashes. 1 #!/usr/bin/perl -w As you can see, you have a lot of flexibility in how you write your application. If you need more information on references, please refer to Chapter 3, "References," to see why Listing 17.3 works. Widgets as Building BlocksBasically, a widget can be "created" by simply calling the new method of the class name. For example, to create a new window, you use the following statement: my $main = new MainWindow; This statement sets aside the necessary system memory, and so on for a new MainWindow widget. The MainLoop; call causes it to appear. The object "created" then can be called via the variable $main. It's a good idea to hang on to each object as it's created in the hierarchy. This way you can refer to the object explicitly should you need to change its parameters. Thus, the return values of most of your calls to create items are assigned to a variable: $mybutton = $main->Button(); Now you can use $mybutton to refer to this Button object. Configuring WidgetsWidgets are configurable to show different types of viewing styles. You can provide a number of configuration parameters via calls to the configure() function. Configuration parameters also can be sent in when the widget is created. For example, these two statements are equivalent: my $button = $main->Button(); and my $button = new $main->Button(-text => 'Hello'); The "Hello, world" application is simple enough to demonstrate the use of Button widgets in Perl/Tk. You do have access to more widgets that you can use to create your own widgets. Check the subdirectories under the Tk-b9.01 tree to see what the widgets are. The Canvas widget is in the Canvas subdirectory. The following Tk widgets are available under perl/Tk:
Each of these widgets comes with its own set of configurable parameters. As you work with these widgets you'll become familiar with the parameters associated with them. The best way to know which parameters are configurable is to check the Perl/Tk reference manuals to see what parameters are available for each type of widget. The MainWindow widget is required for your applications. This widget serves as the main window for your Perl/Tk applications. Several functions exist for use as methods for this MainWindow object. For example, to set the title in the window, use the following command: $main->title(" A sample window"); I cover some of these methods in the next few sections. Let's first see how we can place widgets on the main window. Using CheckButton WidgetsUsing check buttons is relatively easy. See Listing 17.4. The output is shown in Figure 17.2. The three buttons are shown side-by-side in the same window. If the parameters specifying the sides on the left are removed, the buttons appear as shown in Figure 17.3. You get this output by uncommenting the lines that create the buttons in Listing 17.4. Figure 17.2 :Using Check buttons. Figure 17.3 :Using check buttons without packing. Listing 17.4. Using check buttons. 1 #!/usr/bin/perl Using RadioButton WidgetsRadio buttons let you select one of many options, whereas check buttons allow you to select as many as possible. When using check buttons, you can press more than one button at a time. With radio buttons, you are showing several alternatives to an option. The value of the option is only one of several presented. You have to specify the variable option on each radio button. The value of the -variable option is the escaped global Perl variable that will be assigned the value. All related radio buttons have to be assigned the same variable. Pressing each radio button causes the value of the variable to be set. Thus, each radio button has to set the value of the variable, too, with the -value configuration parameter. See Listing 17.5 for a sample script. The output is shown in Figure 17.4. Figure 17.4 :Using radio buttons in Perl/TK scripts. Listing 17.5. Using radio buttons. 1 #!/usr/bin/perl Let's examine the new lines of code in Listing 17.5 in detail. Line 8 sets the title of the application window to Select Delicacy. Line 12 declares and sets the value of the global variable $animal to anything. Lines 13 through 16 specify the first Radiobutton with the title Yak. The variable whose value will be set when this button is pressed is specified in the -variable parameter value. Note the escaped dollar sign for the name of the variable $animal. The -command configuration parameter specifies the anonymous subroutine to call when the button is pressed. The subroutine simply prints the value of the variable. You can add your code here. In lines 17 through 20 and lines 21 through 24, two more radio buttons are specified that set the values of $animal to 'Camel' and 'Llama', respectively. Calling Subroutines When a Button Is PressedYou can add subroutines to call when a button is pressed. The examples in Listing 17.1 and 17.5 are two examples of this. You may specify the -command option in the call to create and pack the button (in Listing 17.5, this was done with lines 15, 19, and 23): -command => sub {print "$animal \n"; } , You can refer to a subroutine by using the escaped ampersand with the name of the subroutine. Any parameters that have to be passed to the subroutine have to be specified with the -command parameters as one list. For example, consider the following function which creates a button with a caption of Stats, and calls the subroutine do_print when the button is pressed: $main->Button(-text => 'Stats', Note the backslash in front of \&do_print. This causes Perl to generate a reference to sub do_print rather than call it. The input variables, $inputfile and $outputfile, are passed by reference not by value, into the do_print subroutine. Arranging the Layout of WidgetsWidgets are laid out on a window using the -pack, -padding, -fill, -expand, and -anchor options of a widget. Windows also use a program called a geometry manager in Tk. A geometry manager controls the arrangement of widgets in a window. The most common geometry manager used in pTk is pack. You have seen the use of the -pack function to place buttons on a window in earlier sections of this chapter. The pack function is also known informally as the "packer." You can invoke pack at the time of widget creation via calls like $widget->pack; where widget can be any of the Perl/Tk widget primitives. The pack function is often used in conjunction with the Frame container widget to arrange your widgets much like a hierarchically arranged set of window panes. See Listing 17.6 and Figure 17.5. Figure 17.5 :The output from Listing 17.6. Listing 17.6. Packing using frames. 1 #!/usr/bin/perl In Listing 17.6, we used two frames: one on the top and the other on the bottom. These frames are called $row1 and $row2 and are created in lines 6 through 9. Then lines 10 and 11 create the two labels in $row1, and in lines 12 and 13, two more labels are created on the second frame. In this fashion we have packed labels on frames, and the frames are then packed onto the main window. You can think of this as building a Mayan temple of sorts with widgets being placed one on top of the other. Note that pack itself is given parameters in this example. The default behavior of pack is to have -side => 'top', that is, align everything using the top edge. You can override this behavior by specifying a different packing style such as "left", "right", or "bottom". The Tk* distribution has a file called popup that uses the -anchor option to configure the layout of the Radiobutton widgets. The output of this demo is shown in Figure 17.6. Run the following program to get the listing with line numbers for reference. Figure 17.6 :Using the -anchor widget option. $ nl popup | more There is also the -anchor configuration option for widgets. There are introductions to the nine possible -anchor values, eight corresponding to the points on a compass and the ninth as the center position. The nine possible values are set around line 22 with list: foreach $r ([qw(nw n ne)],[qw(w c e)],[qw(sw s se)]) In the beginning of the file, we create a small popup window to show when a button is clicked. Rather than create this window every time, a button is created but is not shown immediately. Around lines 13 through 17, the subroutine Show shows this window and requests it to be invisible after one second. In the subroutine Anchor, a master frame is created (see line 21) with a ridge around it. Then three frames are placed on it, each with three buttons showing the anchor positions (see lines 25 through 29). The positions and the labels for the buttons are shown in line 22. When setting lots of uneven widgets on the same frame, you can make their borders the same size by using -fill => 'style'. The style can be none | x | y | both. See the modified version of the radio button application and contrast the code in Listing 17.7 with the code in Listing 17.4. The output is shown in Figure 17.7, which you can compare with Figure 17.3 to see how the buttons with their borders are now shown and resized. Figure 17.7 :Using the -fill option. Listing 17.7. Using the -fill option. 1 #!/usr/bin/perl When laying out your widgets, look at their behavior with multiple resize operations. The -expand option of either pack or the widget itself can be used to set whether the widget expands or shrinks with its parent. Add the statement for packing the buttons in Listing 17.8; the buttons will shrink or expand as the main window is resized. Listing 17.8. Using the Expand button. 1 $main->Checkbutton(-text => 'One', The output of this change to Listing 17.7 is shown in Figure 17.8. Remember to make this change to all the pack calls for the buttons. Figure 17.8 :Using the -expend option.
Using the Listbox and Scrollbar WidgetsNow that you know how to place items on a frame widget, let's see how you create a list of scrollable items. For this exercise, you'll use the Listbox and Scrollbar widgets. The output we are trying to get is shown in Figure 17.9. The code to get this output is shown in Listing 17.9. Figure 17.9 :Using the Listbox and Scrollbar widgers.
Listing 17.9. Using the Listbox and Scrollbar widgets. 1 #!/usr/bin/perl Scrollbars are commonly used to update the items shown in Listbox, Canvas, or Text widgets when the slider of the scrollbar is moved by the user. In Listing 17.9 (line 24), the scrollbar is created with the yview option. For a horizontal scrollbar, use the xview option. In line 29, the listbox is tied to the scrollbar to perform the scrolling action in the y direction. Note also how the label, Listbox, and Scrollbar are packed in the window. Had the -fill option not been used, the widgets would not be shown in the entire height or width of the window. To allow more than one listbox to contain a "selection" (or at least a highlighted item), specify this configuration option: -exportselection => 0 Using Text WidgetsThe Text widget is simply a widget that enables user entry. The default way to create a Text widget is shown here: #!/usr/bin/perl -w Note that the default size of a Text widget is very big for most screens. You might want to limit the size with the -height and -width options to set the same size. The values are given in the number of characters, not the number of pixels. Using the code in the Scrollbar and Listbox examples, you can attach scrollbars to create fairly sophisticated editors very quickly using Perl/Tk. Specifying Fonts for Text and Other WidgetsTo specify the font configuration option of your widget, use the -font option. See the following example: my $mw = MainWindow->new(); The 'fixed' value is the name of the font. You can check your fonts.alias file for more font names to use or look at the output from the xlsfont command. Text Entry WidgetsYou want to call the get() function on the return value of the widget itself. Here is how it may be used in a simplified version of Example 1.1 from the Tk::UserGuide, where a Button is set up to call a sub where the call to get lies. Check the POD file, UserGuide.pod, in the distribution for more information. The output is shown in Figure 17.10. Figure 17.10 :Using the Text Entry widget. Listing 17.10. Using the Text Entry widget. 1 #!/usr/bin/perl -w For collecting passwords, set the value of the -show option to zero: (-show => 0); Handling the Keyboard with Key BindingsUsing the pointer interface is not the only way to collect input in your Perl/Tk programs. There are many default key bindings built into the widgets of Perl/Tk. Making proper use of them often involves setting up the right callback. Read the documentation in BindTable.pod in the Tk package for more detailed help with this subject. The way to bind a key to a widget is to use $widget -> bind('<keyname>' => action); where $widget is the object to which the keys are bound. For global bindings you have to bind to <All>. For specific bindings you need to bind to each widget. Use the following script on each .pm file for which you want to find key bindings: #!/usr/bin/perl When run on the Listbox.pm file, this script reveals a lot of key bindings. Some modules even show <HANDLE> and <ARGV>, so you have to know what to ignore. Also, bound keys are inherited, so listing one module's bindings may not be complete if any properties are inherited from other sources. The output from the Listbox.pm file is as follows: <1>
Listing 17.11 illustrates how to read the button and key bindings from Xevents. Listing 17.11. A sample key bindings display program. 1 #!/usr/bin/perl -w Displaying a BitmapTo display .xbm bitmaps on your widgets, use the -bitmap configuration option. Typically, -bitmap options are used with Label, Frame, Button, and other types of widgets. Canvas widgets have to be treated differently. See the section on "The Canvas Widget" later in this chapter. To specify a bitmap, use the -bitmap option as follows: $main->Button(-bitmap => 'hourglass')->pack; The names of the bitmaps built into Tk are gray50, hourglass, info, question, questhead, and warning. In order to use some of the bitmaps outside the package, you need to specify a full pathname like this: $main->Label(-bitmap => "\@$tk_library/demos/cartoons")->pack; You have to use the escape (\@) with the directory specification. If you wanted to specify a file called mailbox.xbm in the directory where you were running the script, then either of the following two commands should work: $main->Label(-bitmap => '@mailbox.xbm')->pack;
If no explicit pathname is given, the directory is assumed to
exist in the current working $main->Label(-bitmap => "\@/dirty/pix/filth.xbm")->pack; Displaying Images with PhotoThe Photo method in main lets you place GIF images on a button or label. The type supported by Photo is called 'imggif'. See Listing 17.12 and Figure 17.11 for how to use this feature. Figure 17.11 :Using images in labels. Listing 17.12. Using images in labels. 1 #!/usr/bin/perl -w The following formats and file extensions are supported: X11 bitmaps (.xbm), X pixmaps (.xpm), and the graphics interchange format (.gif). There are several demos in the Tk package and on CPAN sites. MenusThe Perl/Tk package gives excellent support for menus. The demo program that comes with the package itself is a great example. I wish I knew the author of this program because I have not found a neater menu usage demonstration elsewhere. Run nl on it to get line numbers and a listing for yourself. The program is not listed here. Check the Tk-b9.01/demos/tom file. This program demonstrates the following items with sample code referred to by line numbers:
To get tear-off menus, use the -tearoff option with a value of 0 in the configuration option of the menu: my $mb = $parent->Menubutton(...); # The button You can use the demo program as the basis for your applications using menus. The basic concepts are easy to pick up once you see the syntax in operation. The Canvas WidgetThe Canvas widget is the most configurable and versatile of the widgets. You use the Canvas widget to draw on. To get the size of a Canvas widget after it has been resized, use the $canvas ->Width; and $canvas->Height; calls to get the width and height, respectively. To get the default size of the canvas when it was created, use the $canvas->cget(-width); and $canvas->cget(-height); calls. If you want your Canvas to be able to grow to arbitrarily large sizes, be sure to specify the -expand and -fill options when you ->pack the Canvas. Unlike other Tk widgets, the Canvas widget does not take the -bitmap configuration option. One of the ways to place things (including bitmaps) onto a Canvas is to call create() on it. Let's see how a Canvas handles bitmaps differently from the configurable widgets. First, assume that you wanted to specify the 'hourglass' built-in bitmap in Listing 17.13. Listing 17.13. Using a bitmap. 1 #!/usr/bin/perl To erase an item like a bitmap, call delete() on it. Assuming your Canvas tag is $cv and your bitmap is stored in $bm, then the call would be this: $cv->delete($bm); This is, of course, useful in a callback. For example, to configure a Button to do your deletion for you, you could use something like this: $mw->Button(-text => 'Erase',
A Canvas widget also can
be used as a geometry manager, because you have to specify a position
for all the items on the Canvas
widget. The x=10 and y=10
parameters in the sample specify the screen pixel location from
the upper-left of the canvas. Other possible units are shown in
Table 17.1.
Just as for the other widget types, there is a two-step process of first getting a Photo handle on the file of interest. See Listing 17.14. Make sure you have a GIF file in your current directory and change the listing to use the name of that file, or else all you'll see is a blank screen. Listing 17.14. Using Photo and Canvas together. 1 #!/usr/bin/perl -w The following types of images can be used in $canvar->create calls:
Miscellaneous TopicsThe following sections are miscellaneous topics about using Perl/Tk that are gleaned from FAQs, news messages, and .pod files. Each topic could not fit in sequence in the chapter but has enough information in it to merit its inclusion. References with SubroutinesEverything in Tk-land is a reference. Always pass variables by reference. Callbacks are closures; therefore, if you do not pass by reference, then the value of the variables in the subroutine will be the value when defined, not when called. Changing the CursorTo change the cursor for an application, you have to use the -cursor option with four values. Here are these values:
The Tk/demos/color_editor uses the following sequence to get the cursor: #!/usr/local/bin/perl -w Debugging Your Perl/Tk ScriptsUnfortunately, you are stuck with the use of the -w switch and use strict; statements since they provide informative error messages. A debugger is available at ftp://ftp.perl.com/pub/perl/ext/TK/Tkperldb-a1.tar.gz; however, at the time of this writing, I could not get it to work. Perhaps in some time this debugger will be functional. See chapter 30, "Using the Perl Debugger." More Than One Input File HandleAs with Perl's select() system call, you can monitor more than one task with Perl/Tk. For example, if you have a GUI monitor program that manages input from a variety of sources for display, you can use the fileevent() function call. Basically, a parent process creates several child processes, each with its own pipe. Process-specific information flows through a one-way pipe from each child to the parent. To achieve this, set up the following statement in the parent loop for each pipe: $main->fileevent(FILEHANDLE,$status,\&subroutine); This causes pTk to monitor the FILEHANDLE and call 'subroutine' when an event happens on that handle. In this case, FILEHANDLE is the handle to the socket or pipe you are waiting on. The value of status could be readable, writable, or exception. The \&subroutine is a reference to a Perl subroutine to call when the select() call is invoked. Eliminating and Hiding WindowsIf you are trying to eliminate a TopLevel or a MainWindow, try this: $main -> destroy; If you would rather not use destroy, then try this: $main->withdraw; # remove If $w is a subwindow (subwidget), then $w->packForget; # remove - if packed You can also call the following function to make a window invisible: $widget->UnmapWindow; Creating More Than One Independent WindowYou can create more than one window to do your user interface for you. The following example creates two separate windows, both of which are empty. You can add widgets to each window by using the $mw and $top1 widgets. See Listing 17.15. Listing 17.15. More than one independent window. 1 #!/usr/bin/perl When running this script, be careful to note which window pops up first. The first window up gets the focus in its widget. To make a Toplevel window active, call grab. Try this call after creating the widgets to grab the focus for your window: $top1->grab(grab_option); SummaryThis chapter has been a whirlwind tour of the Perl/Tk package. Hopefully, this chapter provided you with enough information to write your own GUI scripts or to get you started at the least. The package really deserves more than one chapter-I am sure that I have not even covered some of the basic functionality. Given the information in this chapter, you should know where to look. Finally, check out the man pages that came with the package, the newsgroups, and the CPAN sites for more up-to-date information. Good luck.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
With any suggestions or questions please feel free to contact us | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
