Product Documentation

TDK 3.2 Documentation

Table of Contents
ActiveState, a division of Sophos

Tcl Dev Kit Release Notes

Introduction

ActiveState's Tcl Dev Kit is a powerful set of development tools and an extended Tcl platform for professional Tcl developers.

Tcl Dev Kit is a component of ActiveTcl Pro Studio, which also includes ActiveState's Komodo IDE enhanced with integrated Tcl debugging and syntax checking. For more information on ActiveTcl Pro Studio and its benefits, see ActiveTcl Pro Studio.

Tcl Dev Kit includes the following Tcl productivity tools:

Tcl Dev Kit binaries for Windows, Linux, HP-UX, AIX, and Solaris are available on the ActiveState web site.

Top

New in Version 3.2

General

  • Bugfixes for several tools.
  • Removed the embedded ActiveTcl distribution. The Tcl Dev Kit applications now work with any (Active)Tcl installation they find.
  • Removed the Tcl Browser Plugin distribution.

Tcl Dev Kit Compiler

Tcl Dev Kit TclApp

  • Revised the search for package definition files. TclApp now manages a list of paths to search in its global preferences. Default values are set during installation based on the found (Active)Tcl installations.
  • Added a new tab Kit Info allowing the editing of the string information embedded in Windows executables (Copyright, Version, ...). The associated command line option is -stringinfo.

Tcl Virtual Filesystem Explorer

  • Extended the Version Tab in the File Properties Dialog to allow editing of the shown string information embedded into Windows executables.
Top

Release History

Tcl Dev Kit 3.1.1: December, 2004

General

  • Updated to the ActiveTcl 8.4.9 code base.
  • Bugfixes for several tools.

Tcl Dev Kit Compiler

  • Now providing the sources of package tbcload.

Tcl Dev Kit 3.1: March, 2004

General

  • In all the graphical tools, Ctrl-plus and Ctrl-minus can be used to increase or decrease the font size. Alternatively, Ctrl-MouseWheel will have the same effect on operating systems where the mouse wheel is supported.
  • Tcllib version 1.6 is supported.
  • The HTML version of the documentation now has search functionality.

Cross Reference Tool

  • Scanning performance is faster (approximately 14 times faster), uses less memory, and generates a smaller database (by approximately 60%).
  • The 3.1 version of the Cross Reference Tool can read databases generated by the 3.0 version; however, 3.1 databases cannot be read by the 3.0 version.

