diff options
author | dkf <dkf@noemail.net> | 2009-08-06 12:46:06 (GMT) |
---|---|---|
committer | dkf <dkf@noemail.net> | 2009-08-06 12:46:06 (GMT) |
commit | 9a1efbe07011b0d26c66dd567874550f239f6147 (patch) | |
tree | 548dfb32b242afbd5d7925c21614d3341da62b03 /doc/loadTk.n | |
parent | 2a01ed742df89a099792485254b61700a8ddb399 (diff) | |
download | tk-9a1efbe07011b0d26c66dd567874550f239f6147.zip tk-9a1efbe07011b0d26c66dd567874550f239f6147.tar.gz tk-9a1efbe07011b0d26c66dd567874550f239f6147.tar.bz2 |
Small updates for minor issues
FossilOrigin-Name: ecf381512efd72ce3a73ccbe41c37eb3fac34bc2
Diffstat (limited to 'doc/loadTk.n')
-rw-r--r-- | doc/loadTk.n | 75 |
1 files changed, 34 insertions, 41 deletions
diff --git a/doc/loadTk.n b/doc/loadTk.n index 40fa2d5..becc7ae 100644 --- a/doc/loadTk.n +++ b/doc/loadTk.n @@ -4,7 +4,7 @@ '\" See the file "license.terms" for information on usage and redistribution '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES. '\" -'\" RCS: @(#) $Id: loadTk.n,v 1.13 2008/06/30 22:57:03 dkf Exp $ +'\" RCS: @(#) $Id: loadTk.n,v 1.14 2009/08/06 12:46:07 dkf Exp $ '\" .so man.macros .TH "Safe Tk" n 8.0 Tk "Tk Built-In Commands" @@ -16,34 +16,31 @@ loadTk \- Load Tk into a safe interpreter. \fB::safe::loadTk \fIslave\fR ?\fB\-use\fR \fIwindowId\fR? ?\fB\-display\fR \fIdisplayName\fR? .BE .SH DESCRIPTION -Safe Tk is based on Safe Tcl, which provides a mechanism -that allows restricted and mediated -access to auto-loading and packages for safe interpreters. -Safe Tk adds the ability to configure the interpreter -for safe Tk operations and load Tk into safe -interpreters. .PP -The \fB::safe::loadTk\fR command initializes the required data structures -in the named safe interpreter and then loads Tk into it. -The interpreter must have been created with \fB::safe::interpCreate\fR -or have been initialized with \fB::safe::interpInit\fR. -The command returns the name of the safe interpreter. -If \fB\-use\fR is specified, the window identified by the specified system -dependent identifier \fIwindowId\fR is used to contain the +Safe Tk is based on Safe Tcl, which provides a mechanism that allows +restricted and mediated access to auto-loading and packages for safe +interpreters. Safe Tk adds the ability to configure the interpreter for safe +Tk operations and load Tk into safe interpreters. +.PP +The \fB::safe::loadTk\fR command initializes the required data structures in +the named safe interpreter and then loads Tk into it. The interpreter must +have been created with \fB::safe::interpCreate\fR or have been initialized +with \fB::safe::interpInit\fR. The command returns the name of the safe +interpreter. If \fB\-use\fR is specified, the window identified by the +specified system dependent identifier \fIwindowId\fR is used to contain the .QW . -window of the safe interpreter; it can be any valid id, eventually -referencing a window belonging to another application. As a convenience, -if the window you plan to use is a Tk Window of the application you -can use the window name (e.g. \fB.x.y\fR) instead of its window Id -(\fB[winfo id .x.y]\fR). -When \fB\-use\fR is not specified, -a new toplevel window is created for the +window of the safe interpreter; it can be any valid id, eventually referencing +a window belonging to another application. As a convenience, if the window you +plan to use is a Tk Window of the application you can use the window name +(e.g., +.QW \fB.x.y\fR ) +instead of its window Id (e.g., +.QW \fB[winfo id .x.y]\fR ). +When \fB\-use\fR is not specified, a new toplevel window is created for the .QW . -window of -the safe interpreter. On X11 if you want the embedded window -to use another display than the default one, specify it with -\fB\-display\fR. -See the \fBSECURITY ISSUES\fR section below for implementation details. +window of the safe interpreter. On X11 if you want the embedded window to use +another display than the default one, specify it with \fB\-display\fR. See +the \fBSECURITY ISSUES\fR section below for implementation details. .SH "SECURITY ISSUES" .PP Please read the \fBsafe\fR manual page for Tcl to learn about the basic @@ -53,26 +50,22 @@ security considerations for Safe Tcl. interpreter to the virtual access path of the safe interpreter so that auto-loading will work in the safe interpreter. .PP +Tk initialization is now safe with respect to not trusting the slave's state +for startup. \fB::safe::loadTk\fR registers the slave's name so when the Tk +initialization (\fBTk_SafeInit\fR) is called and in turn calls the master's +\fB::safe::InitTk\fR it will return the desired \fBargv\fR equivalent +(\fB\-use\fR \fIwindowId\fR, correct \fB\-display\fR, etc.) .PP -Tk initialization is now safe with respect to not trusting -the slave's state for startup. \fB::safe::loadTk\fR -registers the slave's name so -when the Tk initialization (\fBTk_SafeInit\fR) is called -and in turn calls the master's \fB::safe::InitTk\fR it will -return the desired \fBargv\fR equivalent (\fB\-use\fR -\fIwindowId\fR, correct \fB\-display\fR, etc.) -.PP -When \fB\-use\fR is not used, the new toplevel created is specially -decorated so the user is always aware that the user interface presented comes -from a potentially unsafe code and can easily delete the corresponding -interpreter. +When \fB\-use\fR is not used, the new toplevel created is specially decorated +so the user is always aware that the user interface presented comes from a +potentially unsafe code and can easily delete the corresponding interpreter. .PP -On X11, conflicting \fB\-use\fR and \fB\-display\fR are likely -to generate a fatal X error. +On X11, conflicting \fB\-use\fR and \fB\-display\fR are likely to generate a +fatal X error. .SH "SEE ALSO" safe(n), interp(n), library(n), load(n), package(n), source(n), unknown(n) .SH KEYWORDS -alias, auto\-loading, auto_mkindex, load, master interpreter, safe +alias, auto-loading, auto_mkindex, load, master interpreter, safe interpreter, slave interpreter, source '\" Local Variables: '\" mode: nroff |