Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _cf53c47e18e0c8386628b0b07a850c74 < prev next >

Wrap

Text File | 2000-03-23 | 12KB | 242 lines

<HTML> <HEAD> <TITLE>option - Using the option database in Perl/Tk</TITLE> <LINK REL="stylesheet" HREF="../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> option - Using the option database in Perl/Tk </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <UL> <LI><A HREF="#being a good citizen">Being a good citizen</A></LI> <LI><A HREF="#option rules and widget identification">Option rules and widget identification</A></LI> </UL> <LI><A HREF="#methods">METHODS</A></LI> <LI><A HREF="#bugs">BUGS</A></LI> <LI><A HREF="#see also">SEE ALSO</A></LI> <LI><A HREF="#keywords">KEYWORDS</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> option - Using the option database in Perl/Tk <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Linux</LI> <LI>Solaris</LI> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> $widget->widgetClass(Name=>name, -class=>class); $widget->PathName; $widget->optionAdd(pattern=>value ?,priority?); $widget->optionClear; $widget->optionGet(name, class); $widget->optionReadfile(fileName ?,priority?); <HR> <H1><A NAME="description">DESCRIPTION</A></H1> The option database (also known as the resource database or the application defaults database) is a set of rules for applying default options to widgets. Users and system administrators can set up these rules to customize the appearance of applications without changing any application code; for example, a user might set up personal foreground and background colors, or a site might use fonts associated with visual or language preferences. Different window managers (and implementations of them) have implemented the database differently, but most Xt-based window managers use the .Xdefaults file or the xrdb utility to manage user preferences; some use both, and/or implement a more complex set of site, user and application databases. Check your site documentation for these topics or your window manager's RESOURCE_MANAGER property. <H2><A NAME="being a good citizen">Being a good citizen</A></H2> For most applications, the option database ``just works.'' The option... methods are for applications that need to do something unusual, such as add new rules or test an option's default. Even in such cases, the application should provide for user preferences. Do not hardcode widget options without a very good reason. All users have their own tastes and they are all different. They choose a special font in a special size and have often spend a lot of time working out a color scheme that they will love until death. When you respect their choices they will enjoy working with your applications much more. Don't destroy the common look and feel of a personal desktop. <H2><A NAME="option rules and widget identification">Option rules and widget identification</A></H2> All widgets in an application are identified hierarchically by pathname, starting from the MainWindow and passing through each widget used to create the endpoint. The path elements are widget names, much like the elements of a file path from the root directory to a file. The rules in the option database are patterns that are matched against a widget's pathname to determine which defaults apply. When a widget is created, the Name option can be used to assign the widget's name and thus create a distinctive path for widgets in an application. If the Name option isn't given, Perl/Tk assigns a default name based on the type of widget; a MainWindow's default name is the appname. These defaults are fine for most widgets, so don't feel you need to find a meaningful name for every widget you create. A widget must have a distinctive name to allow users to tailor its options independently of other widgets in an application. For instance, to create a Text widget that will have special options assigned to it, give it a name such as: <PRE> $text = $mw->Text(Name => 'importantText');</PRE> You can then tailor the widget's attributes with a rule in the option database such as: <PRE> *importantText*foreground: red</PRE> The class attribute identifies groups of widgets, usually within an application but also to group similar widgets among different applications. One typically assigns a class to a TopLevel or Frame so that the class will apply to all of that widget's children. To extend the example, we could be more specific about the importantText widget by giving its frame a class: <PRE> $frame = $mw->Frame(-class => 'Urgent'); $text = $frame->Text(Name => 'importantText');</PRE> Then the resource pattern can be specified as so: <PRE> *Urgent*importantText*foreground: red</PRE> Similarly, the pattern <CODE>*Urgent*background: cyan</CODE> would apply to all widgets in the frame. <HR> <H1><A NAME="methods">METHODS</A></H1> <DL> <DT><A NAME="item_widgetClass">$widget->widgetClass(Name=>name, -class=>class);</A> <DD> Identify a new widget with name and/or class. Name specifies the path element for the widget; names generally begin with a lowercase letter. -class specifies the class for the widget and its children; classes generally begin with an uppercase letter. If not specified, Perl/Tk will assign a unique default name to each widget. Only MainWindow widgets have a default class, made by uppercasing the first letter of the application name. <DT><A NAME="item_PathName">$widget->PathName;</A> <DD> The PathName method returns the widget's pathname, which uniquely identifies the widget within the application. <DT><A NAME="item_optionAdd">$widget->optionAdd(pattern=>value ?, priority?);</A> <DD> The optionAdd method adds a new option to the database. Pattern contains the option being specified, and consists of names and/or classes separated by asterisks or dots, in the usual X format. Value contains a text string to associate with pattern; this is the value that will be returned in calls to the optionGet method. If priority is specified, it indicates the priority level for this option (see below for legal values); it defaults to interactive. This method always returns an empty string. <DT><A NAME="item_optionClear">$widget->optionClear;</A> <DD> The optionClear method clears the option database. Default options (from the RESOURCE_MANAGER property or the .Xdefaults file) will be reloaded automatically the next time an option is added to the database or removed from it. This method always returns an empty string. <DT><A NAME="item_optionGet">$widget->optionGet(name,class);</A> <DD> The optionGet method returns the value of the option specified for $widget under name and class. To look up the option, optionGet matches the patterns in the resource database against $widget's pathname along with the class of $widget (or its parent if $widget has no class specified). The widget's class and name are options set when the widget is created (not related to class in the sense of <A HREF="../../../lib/Pod/perlfunc.html#item_bless">bless</A>); the MainWindow's name is the appname and its class is (by default) derived from the name of the script. If several entries in the option database match $widget's pathname, name, and class, then the method returns whichever was created with highest priority level. If there are several matching entries at the same priority level, then it returns whichever entry was most recently entered into the option database. If there are no matching entries, then the empty string is returned. <DT><A NAME="item_optionReadfile">$widget->optionReadfile(fileName?,priority?);</A> <DD> The optionReadfile method reads fileName, which should have the standard format for an X resource database such as .Xdefaults, and adds all the options specified in that file to the option database. If priority is specified, it indicates the priority level at which to enter the options; priority defaults to interactive. The priority arguments to the option methods are normally specified symbolically using one of the following values: <DL> <DT><A NAME="item_widgetDefault">widgetDefault</A> <DD> Level 20. Used for default values hard-coded into widgets. <DT><A NAME="item_startupFile">startupFile</A> <DD> Level 40. Used for options specified in application-specific startup files. <DT><A NAME="item_userDefault">userDefault</A> <DD> Level 60. Used for options specified in user-specific defaults files, such as .Xdefaults, resource databases loaded into the X server, or user-specific startup files. <DT><A NAME="item_interactive">interactive</A> <DD> Level 80. Used for options specified interactively after the application starts running. If priority isn't specified, it defaults to this level. </DL> Any of the above keywords may be abbreviated. In addition, priorities may be specified numerically using integers between 0 and 100, inclusive. The numeric form is probably a bad idea except for new priority levels other than the ones given above. </DL> <HR> <H1><A NAME="bugs">BUGS</A></H1> The priority scheme used by core Tk is not the same as used by normal Xlib routines. In particular is assumes that the order of the entries is defined, but user commands like xrdb -merge can change the order. <HR> <H1><A NAME="see also">SEE ALSO</A></H1> <A HREF="../../../site/lib/Tk/Xrm.html">Tk::Xrm</A> <HR> <H1><A NAME="keywords">KEYWORDS</A></H1> database, option, priority, retrieve <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> option - Using the option database in Perl/Tk </TD></TR> </TABLE> </BODY> </HTML>