Virtual Filesystem Explorer

  • If the icon associated with a file type is "known" (based on the file's extension), it will be displayed more quickly. The file will subsequently be analyzed for identifying characteristics, and the icon will be updated if necessary. Icon identification is more intelligent; in addition to looking within the file, the application will also look in the registry (on Windows) and, if an association is found, the icon embedded in the associated application is used.
  • On Unix systems, the Virtual Filesystem Explorer now displays (by default) the current user's HOME directory in the directory panel.

TclApp

  • The graphical version of TclApp now displays the corresponding command-line string in the output displayed on the Run tab.
  • The Files tab has a new "Scan" button that lists the packages required by the items that have already been added on the Files tab.

Tcl Debugger

  • Tooltips can be disabled (or re-enabled) via the Windows tab in the Preferences.

Inspector

  • Tooltips can be disabled (or re-enabled) via the Help | Show Tooltips menu option.

Browser Plugin

  • The plugin initialization crashing issue on HP-UX and Solaris has been corrected.
Top

Tcl Dev Kit 3.0: November, 2003

Tcl Dev Kit version 3.0 includes two new tools and numerous enhancements to existing tools. The following sections provide a brief overview of the new tools and enhancements to existing tools. Refer to the relevant chapter in the User Guide for a complete description.

Project files from previous versions of the Tcl Dev Kit are compatible with this version.

Virtual Filesystem Explorer (New!)

The Virtual Filesystem Explorer is used to mount and navigate system drives and volumes, to view the contents of archive files with .zip extensions, and to view the contents of starkits and starpacks. Refer to the Virtual Filesystem Explorer section in the User Guide for complete information.

Running the Virtual Filesystem Explorer:

Windows

  • Start Menu: Start | Programs | ActiveState Tcl Dev Kit | Tcl Dev Kit VFS Explorer
  • Command Line: tclvfse.tcl

Unix

  • Shell Prompt: tclvfse

Cross Reference Tool (New!)

The Cross Reference Tool is a new application that builds a database of program components, including packages, namespaces, variables, etc. Program component information can be extracted from programs and packages contained in TclApp (or Prowrap) projects, Tcl Dev Kit Package definitions (".tap files"), and from Komodo project files. The database can be explored via any of the program components. For example, the Cross Reference Tool can be used to view commands and variables within namespaces, or the source of variable definitions. Refer to the Cross Reference Tool section of the User Guide for complete information.

Running the Cross Reference Tool:

Windows

  • Start Menu: Start | Programs | ActiveState Tcl Dev Kit | Tcl Dev Kit Cross Reference Tool
  • Command Line: tclxref.tcl

Unix

  • Shell Prompt: tclxref

Debugger

  • Renamed Executable: To start the debugger from the Windows command line, enter tcldebugger.tcl. From the Unix command line, enter tcldebugger.
  • Integrated Coverage: It it no longer necessary to invoke the debugger with the coverage switch; coverage functionality is accessible via the View | Code Coverage menu option, or via the Code Coverage button on the toolbar.
  • Profiling: Profiling has been extended to include a timing mechanism. Timing information for individual calls is displayed on the Calls tab in the Code Coverage and Profiling dialog.
  • Debugging Multiple Processes: The debugger can "spawn" another debugger process. To control spawning, use the sub-commands on the Debug | Breakpoints menu ("Add all Spawnpoints" (each line where...); "Add Spawnpoint" (a specific line where a new debugger process should be spawned); "Disable Spawnpoint").
  • User Preferences: User preferences from previous Tcl Dev Kit versions (such as debugger color usage) will not be imported during installation, and must be manually re-configured.

Checker

  • Renamed Executable: To start the graphical version of the Checker from the Windows command line, enter tclchecker.tcl. From the Unix command line, enter tclchecker.
  • Package Versions: The -use option allows a version specification, and overrides package require statements. For example, -use tk4.1 will scan against version 4.1 of Tk, even if the package require statement specified a different Tk version.
  • Variables: The Checker now scans variable usage.
  • Checker API: The Checker API is documented in the User Guide.

Compiler

  • Renamed Executable: To start the Compiler from the Windows command line, enter tclcompiler.tcl. From the Unix command line, enter tclcompiler.
  • 8.3 Compiler: The 8.3-compatible compiler is no longer included.

TclApp

  • Renamed Executable: To start the graphical version of TclApp from the Windows command line, enter tclapp.tcl. From the Unix command line, enter tclapp. To use the command-line version, append options to the command.
  • Icon Preview: In the graphical TclApp, if an icon is associated with the selected Prefix file (as specified on the Wrapping tab), the icon will be displayed to the left of the Prefix file field.
  • Custom Icons: Custom icons can be assigned to wrapped applications using the Custom icon field on the Wrapping tab of the graphical TclApp, or using the -icon path command-line switch.
  • Starkit to Starpack Conversion: TclApp can be used to convert starkits into starpacks.
  • Command-Line Logging: When using the command-line version of TclApp, output can be written to a log file using the new -log switch.
  • Default Extensions: When using a -prefix file, the prefix file's extension will be used as the default extension for the generated application (if no explicit output file name is specified). If the prefix has no extension, the name of the generated application will have no extension.
  • Package Versions: If the version of a package specified in a TclApp project file does not exist, the command-line version of TclApp will fail unless the -pkg-accept switch is used (which will use the highest available version of the package). When using the graphical TclApp, a message will be displayed when opening the project file, and the highest available version of the specified package will be used.

Package Editor

  • Renamed Executable: To start the Package Editor from the Windows command line, enter tclpe.tcl. From the Unix command line, enter tclpe.

Service Manager

  • Renamed Executable: To start the Service Manager from the Windows command line, enter tclsvc.tcl.
  • Service Base Kit: The Tcl Dev Kit includes a new base kit ("base-tclsvc-win32-ix86.exe") that can be used to build "portable" services. When using TclApp to generate the application, specify base-tclsvc-win32-ix86.exe as the prefix file. This service can then be installed on any system (using the Tcl Dev Kit's Service Manager) that supports Windows NT-based services.

Inspector

  • Renamed Executable: To start the Inspector from the Windows command line, enter tclinspector.tcl. From the Unix command line, enter tclinspector.
  • Updated Icons: The icons in the Inspector have been updated.

Documentation and Demos

  • Demos: The demonstration programs included with the Tcl Dev Kit have been updated and expanded. See the Demos page for a list and brief description of each program.
  • Tutorials: There is a new Debugging Subprocesses tutorial; the Building TclApps tutorial has been expanded to include wrapping extensions and DLLs.

Tcl Dev Kit 3.0 Beta 1: November, 2003

Tcl Dev Kit 2.6: May, 2003

  • TclApp supports a new -interpreter option for specifying the interpreter to be included with starkits.
  • TclApp supports a new -notbcload option that prevents the inclusion of the tbcload package in the output application.
  • The debugger now passes STDOUT and STDERR output, and prompts for STDIN input, via the Eval Console.

Tcl Dev Kit 2.5: February, 2003

  • The Tcl Dev Kit Wrapper has been replaced by the new TclApp component. This component is capable of generating starkits, starpacks and Windows services.
  • The Tcl Dev Kit includes a new "Service Manager" component for registering Windows services built with TclApp.
  • The Inspector component is now fully exposed; previously, only aspects of the Inspector were utilized by the Debugger with Coverage component.
  • This version of the Tcl Dev Kit includes the Tcl Browser Plugin for Internet Explorer and browsers based on the Netscape plug-in API.

Tcl Dev Kit 2.5 beta 2: February, 2003

Tcl Dev Kit 2.5 beta 1: January, 2003

Tcl Dev Kit 2.1: November, 2002

  • Based on the Tcl 8.3.5 core; the Tcl 8.4 components are based on 8.4.1
  • Additional Wrapper stubs to support Tcl 8.4-based applications. See Specifying the Tcl Interpreter for a list of command-line interpreters, or Wrapping Tab for information on specifying interpreters in the graphical Wrapper.
  • Compiler support for Tcl 8.4-based applications.
  • The Wrapper stubs for the "-lite" variants of the bigtclsh and bigwish interpreters are now the default. The non-lite versions are no longer supported.

Tcl Dev Kit 2.0.1: October, 2002

  • TclXML version 2.3 (including expat)
  • TclDOM version 2.3
  • Fixed bug in handling of PATHEXT variable when running a Windows installation as a user without administrative rights

Tcl Dev Kit 2.0: August, 2002

  • Graphical Compiler The Tcl Dev Kit Compiler has a new graphical interface.
  • Graphical Wrapper The Tcl Dev Kit Wrapper has a new graphical interface.
  • Code Profiling The Tcl Dev Kit Debugger now provides code coverage analysis and profiling.
  • View Syntax Errors in Debugger The Tcl Dev Kit Debugger has a new Syntax Errors dialog that can be used to quickly list and display all the errors in programs open in the code display.
  • Checker API The Tcl Dev Kit Checker documentation now includes the Checker Interface Specification, for writing custom checker packages.
  • Variable Value Formatting You can now specify the format (hex, octal, etc) in which variable values are displayed in the Variable Display pane, the Watch Variables window and the Data Display window.
  • Support for Tcl 8.4
  • Project Management The file format for debugger projects has changed between Tcl Dev Kit version 1 and 2. Version 1 .tpj files can still be opened by the debugger; changes to version 1 projects will still be stored in the version 1 format. However, information about variable value formatting cannot be stored in version 1 project files. New projects will always use the version 2 format.

TclPro 2.0 beta 1: June, 2002

TclPro 1.5.0.2: January, 2002

  • TclPro Wrapper: fixed a bug where big shells (for wrapping of scripts that used [incr Tcl], TclX, ...) were not being distributed
  • TclPro Wrapper: reintroduced *-dynamic shells to distribution
  • ActiveTcl 8.3.4.2: support (and inclusion) of the latest ActiveTcl version

TclPro 1.5.0.1: December, 2001

TclPro 1.5.0.1 beta 1: October, 2001

Top

Known Issues

  • If the file type icon displayed in the Virtual Filesystem Explorer changes based on file analysis, the new icon will not change until the window is refreshed (for example, by covering then uncovering the application).
  • User preferences from previous Tcl Dev Kit versions (such as debugger color usage) will not be imported during installation, and must be manually re-configured.
  • The compiled help file cannot be opened on Windows NT4 systems.
Top

Contact ActiveState

  • For installation-related support issues, please send questions to support@ActiveState.com.
  • Subscribe to the Tcl mailing lists. Mailing list information and list archives can be viewed on ASPN, the ActiveState Programmer Network.
  • See the Resources topic for more Tcl information sources.
  • Submit an online Bug Report. From this form, you can also view existing bugs and check the status of previous submissions. When submitting a bug report, please include all relevant details and one or more examples that will help us reproduce the problem.
Top