Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Mentry, Scrollutil, Tablelist, Tsw: Minor improvements in the documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
48e317665a5bc56c3079f4dc5358689f |
| User & Date: | csaba 2025-03-23 16:21:27.524 |
Context
|
2025-03-24
| ||
| 11:05 | Released Mentry 4.4. check-in: bcb31e457b user: csaba tags: trunk | |
|
2025-03-23
| ||
| 16:21 | Mentry, Scrollutil, Tablelist, Tsw: Minor improvements in the documentation. check-in: 48e317665a user: csaba tags: trunk | |
|
2025-03-22
| ||
| 16:14 | Mentry: Updated for version 4.4. See the ChangeLog for details. check-in: 07b750d88a user: csaba tags: trunk | |
Changes
Changes to modules/mentry/README.txt.
| ︙ | ︙ | |||
96 97 98 99 100 101 102 | Mentry_tile. The main difference between the two is that Mentry_tile enables the tile-based, theme-specific appearance of mentry widgets; this package requires tile 0.6 or higher. It is not possible to use both packages in one and the same application, because both are implemented in the same "mentry" namespace and provide identical commands. | | | | | 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 |
Mentry_tile. The main difference between the two is that Mentry_tile
enables the tile-based, theme-specific appearance of mentry widgets;
this package requires tile 0.6 or higher. It is not possible to use
both packages in one and the same application, because both are
implemented in the same "mentry" namespace and provide identical
commands.
To be able to access the commands and variables of the Mentry package,
your scripts must contain one of the lines
package require mentry ?version?
package require Mentry ?version?
Likewise, to be able to access the commands and variables of the
Mentry_tile package, your scripts must contain one of the lines
package require mentry_tile ?version?
package require Mentry_tile ?version?
Since the packages Mentry and Mentry_tile are implemented in the
"mentry" namespace, you must either import the procedures you need, or
|
| ︙ | ︙ |
Changes to modules/scrollutil/README.txt.
| ︙ | ︙ | |||
90 91 92 93 94 95 96 | the same application, because both are implemented in the same "scrollutil" namespace and provide identical commands (except for the commands "scrollutil::scrollednotebook", "scrollutil::plainnotebook", "scrollutil::addclosetab", "scrollutil::removeclosetab", and "scrollutil::closetabstate", which are provided by the Scrollutil_tile package only). | | | | | | 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 |
the same application, because both are implemented in the same
"scrollutil" namespace and provide identical commands (except for the
commands "scrollutil::scrollednotebook", "scrollutil::plainnotebook",
"scrollutil::addclosetab", "scrollutil::removeclosetab", and
"scrollutil::closetabstate", which are provided by the Scrollutil_tile
package only).
To be able to access the commands and variables of the Scrollutil
package, your scripts must contain one of the lines
package require scrollutil ?version?
package require Scrollutil ?version?
Likewise, to be able to access the commands and variables of the
Scrollutil_tile package, your scripts must contain one of the lines
package require scrollutil_tile ?version?
package require Scrollutil_tile ?version?
Since the packages Scrollutil and Scrollutil_tile are implemented in the
"scrollutil" namespace, you must either import the procedures you need,
or use qualified names like "scrollutil::scrollarea".
|
| ︙ | ︙ |
Changes to modules/scrollutil/doc/scrollutil.html.
| ︙ | ︙ | |||
384 385 386 387 388 389 390 | in the same <code>scrollutil</code> namespace and provide identical commands (except for the commands <code>scrollutil::scrollednotebook</code>, <code>scrollutil::plainnotebook</code>, <code>scrollutil::addclosetab</code>, <code>scrollutil::removeclosetab</code>, and <code>scrollutil::closetabstate</code>, which are provided by the Scrollutil_tile package only).</p> | | | | | 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 |
in the same <code>scrollutil</code> namespace and provide identical commands
(except for the commands <code>scrollutil::scrollednotebook</code>,
<code>scrollutil::plainnotebook</code>, <code>scrollutil::addclosetab</code>,
<code>scrollutil::removeclosetab</code>, and
<code>scrollutil::closetabstate</code>, which are provided by the
Scrollutil_tile package only).</p>
<p>To be able to access the commands and variables of the Scrollutil package,
your scripts must contain one of the lines</p>
<blockquote>
<pre>
package require scrollutil ?<i>version</i>?
package require Scrollutil ?<i>version</i>?
</pre>
</blockquote>
<p>You can use either one of the two statements above because the file
<code>scrollutil.tcl</code> contains both lines</p>
<blockquote>
<pre>
package provide scrollutil ...
package provide Scrollutil ...
</pre>
</blockquote>
<p>Likewise, to be able to access the commands and variables of the
Scrollutil_tile package, your scripts must contain one of the lines</p>
<blockquote>
<pre>
package require scrollutil_tile ?<i>version</i>?
package require Scrollutil_tile ?<i>version</i>?
</pre>
|
| ︙ | ︙ |
Changes to modules/tablelist/README.txt.
| ︙ | ︙ | |||
135 136 137 138 139 140 141 | Tablelist_tile. The main difference between the two is that Tablelist_tile enables the tile-based, theme-specific appearance of tablelist widgets; this package requires tile 0.6 or higher. It is not possible to use both packages in one and the same application, because both are implemented in the same "tablelist" namespace and provide identical commands. | | | | | | 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 |
Tablelist_tile. The main difference between the two is that
Tablelist_tile enables the tile-based, theme-specific appearance of
tablelist widgets; this package requires tile 0.6 or higher. It is not
possible to use both packages in one and the same application, because
both are implemented in the same "tablelist" namespace and provide
identical commands.
To be able to access the commands and variables of the Tablelist
package, your scripts must contain one of the lines
package require tablelist ?version?
package require Tablelist ?version?
Likewise, to be able to access the commands and variables of the
Tablelist_tile package, your scripts must contain one of the lines
package require tablelist_tile ?version?
package require Tablelist_tile ?version?
Since the packages Tablelist and Tablelist_tile are implemented in the
"tablelist" namespace, you must either import the procedures you need,
or use qualified names like "tablelist::tablelist".
|
| ︙ | ︙ |
Changes to modules/tablelist/doc/tablelist.html.
| ︙ | ︙ | |||
245 246 247 248 249 250 251 | and <b>Tablelist_tile</b>. The main difference between the two is that Tablelist_tile enables the tile-based, theme-specific appearance of tablelist widgets; this package requires tile 0.6 or higher. It is not possible to use both packages in one and the same application, because both are implemented in the same <code>tablelist</code> namespace and provide identical commands.</p> | | | | | 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 |
and <b>Tablelist_tile</b>. The main difference between the two is that
Tablelist_tile enables the tile-based, theme-specific appearance of tablelist
widgets; this package requires tile 0.6 or higher. It is not possible
to use both packages in one and the same application, because both are
implemented in the same <code>tablelist</code> namespace and provide
identical commands.</p>
<p>To be able to access the commands and variables of the Tablelist package,
your scripts must contain one of the lines</p>
<blockquote>
<pre>
package require tablelist ?<i>version</i>?
package require Tablelist ?<i>version</i>?
</pre>
</blockquote>
<p>You can use either one of the two statements above because the file
<code>tablelist.tcl</code> contains both lines</p>
<blockquote>
<pre>
package provide tablelist ...
package provide Tablelist ...
</pre>
</blockquote>
<p>Likewise, to be able to access the commands and variables of the
Tablelist_tile package, your scripts must contain one of the lines</p>
<blockquote>
<pre>
package require tablelist_tile ?<i>version</i>?
package require Tablelist_tile ?<i>version</i>?
</pre>
|
| ︙ | ︙ |
Changes to modules/tsw/README.txt.
| ︙ | ︙ | |||
76 77 78 79 80 81 82 | On Windows, use WinZip or some other program capable of unpacking the distribution file "tsw1_0.zip" into the directory "tsw1.0", with the subdirectories "demos", "doc", and "scripts". How to Use It? -------------- | | | | 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 |
On Windows, use WinZip or some other program capable of unpacking the
distribution file "tsw1_0.zip" into the directory "tsw1.0", with the
subdirectories "demos", "doc", and "scripts".
How to Use It?
--------------
To be able to access the commands and variables of the Tsw package, your
scripts must contain one of the lines
package require tsw ?version?
package require Tsw ?version?
Since the Tsw package is implemented in its own namespace called "tsw",
you must either invoke the
|
| ︙ | ︙ |
Changes to modules/tsw/doc/tsw.html.
| ︙ | ︙ | |||
156 157 158 159 160 161 162 | <p>Notice that in tklib the Tsw <code>demos</code> directory is replaced with the subdirectory <code>tsw</code> of the <code>examples</code> directory. Please take this into account when reading the <a href= "#examples">examples</a> below.</p> <h3 id="ov_use">How to Use It?</h3> | | | | 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 |
<p>Notice that in tklib the Tsw <code>demos</code> directory is replaced with
the subdirectory <code>tsw</code> of the <code>examples</code>
directory. Please take this into account when reading the <a href=
"#examples">examples</a> below.</p>
<h3 id="ov_use">How to Use It?</h3>
<p>To be able to access the commands and variables of the Tsw package, your
scripts must contain one of the lines</p>
<blockquote>
<pre>
package require tsw ?<i>version</i>?
package require Tsw ?<i>version</i>?
</pre>
</blockquote>
|
| ︙ | ︙ |